[v1.6.0] Release Schedule and Tracker
Maintainer antworten meist innerhalb von 1 Tag
@JacobSzwejbka arbeitet bereits daran.
Seit 08.10.2026.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
🚀 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:
- Critical fixes in core components: build, exir, backends, runtime, sdk
- Bug fixes in demos/examples. No new features or experiments
- Critical bug fixes based on community feedback
- Documentation improvements
- Test/CI fixes
- 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
- Ensure your PR has landed in main. This does not apply to release-branch-specific changes.
- Create, but do not land, a PR against the release branch using one of the options below.
- 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
- Vorherrschende Sprache
- Python
- Sterne
- 5.1k
- Forks
- 1.2k
- Ø Merge
- 1 T. 18 Std.
- Gemergte PRs (30 T.)
- 668
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus pytorch/executorch
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
pytorch/executorch#24434 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
pytorch/executorch#24410 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement triaged
Schwierigkeit 2/5 Ein halber Tag Anfängerfreundlichkeit 68/100
pytorch/executorch#21640 ·
Maintainer antworten meist innerhalb von 1 Tag
-
`install_executorch.sh` fails in a fresh uv virtual environment: `No module named pip`Evtl. vergeben Ein verknüpfter Pull Request ist offen oder bereits gemergt. Offen
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 45/100
pytorch/executorch#24417 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[CPU] Complex scalar broadcasting fails or returns incorrect resultsEvtl. vergeben @SofianElmotiem hat das heute übernommen. Offen
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
pytorch/executorch#24408 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in pytorch/executorch
Ähnliche Issues
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 78/100
521xueweihan/HelloGitHub#4237 ·
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
jejjohnson/gaussx#721 ·
Maintainer antworten meist innerhalb von 1 Tag
-
mock-core-configs/etc/mock/rocky-10-riscv64.cfg contains the wrong architecture in config_opts['root']Evtl. vergeben @jasonmontleon hat das vor 4 Tagen übernommen. Offen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 94/100
rpm-software-management/mock#1834 ·
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 75/100
elastic/elastic-otel-python#683 ·
Maintainer antworten meist innerhalb von 1 Tag
-
ci-rerun: collect.py fails a whole pr-babysit cycle on one transient GitHub 5xx and never retriesOffenfollow-up
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
Maintainer antworten meist innerhalb von 1 Tag