We need more releases :) 0.5.2 incoming.
a47780541536764cf56d09f78a988d6155689c7f has an error in the commit message. Instead of action_config 'generic' it should say 'cc-flags-make-variable'.
hlopko
All 39 comments
Make sure fix for #3064 is included. The SHA of the fix is 7d8943e .
hlopko
on 6 Jun 2017
Thanks so much @mhlopko
buchgr
on 6 Jun 2017
What is the overhead to doing releases that makes them less frequent? (I mean: it sounds like the process is largely automated end-to-end).
petemounce
on 6 Jun 2017
Right now, our release candidates get more thorough testing by teams using Bazel internally. It's in the process of being automated, but we're not there yet. But ideally yeah, we would release more often, and regularly.
hlopko
on 6 Jun 2017
@mhlopko say - what are the chances of getting an RC cut for 0.5.2, so that we can give early feedback, but also get past our blocker (#3064)?
petemounce
on 8 Jun 2017
@petemounce If we'll have a green CI, I think we can cut something tomorrow (or soonish). It's been a while since the last baseline anyway.
hlopko
on 8 Jun 2017
I just cut a canary on @mhlopko's behalf. Waiting for Jenkins to process it. (I couldn't wait for a green CI, maybe that was a mistake.)
ulfjack
on 9 Jun 2017
68028317c1d3d831a24f90e2b25d1410ce045c54 fixes a deadlock in --experimental_ui; can we cherry-pick it to the next release candidate? Thanks.
aehlig
on 9 Jun 2017
I filed #3159 as a reminder to cherrypick the change.
ulfjack
on 9 Jun 2017
@mhlopko CI looks quite _gorgeously_ green (though I don't know which builds are which, particularly). Friendly ping?
petemounce
on 13 Jun 2017
We need a second cherrypick, which isn't merged yet.
ulfjack
on 13 Jun 2017
Any chance this will be released this week/beginning of next week?
On Tue, 13 Jun 2017 at 13:13 Ulf Adams notifications@github.com wrote:
We need a second cherrypick, which isn't merged yet.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/bazel/issues/3086#issuecomment-308071178,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF7Iy_UAWSFuteEAKGGp_kCZXTgEaks5sDmDAgaJpZM4NrwzD
.
ittaiz
on 13 Jun 2017
We also need to cherrypick 019935dfbb61e61d08d1351b0365fb4e2d0df305.
ulfjack
on 13 Jun 2017
Just baked rc2. If there are no blockers and no more release candidates, we can release on Friday at soonest (following the policy of at least 7 days from initial RC to a release). But since we needed 23 cherry-picks and 9 RCs for 0.5.0 I'm a little bit skeptical. I'll update this thread with all the news.
hlopko
on 13 Jun 2017
https://chocolatey.org/packages/bazel/0.5.2-rc2 is available. As with 0.5.1, this is the msysless flavour.
petemounce
on 13 Jun 2017
Thanks Pete for a quick packaging!
hlopko
on 13 Jun 2017
We'll need another cherrypick for #3189.
ulfjack
on 14 Jun 2017
Btw. the release notes are missing a line break between the cherrypicks.
ulfjack
on 14 Jun 2017
We need a cherry-pick of 1d82d199f82409f217a42bcefebb96f723f91caa ... as this fixes the JDK7 build.
buchgr
on 16 Jun 2017
I also marked #3055 as a release blocker.
ulfjack
on 20 Jun 2017
Possibly we'll need 9eea05d068a06ab642dd9d86d46ee5fa2e36b02e too
hlopko
on 20 Jun 2017
7dec00574aa91327693f6ba7e90bff5bc834253e, which is in the current RC was just rolled back internally for breaking bazel query --output package, so I'd like to request a cherrypick of the rollback commit (which has not yet been exported -- internal id is 159718294).
aj-michael
on 21 Jun 2017
I just created RC3 with all the mentioned cherry picks:
hlopko
on 22 Jun 2017
And since I forgot one important cherry pick, we have another rc:
https://storage.googleapis.com/bazel/0.5.2/rc4/index.html
hlopko
on 22 Jun 2017
https://chocolatey.org/packages/bazel/0.5.2-rc3 and https://chocolatey.org/packages/bazel/0.5.2-rc4 are available.
petemounce
on 23 Jun 2017
Thank you Pete!
hlopko
on 23 Jun 2017
@mhlopko Is there still a chance to cherry-pick 5b8045836fc64a783fa527fd7c4e274ccf14d6ff and 9b3f76ee2731cb951177cb2d656de8bbf0d4a4b5 ?
This will make TF GPU build work on Windows.
meteorcloudy
on 27 Jun 2017
Is that a regression? Otherwise I'd prefer if we push 0.5.2 and then start on 0.5.3 right away.
ulfjack
on 27 Jun 2017
Compare to 0.5.0, it's not, because GPU build is broken with it already.
But compare to previous version that works for TF Windows GPU build, it is.
I was thinking leave them to 0.5.3, but TF now wants to use Bazel to build a C library with GPU support.
Similar to http://ci.tensorflow.org/view/All/job/release-libtensorflow-windows/
How soon will 0.5.3 come?
meteorcloudy
on 27 Jun 2017
If #3248 is no longer a release blocker, I guess we can release 0.5.2 today? If that's the case, I am fine leaving it to 0.5.3. :)
meteorcloudy
on 27 Jun 2017
It's a release blocker for the next release, be it 0.6.0 or 0.5.3.
hlopko
on 27 Jun 2017
I see, so let's release 0.5.2 and then start 0.5.3 ASAP
meteorcloudy
on 27 Jun 2017
2 more cherry-picks on their way.
damienmg
on 27 Jun 2017
False alarm, still no more cherry picks for 0.5.2.
hlopko
on 27 Jun 2017
And here it comes: https://github.com/bazelbuild/bazel/releases/tag/0.5.2 :) Thank you all for all the help and testing!
hlopko
on 27 Jun 2017
Published https://chocolatey.org/packages/bazel/0.5.2 . I'm not a bot, promise :p
petemounce
on 27 Jun 2017
hlopko
on 27 Jun 2017
I think we're free to close this issue now. Lets try to get 0.6.0 next?
hlopko
on 28 Jun 2017
Congrats on 0.5.2 @mhlopko !
buchgr
on 29 Jun 2017
Related issues
davidzchen
·
3Comments
cyberbono3
·
3Comments
filipesilva
·
3Comments
GaofengCheng
·
3Comments
C00IHandLuke
·
3Comments
Most helpful comment
And here it comes: https://github.com/bazelbuild/bazel/releases/tag/0.5.2 :) Thank you all for all the help and testing!