Release - February 2018 - Target RC date: 2018-02-01 - name: 0.11.0

[damienmg]

Release tracking bug for February 2018:

• Target cut should be 1st of February (first business day of January) but it is close to FOSDEM so we might want to delay
• Name: 0.11.0

RM if we follow the rotation should be @katre: can you take it?

[buchgr]

thanks so much @petemounce ... ur work is awesome

[petemounce]

My pleasure :)

[katre]

Thanks very much @petemounce!

With this finished, I am closing the issue for this release.

[katre]

Re-opening to create RC for 0.11.1, cherrypicking fc98b44 to deal with #4736 .

[katre]

Release command:

release.sh create 0.11.1 \
  00d781ae78a8bd51d3c61b621d79f0bb095aff9e \
  ea2d4c4 \
  d855d81 \
  56aeb04 \
  cf3f81a \
  28bd997 \
  109e4b4 \
  b3d52b1 \
  1001141 \
  fc98b44

[katre]

The release branch is created, but given the current state of our CI system I do not know if Buildkite can create the release artifacts. @philwo and @buchgr , can you comment?

[katre]

Release branch is https://github.com/bazelbuild/bazel/tree/release-0.11.1

[buchgr]

cc: @vbatts

[vbatts]

hey hey! Been a while since you CC'ed, but usually blogtrottr.com does a good job emailing as soon as you tag the releases but didn't get notification of 0.11.0 :thinking:

https://copr.fedorainfracloud.org/coprs/vbatts/bazel/builds/ has up to 0.10.1

[vbatts]

perhaps i'll just jump to 0.11.1 once it's out?

[buchgr]

@vbatts I apologize. I have just noticed this myself a few hours ago and that's why I pinged you :-). It's up to you. 0.11.1 should be out next week.

We are currently working on a new release process and we'll be able to set it up so that we can automatically send you an e-mail. Again, apologies for not pinging you.

[vbatts]

Right on. I'll wait til 0.11.1 :-)

On Fri, Mar 2, 2018, 15:59 Jakob Buchgraber notifications@github.com wrote:

@vbatts https://github.com/vbatts I apologize. I have just noticed this myself a few hours ago and that's why I pinged you :-). It's up to you. 0.11.1 should be out next week.

We are currently working on a new release process and we'll be able to set it up so that we can automatically send you an e-mail. Again, apologies for not pinging you.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bazelbuild/bazel/issues/3959#issuecomment-370050761, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEF6VrLdpSHx7Wh_mwAmJMWikD4JK38ks5tabLFgaJpZM4QEZgf .

[philwo]

I'm working to get this pushed as a release, but am currently fighting with our scripts a bit. Sorry for the delay! Hope to get it out by tomorrow.

[philwo]

I had to recreate the release branch on my machine, as otherwise the script wouldn't let me release it.

Steps:

release.sh create 0.11.1 \
  00d781ae78a8bd51d3c61b621d79f0bb095aff9e \
  ea2d4c4 \
  d855d81 \
  56aeb04 \
  cf3f81a \
  28bd997 \
  109e4b4 \
  b3d52b1 \
  1001141 \
  fc98b44

# Resolve first conflict:
git rm site/docs/remote-caching.md
git cherry-pick --continue; exit

# Resolve second conflict:
vi tools/test/test-setup.sh  # Pick the second version of the conflicting diff.
git add tools/test/test-setup.sh
git cherry-pick --continue; exit

# Edit release notes to read:
Important changes:
  - Fixes regression building Android rules on Windows.

# Push
release.sh push

# Release
release.sh release

Now waiting for CI to build the binaries, will verify that they're fine and will run the release steps for GitHub, GCS and the apt repository then.

[philwo]

Release was built successfully: https://buildkite.com/bazel/release/builds/11 and released: https://groups.google.com/d/msg/bazel-discuss/lmuaMaYiY-o/r8CCYqO6AAAJ

🎉

[vbatts]

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

On Wed, Mar 7, 2018 at 10:19 AM Philipp Wollermann notifications@github.com wrote:

Release was built successfully: https://buildkite.com/bazel/release/builds/11 and released: https://groups.google.com/d/msg/bazel-discuss/lmuaMaYiY-o/r8CCYqO6AAAJ 🎉

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bazelbuild/bazel/issues/3959#issuecomment-371169893, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEF6fTMWVjJ85n0KnZjXY_O2pHRIxsnks5tb_j3gaJpZM4QEZgf .

[buchgr]

tyvm @vbatts

[petemounce]

0.11.1 is published to chocolatey.

[buchgr]

ty @petemounce !