Skip to content
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

Closed
atalman opened this issue Nov 29, 2022 · 26 comments
Closed

[v.1.13.1] Release Tracker #89855

atalman opened this issue Nov 29, 2022 · 26 comments
Labels
triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Milestone

Comments

@atalman
Copy link
Contributor

atalman commented Nov 29, 2022

We cut a release branch for the 1.13.1 release.

Our plan from this point from this point is roughly:

  • Phase 1 (until 12/8): Release Candidate 1
  • Phase 2 (until 12/15): Tentative General Availability

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:

  1. Fixes to regressions against previous major version (e.g. regressions introduced in 1.13.0 from 1.12.0 are pickable for 1.13.1)
  2. Critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
  3. Fixes to new features being introduced in this release
  4. Documentation improvements
  5. Release branch specific changes (e.g. blocking ci fixes, change version identifiers)

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

  1. Ensure your PR has landed in master. This does not apply for release-branch specific changes (see Phase 1 criteria).

  2. Create (but do not land) a PR against the release branch.

    # Find the hash of the commit you want to cherry pick
    # (for example, abcdef12345)
    git log
    
    git fetch origin release/1.13
    git checkout release/1.13
    git cherry-pick abcdef12345
    
    # Submit a PR based against 'release/1.10' either:
    # via the GitHub UI
    git push my-fork
    
    # via the GitHub CLI
    gh pr create --base release/1.13
  3. Make a request below with the following format:

Link to landed master PR (if applicable):
* 

Link to release branch PR:
* 

Criteria Category:
* 
  1. Someone from the release team will reply with approved / denied or ask for more information.
  2. If approved, someone from the release team will merge your PR once the tests pass. Do not land the release branch PR yourself.

NOTE: Our normal tools (ghstack / ghimport, etc.) do not work on the release branch.

See HUD 1.13

@atalman atalman added this to the 1.13.1 milestone Nov 29, 2022
@atalman atalman pinned this issue Nov 29, 2022
@roywei
Copy link

roywei commented Nov 29, 2022

can we include this security fix as well? #88868

@atalman
Copy link
Contributor Author

atalman commented Nov 30, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • Documentation change

@atalman merged

@atalman
Copy link
Contributor Author

atalman commented Nov 30, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • Critical Fix

@atalman merged

@atalman
Copy link
Contributor Author

atalman commented Nov 30, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • Critical security fix

@malfet merged

@weiwangmeta
Copy link
Contributor

weiwangmeta commented Nov 30, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • To be updated

Update:

@weiwangmeta
Copy link
Contributor

weiwangmeta commented Nov 30, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • Critical fix

@atalman merged

@weiwangmeta
Copy link
Contributor

weiwangmeta commented Nov 30, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • To be updated

@atalman merged

@weiwangmeta
Copy link
Contributor

weiwangmeta commented Nov 30, 2022

@charlie-wt
Copy link
Contributor

charlie-wt commented Dec 1, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria category:

  • 2: Prevents a crash, which was introduced here, tagged for 1.13

@atalman merged

@charlie-wt
Copy link
Contributor

charlie-wt commented Dec 1, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • 2: This affects correct behaviour of IPU tensors, in the out-of-tree IPU backend.

@atalman merged

@charlie-wt
Copy link
Contributor

charlie-wt commented Dec 1, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • 2: This affects correct behaviour of IPU tensors, in the out-of-tree IPU backend.

@atalman merged

@drisspg drisspg added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Dec 1, 2022
@izaitsevfb
Copy link
Contributor

izaitsevfb commented Dec 2, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • Regression

@izaitsevfb merged

@izaitsevfb
Copy link
Contributor

izaitsevfb commented Dec 2, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Issue fixed:

Criteria Category:

  • Regression

@atalman merged

@weiwangmeta
Copy link
Contributor

weiwangmeta commented Dec 2, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Issue fixed:

Criteria Category:

  • Regression

@atalman merged

@izaitsevfb
Copy link
Contributor

izaitsevfb commented Dec 3, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • Regression

@atalman merged

@atalman
Copy link
Contributor Author

atalman commented Dec 6, 2022

Link to landed master PR (if applicable):

  • NA

Link to release branch PR:

Criteria Category:

  • Release only change fixes, failing tests

@atalman merged

@atalman
Copy link
Contributor Author

atalman commented Dec 6, 2022

Link to landed master PR (if applicable):

  • NA

Link to release branch PR:

Criteria Category:

  • Release only, Critical CI fix (Rocm 5.1.1)

@atalman merged

@atalman
Copy link
Contributor Author

atalman commented Dec 7, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • Critical CI fix - builder repo

@atalman merged

@atalman
Copy link
Contributor Author

atalman commented Dec 7, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • Critical Fix, amazon linux 2 installation failure

@atalman merged

@atalman
Copy link
Contributor Author

atalman commented Dec 8, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • Critical fix for release, limiting produced binary size

@atalman merged

@malfet
Copy link
Contributor

malfet commented Dec 9, 2022

Link to landed master PR (if applicable):

  • NA

Link to release branch PR:

Criteria Category:

  • Release specific CI fixes (uses the same xla hash for build and test)

@malfet: merged

@atalman
Copy link
Contributor Author

atalman commented Dec 9, 2022

Link to landed master PR (if applicable):

  • NA

Link to release branch PR:

Criteria Category:

  • Release only change, turn off test that was enabled just before 1.13.1 but disabled for 1.13.0

@atalman merged

@roywei
Copy link

roywei commented Dec 11, 2022

Hi, request to fix this installation issue for 1.13.1, thanks a lot!
#90673


@atalman wrote: Yes, this should be resolved now.

@kevalmorabia97
Copy link
Contributor

kevalmorabia97 commented Dec 12, 2022

Link to landed master PR (if applicable):

Link to release branch PR:

Criteria Category:

  • Bug fix: regression with previous releases

@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.

@atalman
Copy link
Contributor Author

atalman commented Dec 14, 2022

Please note, we don't accept cherry-picks anymore. The release is scheduled on Dec 15 to go live.

@atalman
Copy link
Contributor Author

atalman commented Dec 15, 2022

Closing the issue tracker since release is live

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Development

No branches or pull requests

8 participants