Skip to content

[v.2.7.0] Release Tracker #149044

@atalman

Description

@atalman

We cut a release branch for the 2.7.0 release.

Our plan from this point from this point is roughly:

  • Phase 1 (until 3/31/25): work on finalizing the release branch
  • Phase 2 (after 3/31/25): 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 3/31/25):

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

  1. Fixes to regressions against the most recent minor release (e.g. 2.6.x for this release; see module: regression issue list)
  2. Critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
  3. Critical fixes to new features introduced in the most recent minor release (e.g. 2.6.x for this release)
  4. Test/CI fixes
  5. Documentation improvements
  6. Compilation fixes or ifdefs required for different versions of the compilers or third-party libraries
  7. Release branch specific changes (e.g. change version identifiers)

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

Phase 2 (after 3/31/25):

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.

    Details
    # Find the hash of the commit you want to cherry pick
    # (for example, abcdef12345)
    git log
    
    git fetch origin release/2.7
    git checkout release/2.7
    git cherry-pick -x abcdef12345
    
    # Submit a PR based against 'release/2.7' either:
    # via the GitHub UI
    git push my-fork
    
    # via the GitHub CLI
    gh pr create --base release/2.7

    You can also use the @pytorchbot cherry-pick command to cherry-pick your PR. To do this, just add a comment in your merged PR. For example:

    @pytorchbot cherry-pick --onto release/2.7 -c docs
    

    (-c docs - is the category of your changes - adjust accordingly):

    For more information, see pytorchbot cherry-pick docs.

  3. Make a request below with the following format:

Link to landed trunk 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.

Please note HUD Link with branch CI status and link to the HUD to be provided here.
HUD

Download instructions for testing release candidate

PIP CPU

Windows/Linux/MacOS:
pip3 install torch==2.7.0 torchvision torchaudio --index-url https://download.pytorch.org/whl/test/cpu

PIP CUDA 11.8, 12.6, 12.8

Windows/Linux:
pip3 install torch==2.7.0 torchvision torchaudio --index-url https://download.pytorch.org/whl/test/cu118
pip3 install torch==2.7.0 torchvision torchaudio --index-url https://download.pytorch.org/whl/test/cu126
pip3 install torch==2.7.0 torchvision torchaudio --index-url https://download.pytorch.org/whl/test/cu128

PIP Linux Aarch6

pip3 install torch==2.7.0 torchvision torchaudio --extra-index-url https://download.pytorch.org/whl/test/cpu

PIP Linux CUDA 12.8 Aarch64

pip3 install torch==2.7.0 torchvision torchaudio --extra-index-url https://download.pytorch.org/whl/test/cu128

PIP ROCM 6.2.4

pip3 install torch==2.7.0 torchvision torchaudio --index-url https://download.pytorch.org/whl/test/rocm6.2.4

PIP ROCM 6.3

pip3 install torch==2.7.0 torchvision torchaudio --index-url https://download.pytorch.org/whl/test/rocm6.3

PIP XPU

Linux/Windows:
pip3 install torch==2.7.0 torchvision torchaudio --index-url https://download.pytorch.org/whl/test/xpu

Libtorch

CPU Linux:
(cxx11 ABI): https://download.pytorch.org/libtorch/test/cpu/libtorch-cxx11-abi-shared-with-deps-latest.zip

CPU Windows:
Download here (Release version): https://download.pytorch.org/libtorch/test/cpu/libtorch-win-shared-with-deps-latest.zip
Download here (Debug version): https://download.pytorch.org/libtorch/test/cpu/libtorch-win-shared-with-deps-debug-latest.zip

CPU MacOS Arm64:
https://download.pytorch.org/libtorch/nightly/cpu/libtorch-macos-arm64-latest.zip

CUDA 11.8, 12.6, 12.8 Linux
https://download.pytorch.org/libtorch/test/cu118/libtorch-cxx11-abi-shared-with-deps-latest.zip
https://download.pytorch.org/libtorch/test/cu126/libtorch-cxx11-abi-shared-with-deps-latest.zip
https://download.pytorch.org/libtorch/test/cu128/libtorch-cxx11-abi-shared-with-deps-latest.zip

Windows CUDA 11.8, 12.6, 12.8

(Release version):
https://download.pytorch.org/libtorch/test/cu118/libtorch-win-shared-with-deps-latest.zip
https://download.pytorch.org/libtorch/test/cu126/libtorch-win-shared-with-deps-latest.zip
https://download.pytorch.org/libtorch/test/cu128/libtorch-win-shared-with-deps-latest.zip

(Debug version):
https://download.pytorch.org/libtorch/test/cu118/libtorch-win-shared-with-deps-debug-latest.zip
https://download.pytorch.org/libtorch/test/cu126/libtorch-win-shared-with-deps-debug-latest.zip
https://download.pytorch.org/libtorch/test/cu128/libtorch-win-shared-with-deps-debug-latest.zip

Docker images CUDA 11.8, 12.6, 12.8

Devel:
docker pull ghcr.io/pytorch/pytorch-test:2.7.0-cuda11.8-cudnn9-devel
docker pull ghcr.io/pytorch/pytorch-test:2.7.0-cuda12.6-cudnn9-devel
docker pull ghcr.io/pytorch/pytorch-test:2.7.0-cuda12.8-cudnn9-devel

Runtime:
docker pull ghcr.io/pytorch/pytorch-test:2.7.0-cuda11.8-cudnn9-runtime
docker pull ghcr.io/pytorch/pytorch-test:2.7.0-cuda12.6-cudnn9-runtime
docker pull ghcr.io/pytorch/pytorch-test:2.7.0-cuda12.8-cudnn9-runtime

cc @seemethere @malfet @pytorch/pytorch-dev-infra

Versions

2.7.0

Metadata

Metadata

Labels

module: ciRelated to continuous integrationrelease trackerAdd this label to release tracker issuestriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions