Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[v1.6.0] Release Schedule and Tracker

オープン
  • 何か問題がありますか？
#23,608 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@JacobSzwejbka がすでに取り組んでいます。

2026年10月8日 から。

評価

この issue はまだ評価されていません。

説明

🚀 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: Thursday, October 29, 2026

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

主要言語
Python
スター
5.1k
フォーク
1.2k
平均マージ
2日 10時間
マージ済み PR（30日）
632

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

pytorch/executorch のほかの issue

pytorch/executorch の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。