Release 1.2 - November 2019 (stable)

[dslomov]

Target RC: November 4th, 2019

[meisterT]

If you didn't cut a baseline yet, you might want to wait until #10184 is merged.

[philwo]

Status of Bazel 1.2

Bazel 1.2, November 12th and a green downstream pipeline: The stars have finally aligned. Let's get this release ready:

• Target baseline: 11deef7
• Expected release date: 2019-11-26
• 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: 11deef7
• Create release candidate:
• Check downstream projects:
• Create draft release announcement
• Send for review the release announcement PR:
• Push the release, notify package maintainers:
• Update the documentation
• Push the blog post
• Update the release page

[philwo]

Created 1.2.0rc1 with baseline 11deef7 and cherry-pick c76c3e5.

RELEASE_NUMBER=1.2.0
BASELINE_COMMIT=11deef7582dfeec7a04ee3f7236393d9b8027367
git clone https://github.com/bazelbuild/bazel.git ~/src/bazel-release-$RELEASE_NUMBER
cd ~/src/bazel-release-$RELEASE_NUMBER
scripts/release/release.sh create $RELEASE_NUMBER $BASELINE_COMMIT c76c3e539c73ecf6e96e3e098be7be59e17bf276
scripts/release/release.sh push

[jmillikin-stripe]

Any chance of getting #10110 in? It's a three-line delta that materially improves ergonomics for scripting languages (Javascript, Ruby) when using hermetic runtimes.

[philwo]

Will create rc2 with additional cherry-pick #10222 in order to fix broken C++ compilation when using an empty PATH.

[philwo]

@jmillikin-stripe I reached out to Lukacs, if we can get this reviewed & imported today, I can cherry-pick it.

[jmillikin]

@philwo Thanks a ton! I'll keep an eye on my inbox in case there's any review feedback.

[philwo]

Bazel 1.2.0rc2 is ready:

RELEASE_NUMBER=1.2.0
RC_NUMBER=2
BASELINE_COMMIT=11deef7582dfeec7a04ee3f7236393d9b8027367
cd ~/src/bazel-release-$RELEASE_NUMBER
scripts/release/release.sh create --force_rc=$RC_NUMBER $RELEASE_NUMBER \
    $BASELINE_COMMIT \
    c76c3e539c73ecf6e96e3e098be7be59e17bf276 \
    63332eb556fadfe9edd0806add79942482adddef \
    ceadf0a063cb97c32aced143d2447781d1dafc38
scripts/release/release.sh push

[johnplate]

Is it still possible to get #10216 into 1.2? It is a trivial fix for a syntax error occurring with mingw-gcc that prevents us (GAPID team) to upgrade to anything newer than 0.26.0. Thanks in advance!

[keith]

Is there a target date for when this release will be finalized?

[philwo]

@johnplate I'll get that in.

@keith I hope we can release it tomorrow. I'm not aware of any regressions or other cherry-pick requests. Will do another downstream pipeline run to ensure everything looks green on CI.

[philwo]

Created Bazel 1.2.0rc3 with:

RELEASE_NUMBER=1.2.0
RC_NUMBER=3
BASELINE_COMMIT=11deef7582dfeec7a04ee3f7236393d9b8027367
cd ~/src/bazel-release-$RELEASE_NUMBER
scripts/release/release.sh create --force_rc=$RC_NUMBER $RELEASE_NUMBER \
    $BASELINE_COMMIT \
    c76c3e539c73ecf6e96e3e098be7be59e17bf276 \
    63332eb556fadfe9edd0806add79942482adddef \
    ceadf0a063cb97c32aced143d2447781d1dafc38 \
    dbe63b00954a25fa4405f7cbf273df78c16498dd
scripts/release/release.sh push

[philwo]

Downstream is green except for TensorFlow failing on macOS, which seems to be an incompatibility with their protobuf version and Xcode 11.1: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1287

[davido]

Am I correct to assume, that the new 1.2 release is the solution for this 1.0.1 overwrites 1.1.0 metadaten in Bazel apt repository issue?

Can we publish 1.2 release ASAP then?

We have complaints from Gerrit users who depend on Bazel apt repository containing the version included in Gerrit's .bazelversion file. They are not able to install 1.1.0, and as the consequence they cannot install the right Bazel version and cannot build gerrit, because the minimum version check is failing.

They cannot install bazelisk because it is not available on their standard Linux distribution.

IOW Gerrit users are blocked and cannot work on gerrit any more.

Here is the request to downgrade Bazel from 1.1.0 to 1.0.1, but that would be a pain, because we would have to revert a number of other changes as well, e.g. related to this Bazel bug.

[philwo]

@davido Yes, releasing Bazel 1.2.0 will fix the metadata issue for now. I'll do some final checks now and if everything looks fine, I'll release it.

We're very close to fixing the metadata generation for the repository, too, so that it will not happen again in the future.

[philwo]

Draft blog post with release notes is here: bazelbuild/bazel-blog#209

[philwo]

Release pushed and now building on CI: https://buildkite.com/bazel-trusted/bazel-release/builds/116

[keith]

@philwo it looks like the public doesn't have access to the pipeline, is there a way it could be readonly publicly?

[philwo]

@keith I'll see what I can do there tomorrow. 😊

If you're curious, the pipeline definition is here: https://github.com/bazelbuild/continuous-integration/blob/master/pipelines/bazel-release.yml

[philwo]

Bazel 1.2.0 has been released.

[chenrui333]

I have submit a ticket on this, #10297

It seems currently it impacts highsierra users.

[philwo]

The breakage reported by @chenrui333 will require a patch release, as breaking backwards compatibility with macOS High Sierra was not intended (and is not OK) in the 1.x line.

I'll do that on Monday.

[philwo]

When bazelbuild/continuous-integration#873 is merged, I will create the patch release.

[philwo]

Bazel 1.2.1 has been released.

[petemounce]

Chocolatey for 1.2.0 is published, apologies for the wait.

[petemounce]

1.2.1 pushed too.

[philwo]

Thank you, @petemounce!