-
Notifications
You must be signed in to change notification settings - Fork 355
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
[v0.4.0] Release Tracker #5366
Comments
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
Link to landed trunk PR:
Link to release branch PR: Criteria category and reasons:
|
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: |
We can close this now that 0.4 is released |
The v0.4.0 release will be cut from the "release/0.4" branch for critical fixes to the v0.4.0 release.
Branch Cut Date: 09/15/2024
Intended Release Date: 10/17/2024
This issue is for tracking cherry-picks to the release branch.
Cherry-Pick Criteria
Focus on stability and documentation correctness. Ideally only low risk changes may be cherry-picked from main:
Any core components changes and other change will require special dispensation from the release managers (currently @vmpuri @dvorjackz). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
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.
Option 1: Use
pytorchbot
to cherry pick a PR that has been committed to the main branch using@pytorchbot cherry-pick
command as follows.Option 2: Manually create a cherry pick PR using git command as follows.
Make a request below with the following format:
Please note HUD Link with branch CI status and link to the HUD to be provided here.
HUD
Versions
0.4.0
The text was updated successfully, but these errors were encountered: