[v1.6.0] Release Schedule and Tracker

Ouverte
  • Quelque chose ne va pas ?
#23,608 32 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@JacobSzwejbka y travaille déjà.

Depuis le 8/10/2026.

  • #24198 par @JacobSzwejbka — ouverte
  • #24199 par @JacobSzwejbka — ouverte

Évaluation

Cette issue n'a pas encore été évaluée.

Description

🚀 The feature, motivation and pitch

[v1.6.0] Release Schedule and Tracker

The v1.6.0 release will be released from the release/1.6 branch. After branch cut, this branch will accept fixes according to the cherry-pick criteria below.

Release Schedule

  • Branch Cut Date: Friday, October 16, 2026
  • Release branch finalized, documentation and tutorials finalized: Wednesday, October 21, 2026 (last day; proposed)
  • Intended Release Date: Friday, October 30, 2026 (delayed by one day from October 29)

The intended release date follows the PyTorch 2.15 release schedule. If the PyTorch release moves, the ExecuTorch release target will move to the following calendar day.

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:

  1. Critical fixes in core components: build, exir, backends, runtime, sdk
  2. Bug fixes in demos/examples. No new features or experiments
  3. Critical bug fixes based on community feedback
  4. Documentation improvements
  5. Test/CI fixes
  6. Release-branch-specific changes (for example, version identifier changes)

Any core component changes or other changes require special dispensation from the release managers. If this applies to your change, write Special Dispensation in the Criteria category and reasons: section of the template below and explain why it should be included.

Cherry-Pick Process

  1. Ensure your PR has landed in main. This does not apply to release-branch-specific changes.
  2. Create, but do not land, a PR against the release branch using one of the options below.
  3. Submit a request in a comment on this issue using the request template below.
Option 1: Use pytorchbot

Use pytorchbot to cherry-pick a PR committed to the main branch. Comment on that PR, selecting the appropriate category:

@pytorchbot cherry-pick --onto release/1.6 -c {regression,critical,fixnewfeature,docs,release,examples,testci}
Command usage 
usage: @pytorchbot cherry-pick --onto ONTO [--fixes FIXES] -c
                              {regression,critical,fixnewfeature,docs,release,examples,testci}

Cherry-pick a pull request onto a release branch for inclusion in a release.

optional arguments:
  --onto ONTO    Branch to cherry-pick onto (example: release/1.6)
  --fixes FIXES  Link to the issue fixed by the PR
  -c            Machine-friendly classification of the cherry-pick reason
Option 2: Manually create a cherry-pick PR
Manual commands 
# Find the hash of the commit to cherry-pick.
git log

git fetch origin release/1.6
git checkout -b cherry-pick-for-1.6 origin/release/1.6
git cherry-pick -x <commit>

# Push the branch to your fork and open a PR based against release/1.6,
# either through the GitHub UI or with:
git push <fork-remote> cherry-pick-for-1.6
gh pr create --repo pytorch/executorch --base release/1.6
Cherry-Pick Request Template
Link to landed trunk PR:
*

Link to release branch PR:
*

Criteria category and reasons:
*

Someone from the release team will approve, deny, or request more information. If approved, the release team will merge the PR after tests pass. Do not land the release-branch PR yourself.

If the release team has acted on a cherry-pick request, its comment will be liked. Once the cherry-pick has merged, a rocket reaction will be added to the comment.

Release branch CI: HUD

Version

1.6.0

Alternatives

No response

Additional context

No response

RFC (Optional)

No response

Langage dominant
Python
Étoiles
5.1k
Forks
1.2k
Merge moyen
1 j 18 h
PR mergées (30 j)
668

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de pytorch/executorch

Toutes les issues de pytorch/executorch

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.