[v1.7.0] Release Tracker

We cut a release branch for the 1.7.0 release.

Our plan from this point is roughly:

  • Phase 1 (until 10/13): work on finalizing the release branch
  • Phase 2 (after 10/13): perform extended integration/stability/performance testing based on Release Candidate builds.

This issue is for tracking cherry-picks to the release branch.

Cherry-Pick Criteria

Phase 1 (until 10/13):

Only low-risk changes may be cherry-picked from master:

  1. Fixes to regressions against PyTorch 1.0+
  2. Critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
  3. Fixes to new features being introduced in this release
  4. Compilation fixes or ifdefs required for different versions of the compilers or third-party libraries
  5. Test/CI fixes or improvements
  6. Documentation improvements
  7. Release branch specific changes (e.g. change version identifiers, remove/hide features that aren’t ready for release)

Any other change requires special dispensation from the release managers (currently @malfet, @seemethere, @gchanan). If this applies to your change please write “Special Dispensation” in the “Criteria Category:” template below and explain.

Phase 2 (after 10/13):

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

This 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. Note that you should use the normal github workflow for this; ghstack does not support release branches.

  3. Make a request below with the following template:

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. NOTE: do not land the release branch PR yourself. Our normal landing tools (ghimport, phabricator, etc.) do not work on the release branch.

Author: Fantashit

1 thought on “[v1.7.0] Release Tracker

  1. Link to landed master PR (if applicable): #46315
    Link to release branch PR: #46388
    Criteria Category: Test/CI fixes or improvements

    Avoid error when using Python 3.9 (e.g. clang-tidy CI)


    @malfet: merged and thank you for the pick

Comments are closed.