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
[v.1.13.1] Release Tracker #89855
Comments
can we include this security fix as well? #88868 |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@malfet merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
Update:
|
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category: @atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@izaitsevfb merged |
Link to landed master PR (if applicable): Link to release branch PR: Issue fixed: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Issue fixed: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable):
Link to release branch PR: Criteria Category:
@malfet: merged |
Link to landed master PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman reviewed: According to following comment #89261 (comment) this is not a hi-priority issue. We are 2 days away from the release, at this point we can accept only Critical and high priority fixes to avoid a delay with this release. @malfet: Test bundled with the PR does not confirm it is a regression from previous release, see #89299 (comment) @kevalmorabia97: Fixed the test case to verify this is a regression. Do we want to merge this PR now? @atalman: Please note: merging this fix would require us to delay the release, and repeat all the testing we have done before this release. We only allow to do it for critical hi-priority fixes. According to the comments on the PR this is not hi priority issue. |
Please note, we don't accept cherry-picks anymore. The release is scheduled on Dec 15 to go live. |
Closing the issue tracker since release is live |
We cut a release branch for the 1.13.1 release.
Our plan from this point from this point is roughly:
This issue is for tracking cherry-picks to the release branch.
Cherry-Pick Criteria
Phase 1 (until 12/8/2022):
Only low-risk changes may be cherry-picked from master:
Any other change requires special dispensation from the release managers (currently @malfet, @atalman, @weiwangmeta , @izaitsevfb). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
Phase 2 (after 12/15/2022):
Note that changes here require us to rebuild a Release Candidate and restart extended testing (likely delaying the release). Therefore, the only accepted changes are Release-blocking critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
Changes will likely require a discussion with the larger release team over VC or Slack.
Cherry-Pick Process
Ensure your PR has landed in master. This does not apply for release-branch specific changes (see Phase 1 criteria).
Create (but do not land) a PR against the release branch.
Make a request below with the following format:
NOTE: Our normal tools (ghstack / ghimport, etc.) do not work on the release branch.
See HUD 1.13
The text was updated successfully, but these errors were encountered: