Release 3.4 - July 2020

[meisterT]

Status of Bazel 3.4

• Target baseline: 2020-07-02
• Expected release date: 2020-07-13
• List of release blockers

To report a release-blocking bug, please file a bug using the Release blocker label, and cc me.

Task list:

• Update GitHub issues for incompatible changes
• Pick release baseline: 7404d17
• Create release candidate: release-3.4.0rc1
• Check downstream projects:
• Create draft release announcement
• Send for review the release announcement PR: Add blog post for 3.4 bazel-blog#231
• Push the release, notify package maintainers:
• Update the documentation
• Push the blog post
• Update the release page

[davido]

@meisterT Should we mention in the release notes that upcoming Release 3.4 includes new java_tools release 9.0 with major Error Prone version upgrade to 2.4.0, with a lot of fixes and out of the box support for Java 14?

And also warn, that some new EP checks were added and some existing checks were extended so that more diagnostic could be reported for new and existing EP checks so that Bazel users may see new compiler warnings or even failures with upcoming Bazel release 3.4?

FTR: I uploaded this PR #11447 to add --incompatible_use_java_tools_beta_release option to make the java_tools upgrade process less disruptive, but it wasn't merged yet. So may be next time java_tools upgrade process will be less painful.

[jmillikin-stripe]

Would it be possible to get #11659 reviewed and pulled into this release?

[Yannic]

Would it be possible to also get #11617 into 3.4?

[meisterT]

release-3.4.0rc1 cut at 7404d17

@jmillikin-stripe @Yannic both PRs are merged and included.

[meisterT]

WIP release announcement: https://docs.google.com/document/d/1wDvulLlj4NAlPZamdlEVFORks3YXJonCjyuQMUQEmB0/edit#heading=h.8vvjiikmd0sz

@davido please suggest your change there

[davido]

@davido please suggest your change there

Thanks for the pointer. Done.

[meisterT]

Already known commit to 🍒 pick: f31f2d7

[meisterT]

just created a new candidate: scripts/release/release.sh create --force_rc=2 3.4.0 7404d17ac76da876ae0b432d1fccf222a9e991fe f31f2d7

[xingxinghuo1000]

@meisterT Would you please give a plan to build a pakcage(installer.sh). I want to try a new feature. if it does not work, I'll notify the author ASAP. Thanks

[meisterT]

You can download the most recent release candidate here:
https://releases.bazel.build/3.4.0/rc2/index.html

Another way to test releases is to use Bazelisk (https://github.com/bazelbuild/bazelisk) and set the environment variable USE_BAZEL_VERSION to last_rc (see more https://github.com/bazelbuild/bazelisk#how-does-bazelisk-know-which-bazel-version-to-run).

[meisterT]

I have just released Bazel 3.4.0:
https://github.com/bazelbuild/bazel/releases/tag/3.4.0
https://releases.bazel.build/3.4.0/release/

@vbatts @petemounce @excitoon please update your packages

[meisterT]

The release seems to be broken: #11756

[meisterT]

Creating new candidate with scripts/release/release.sh create 3.4.1 7404d17ac76da876ae0b432d1fccf222a9e991fe f31f2d7 08bf906 0415511

[meisterT]

3.4.1 has been released, blog post https://blog.bazel.build/2020/07/13/bazel-3-4.html

https://github.com/bazelbuild/bazel/releases/tag/3.4.1
https://releases.bazel.build/3.4.1/release/

@vbatts @petemounce @excitoon sorry for the second ping, but this should now be ready to be published

[vbatts]

fedora and centos build is kicked off: https://copr.fedorainfracloud.org/coprs/vbatts/bazel/build/1553694/

[or-shachar]

@meisterT - Do you know when is the next release and who's the owner of it?

edit: Just saw the post by @philwo . Release 3.5 should be released this month.

I want to make sure that 003f766 enters.

Thanks!

[meisterT]

I have just created #11885 for the next release. @aiuto agreed to shepherd it.

[aiuto]

I will probably cut the baseline on August 5, so it will be in it.

…

On Sun, Aug 2, 2020 at 4:26 AM Or Shachar ***@***.***> wrote: @meisterT <https://github.com/meisterT> - Do you know when is the next release and who's the owner of it? I want to make sure that 003f766 <003f766> enters. Thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#11687 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXHHHFPK2HRAD4JSSJ47G3R6UPLRANCNFSM4ONIKKGA> .