Release 1.1 - October 2019 (stable)

[dslomov]

Target RC date - October 14th, 2019

[jmillikin-stripe]

Has the baseline CL already been cut? I'm hoping to get #9872 into v1.1 since it was too late for v1.0.

[meisterT]

My plan is to cut the release on Monday morning MUC time.

[iirina]

Can we include the latest java_tools release #9991 in Bazel 1.1? We release java_tools once per month with the goal of upgrading the default version in bazel released on the same month. We were late with the java_tools release because of some uncertainty around #8772 and also because of not knowing when bazel 1.1 rc1 is going to be cut.

[iirina]

@meisterT The commit to include is f939278.

[davido]

Can we include the latest java_tools release #9991 in Bazel 1.1?

+1 to include #9991 in Bazel 1.1.

f939278 partially fixed #8772, as it includes this PR.

[meteorcloudy]

Please make sure to include 618e5a2 for fixing #9995

[meisterT]

RC1 created: scripts/release/release.sh create 1.1.0 d9fe1d4078c25912427c9b2e79e115f4ee9b7ab8

expected release date Oct 21

[meisterT]

Downstream build is here: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1234
Draft release announcement is here: https://docs.google.com/document/d/1wDvulLlj4NAlPZamdlEVFORks3YXJonCjyuQMUQEmB0/edit?ts=5da47c92&pli=1#heading=h.c3hdfz9d222b

[meisterT]

First release blocker (more to come):
#10023
(java tools)

[meisterT]

Issue with Bazelisk: #10024

[meisterT]

Issue with Tulsi: #10026

[iirina]

Please cherry pick 0a8071a for #10023.

[meisterT]

creating new rc with scripts/release/release.sh create --force_rc=2 1.1.0 d9fe1d4078c25912427c9b2e79e115f4ee9b7ab8 0a8071a

[meteorcloudy]

Since 618e5a2 is in the release, but it's rollbacked and replaced by 3a43b09, we probably should cherry-pick ac99c29 and 3a43b09.

[meisterT]

We have decided offline that Yun's cherry-pick request would not require a new RC.

Downstream pipeline is green, so we'll release on Monday as planned if there are no new blockers until then.

[meisterT]

We have a new release.

cc @vbatts @petemounce @excitoon

[vbatts]

What's the branch strategy now? 1.1 and 1.0.1 in the same day. COPR repos like I am using for fedora and CentOS only publish the latest build of a package.

…

-------- Original Message --------

On Oct 21, 2019, 05:49, Tobias Werth wrote: We have a new release. cc ***@***.***(https://github.com/vbatts) ***@***.***(https://github.com/petemounce) ***@***.***(https://github.com/excitoon) — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#9982?email_source=notifications&email_token=AAAQL2IMJPXWQG265NO5SJDQPV3KLA5CNFSM4I7OPBWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBZXRZQ#issuecomment-544438502), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAAQL2J43EJV3DKCX3F5NBLQPV3KLANCNFSM4I7OPBWA).

[meisterT]

1.0.1 only contains bug fixes, while 1.1.0 also contains (compatible) features.

[vbatts]

On 21/10/19 02:49 -0700, Tobias Werth wrote: We have a new release. cc ***@***.*** ***@***.*** ***@***.***

fedora and centos/rhel builds kicked off for x86_64 and aarch64: https://copr.fedorainfracloud.org/coprs/vbatts/bazel/build/1067164/ also, success on building fedora, centos, and rhel for ppc64le: https://copr.fedorainfracloud.org/coprs/vbatts/bazel/build/1067140/ (only oddity is `env ./output/bazel build ${EXTRA_BAZEL_ARGS} //scripts:bazel-complete.bash` is failing with "Exec format error")

[meisterT]

Thanks!

[petemounce]

Gonna be a latency for chocolatey release; I'm in China until November.

[keith]

We discovered a bug that I believe warrants a patch release once we can find a fix #10184

[keith]

I have submitted a fix for this issue #10185 and would love it if we could consider a patch release for this.

[petemounce]

Chocolatey published, apologies for the wait.