[v1.5.0] Release Schedule and Tracker
Los mantenedores suelen responder en 1 día
@JacobSzwejbka ya está trabajando en esto.
Desde el 26/8/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
🚀 The feature, motivation and pitch
[v1.5.0] Release Schedule and Tracker
The v1.5.0 release will be cut from the release/1.5 branch for critical fixes to the v1.5.0 release.
- Branch Cut Date: Thursday, September 3, 2026
- Tokenizers Release Date: Tuesday, September 8, 2026
- Release branch finalized, documentation and tutorials finalized: Wednesday, September 9, 2026 (last day)
- Intended Release Date: Monday, September 14, 2026
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 (@JacobSzwejbka, @rascani). 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.
-
Option 1: Use pytorchbot to cherry-pick a PR committed to the main branch:
-
@pytorchbot cherry-pick --onto release/1.5 -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.5)
- --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.5
- git checkout release/1.5
- git cherry-pick -x
-
Push the branch to your fork and open a PR based against release/1.5,
-
either through the GitHub UI or with:
- gh pr create --base release/1.5
- Submit a request in a comment below using this format:
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.5.0
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
- Lenguaje dominante
- Python
- Estrellas
- 5.1k
- Forks
- 1.2k
- Merge medio
- 2 d 9 h
- PR fusionados (30 d)
- 661
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pytorch/executorch
-
enhancement triaged
Dificultad 2/5 Medio día Aptitud para principiantes 68/100
pytorch/executorch#21640 ·
Los mantenedores suelen responder en 1 día
-
Prompts of max_seq_len tokens fail to prefill: export_llm bounds the KV-cache token input at max_seq_len - 1 but publishes get_max_seq_len = max_seq_lenPosiblemente ocupada @alpharomercoma la tomó hoy. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 20/100
pytorch/executorch#23678 ·
Los mantenedores suelen responder en 1 día
-
[v1.6.0] Release Schedule and TrackerPosiblemente ocupada @JacobSzwejbka la tomó hace 2 días. Abierto
pytorch/executorch#23608 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
QNN sharded LLM export fails: ResolveDebugHandle is not the last edge pass (dep_table entry overwritten by SplitGraph registration)Posiblemente ocupada @psiddh la tomó hace 2 días. Abiertobug module: llm module: qnn triaged
pytorch/executorch#23580 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
pytorch/executorch#23553 ·
Los mantenedores suelen responder en 1 día
Todos los issues de pytorch/executorch
Issues similares
-
Update Python support to 3.15Abiertopython-version
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
bug javascript P2-medium python release:v3.1
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
adrirubio/claude-deck#546 ·
Los mantenedores suelen responder en 1 día
-
area: desktop area: website priority: P2 type: feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
appandflow/stim#3411 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 Menos de una hora Aptitud para principiantes 88/100
baptistehamon/lsapy#185 ·
Los mantenedores suelen responder en 1 día