-
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 5.3 - August 2022 #15685
Comments
Hello 👋 general question on release cadence - #15682 is a bug in 5.2.0. Should it be picked into a 5.2.x patch release, or is 5.3.0 is the patch release? Just wanted to make sure whichever release it lands only contains the bug fixes, and no new development. |
Hello - there is a ticket #15762 .Are you also planning to pick it for the next patch release |
@wisechengyi We have already cherry picked the fix that is addressing this issue to release-5.3.0. At this point we are not planing to perform any patch release. |
@ananta-code Since we are not planing for any patch release at this point, this will be cherry picked to release-5.3.0. |
Context: we recently run into an issue where we have a lot of rules_docker actions that zip/tar large blobs of container images. These actions can be quite expensive in memory consumption and require fine tuning to avoid they all run in parallel together, which trigger kernel's OOM killer. Having Edit: created #15968 to discuss this Edit2: it seems like the change was included as part of this squashed commit 78af34f Sorry for the noise, thanks for the amazing work 🙇♂️ |
Hello all, we have decided to push the release date to 08/15/2022. Just wanted to keep you all updated. Thanks! |
Ran 5.3 RC1 on our build against our remote execution cluster and it fails to run tests. #16003 is the bug I filed. This is a regression from 5.0, which worked with the exact same version of the code being built and the exact same command. |
Hi @AustinSchuh, we are awaiting review on 16008 which fixes the issue. |
Hello @AustinSchuh! Just an update, as 16008 fixes the issue, it has been reviewed and merged to release 5.3.0. Thanks! |
I would like to put forward #16095 a trivial change to add support for java language level 17 to the linux-aarch64 platform |
Will there be a 5.3.0rc2 before the final release? |
Hi @dws! yes, we are going to announce 5.3.0rc2 before the final release. Thanks! |
I see. Is there a branch cut for this next release, to open PRs against? |
Hi @nresare! Not as of yet, we will be cutting the branch for next release after this release. Thanks! |
5.3 is now out! @petemounce @excitoon @vbatts Could you please update relevant package managers? Thanks! |
@ckolli5 I don't see this listed in the 5.3 release notes. Can you confirm the fix has been included? Both #15762 and #15865 are still open. |
#16008 (comment) is a first report of a 5.3.0 regression my fix for #16003 introduced - the existing tests didn't cover local execution. |
Hi @dan-cohn-sabre! As we are working on it, we will keep you updated of any progress. Thanks! |
Hi @ananta-code ! As this issue is marked as P3, we don't have any resource to work on this. Please feel free to send PR. Thanks! |
5.3.1 is now out! @vbatts @petemounce @excitoon Could you please update relevant package managers? Thanks! |
Done, both; apologies for delay. @kshyanashree - who can I talk to to integrate the chocolatey build & push into bazel CI? It requires:
|
@meteorcloudy FYI, we could maybe look into this |
@petemounce Thanks! I filed an issue to track this: bazelbuild/continuous-integration#1456 |
5.3.2 is now out! @petemounce @excitoon @vbatts Could you please update relevant package managers? Thanks! |
Done. Ping on bazelbuild/continuous-integration#1456 |
Status of Bazel 5.3
To report a release-blocking bug, please add a comment with the text
@bazel-io flag
to the issue. A release manager will triage it and add it to the milestone.To cherry-pick a mainline commit into 5.3, simply send a PR against the
release-5.3.0
branch.Task list:
The text was updated successfully, but these errors were encountered: