Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[v1.5.0] Release Schedule and Tracker

未关闭
  • 哪里不对？
#22,188 5 条评论 1 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@JacobSzwejbka 已经在做这个了。

开始于 2026年8月26日。

评估

这个 Issue 还没有评估数据。

描述

release tracker
🚀 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:

  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 (@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

  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.

  3. Option 1: Use pytorchbot to cherry-pick a PR committed to the main branch:

  4. @pytorchbot cherry-pick --onto release/1.5 -c {regression,critical,fixnewfeature,docs,release,examples,testci}

Command usage
  1. usage: @pytorchbot cherry-pick --onto ONTO [--fixes FIXES] -c
  2.                      {regression,critical,fixnewfeature,docs,release,examples,testci}
  4. Cherry-pick a pull request onto a release branch for inclusion in a release.
  6. optional arguments:
  7. --onto ONTO Branch to cherry-pick onto (example: release/1.5)
  8. --fixes FIXES Link to the issue fixed by the PR
  9. -c Machine-friendly classification of the cherry-pick reason
  1. Option 2: Manually create a cherry-pick PR:
Manual commands

  1. Find the hash of the commit to cherry-pick.

  2. git log
  4. git fetch origin release/1.5
  5. git checkout release/1.5
  6. git cherry-pick -x

  8. Push the branch to your fork and open a PR based against release/1.5,

  9. either through the GitHub UI or with:

  10. gh pr create --base release/1.5
  1. 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

主要语言
Python
星标
5.1k
派生
1.2k
平均合并
2 天 8 小时
30 天内合并 PR
610

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

pytorch/executorch 的其他 Issue

查看 pytorch/executorch 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。