-
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 2.2 (stable) - February 2020 #10133
Comments
Scheduling note: if possible, I'd love to get #10622 into this release -- it's been delayed a fairly long time on design reviews, and our internal builds are suffering for it. |
@meteorcloudy Can we make Bazel 2.2 our first release built on Kokoro? :) |
|
@jmillikin-stripe I'm sorry, the PR you wanted to have in Bazel 2.2 still hasn't been merged yet, but I'm already super late with cutting the baseline for Bazel 2.2. The next Bazel release will already be cut on March 1st. I pinged Jakob, but he said he can't get it done right now, so I have to go ahead and prepare Bazel 2.2 now. |
I'm preparing Bazel 2.2.0 now:
|
It's here I guess? ➡️ https://releases.bazel.build/2.2.0/rc1/index.html |
@gertvdijk Correct. :) I'll send the announcement to bazel-discuss@ now. |
@philwo little bit of a threadjack but I noticed in the rc1 release notes the cuda/opencl file extension support I've been using for ~2 years now and that recently got accepted was reverted Is this going to be cut from 2.2 / can you maybe make sure to chase down why it's important to revert those changes and the right thing to do over all? |
FWIW, 2.2.0rc1 works like a charm here as drop-in replacement for 2.1.0 (tested @ linux x86_64 via Bazelisk on some internal repos). |
@gertvdijk Let's push it then :D I haven't heard about any release blockers. Edit: I haven't finished the release notes yet, will do that tomorrow morning and then push the release. 2.2.0 will be identical to 2.2.0rc1 unless I hear anything by then. |
Release 2.2.0 has been pushed, release notes on our blog to follow. |
fedora/centos/RHEL builds are kicked off: https://copr.fedorainfracloud.org/coprs/build/1282540
also note, this package is "bazel2"
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
…On Tuesday, March 3, 2020 4:53 AM, Dmitry Lomov ***@***.***> wrote:
Status of Bazel 2.2.0
- Target baseline: 78055ef
- Expected release date: 2020-02-20
- [List of release blockers](https://github.com/bazelbuild/bazel/labels/Release%20blocker)
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: 78055ef
- Create release candidate: https://releases.bazel.build/2.2.0/rc1/index.html
- Check downstream projects: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1389
- [Create draft release announcement](https://docs.google.com/document/d/1wDvulLlj4NAlPZamdlEVFORks3YXJonCjyuQMUQEmB0/edit)
- Send for review the release announcement PR:
- Push the release, notify package maintainers: ***@***.***(https://github.com/vbatts) ***@***.***(https://github.com/petemounce) ***@***.***(https://github.com/excitoon)
- Update the documentation
- Push the blog post
- Update the [release page](https://github.com/bazelbuild/bazel/releases/)
—
You are receiving this because you were mentioned.
Reply to this email directly, [view it on GitHub](#10133?email_source=notifications&email_token=AAAQL2OEHTC6L5U4NA25DJTRFTHSPA5CNFSM4JGVBMU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HVKF6QQ), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAAQL2JOSEEOQ46YBDD3K7TRFTHSPANCNFSM4JGVBMUQ).
|
bazelbuild/bazel#10133 Signed-off-by: Vincent Batts <[email protected]>
bazelbuild/bazel#10133 Signed-off-by: Vincent Batts <[email protected]>
none of the aarch64 builds succeeded |
Looks like this is the error on aarch64:
If someone can repro and send a PR to fix it, I can look into doing a patch release. I won't have time to do it myself this week unfortunately. |
We should also file this so I can track it for the next release. |
@philwo Hi, were you able to do a patch? I also get this exact error. My Java details:
I have confirmed that
|
@vbatts I still cannot install 2.2.0 on Fedora 31:
|
I am also still unable to build 2.2.0 on ARM. |
|
Thanks! Should the documentation be updated: [1]?
[1] https://docs.bazel.build/versions/master/install-redhat.html |
@source-creator Unfortunately not yet. If anyone has a working patch that makes the build work on ARM, I'm happy to review it and get it in. |
Per discussion at bazelbuild#10133, Bazel 2.x is packaged as bazel2 on Red Hat.
Per discussion at bazelbuild#10133, Bazel 2.x is packaged as bazel2, and 3.x as bazel3 on Red Hat.
@philwo is there a reason why this issue is still opened or just forgotten? |
@limdor Just forgotten to close it, sorry. |
Status of Bazel 2.2.0
To report a release-blocking bug, please file a bug using the
Release blocker
label, and cc me.Task list:
The text was updated successfully, but these errors were encountered: