-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.5.2 #3086
Comments
Make sure fix for #3064 is included. The SHA of the fix is 7d8943e . |
Thanks so much @mhlopko |
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). |
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. |
@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. |
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.) |
6802831 fixes a deadlock in |
I filed #3159 as a reminder to cherrypick the change. |
@mhlopko CI looks quite gorgeously green (though I don't know which builds are which, particularly). Friendly ping? |
We need a second cherrypick, which isn't merged yet. |
Any chance this will be released this week/beginning of next week?
…On Tue, 13 Jun 2017 at 13:13 Ulf Adams ***@***.***> 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
<#3086 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABUIF7Iy_UAWSFuteEAKGGp_kCZXTgEaks5sDmDAgaJpZM4NrwzD>
.
|
We also need to cherrypick 019935d. |
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. |
https://chocolatey.org/packages/bazel/0.5.2-rc2 is available. As with 0.5.1, this is the msysless flavour. |
Thanks Pete for a quick packaging! |
We'll need another cherrypick for #3189. |
Btw. the release notes are missing a line break between the cherrypicks. |
We need a cherry-pick of 1d82d19 ... as this fixes the JDK7 build. |
I also marked #3055 as a release blocker. |
Possibly we'll need 9eea05d too |
7dec005, 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). |
I just created RC3 with all the mentioned cherry picks: |
And since I forgot one important cherry pick, we have another rc: |
Thank you Pete! |
Is that a regression? Otherwise I'd prefer if we push 0.5.2 and then start on 0.5.3 right away. |
Compare to 0.5.0, it's not, because GPU build is broken with it already. |
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. :) |
It's a release blocker for the next release, be it 0.6.0 or 0.5.3. |
I see, so let's release 0.5.2 and then start 0.5.3 ASAP |
2 more cherry-picks on their way. |
To cherry-pick for #3086. Change-Id: I05db2aef04a7cd6cec22c918f00e4b47bae3a1f4 PiperOrigin-RevId: 160249482
Double quoting make bash interpret the backquote and bazel is not on the path of the resulting process, showing error on the console. To cherry-pick for #3086. Change-Id: I15a4cdbd349300c87bd90d56ecb8df63ecf62dfb PiperOrigin-RevId: 160250275
False alarm, still no more cherry picks for 0.5.2. |
And here it comes: https://github.com/bazelbuild/bazel/releases/tag/0.5.2 :) Thank you all for all the help and testing! |
Published https://chocolatey.org/packages/bazel/0.5.2 . I'm not a bot, promise :p |
I think we're free to close this issue now. Lets try to get 0.6.0 next? |
Congrats on 0.5.2 @mhlopko ! |
We need more releases :) 0.5.2 incoming.
a477805 has an error in the commit message. Instead of action_config 'generic' it should say 'cc-flags-make-variable'.
The text was updated successfully, but these errors were encountered: