executorch
executorch copied to clipboard
[v0.2.1] Release Tracker
The v0.2.1 release will be cut from the "release/0.2" branch for critical fixes to the v0.2.0 release. Date TBD
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/experiments
- Critical bug fixes based on community feedback
- Documentation improvements
- Test/CI fixes
- Release branch specific changes (e.g. change version identifiers)
Any core components changes and other change will require special dispensation from the release managers (currently @guangy10 @mergennachin @dbort ). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
Cherry-Pick Process
-
Ensure your PR has landed in master. This does not apply for release-branch specific changes (see Phase 1 criteria).
-
Create (but do not land) a PR against the release branch. Option 1: Use
pytorchbot
to cherry pick a PR that has been committed to the main branch using@pytorchbot cherry-pick
command as follows.@pytorchbot cherry-pick --onto release/0.2 -c {regression,critical,fixnewfeature,docs,release}
usage: @pytorchbot cherry-pick --onto ONTO [--fixes FIXES] -c {regression,critical,fixnewfeature,docs,release} Cherry pick a pull request onto a release branch for inclusion in a release optional arguments: --onto ONTO Branch you would like to cherry pick onto (Example: release/0.2) --fixes FIXES Link to the issue that your PR fixes (i.e. https://github.com/pytorch/executorch/issues/2345) -c {regression,critical,fixnewfeature,docs,release} A machine-friendly classification of the cherry-pick reason.
Option 2: Manually create a cherry pick PR using git command as follows.
# Find the hash of the commit you want to cherry pick # (for example, abcdef12345) git log git fetch origin release/0.2 git checkout release/0.2 git cherry-pick -x abcdef12345 # Submit a PR based against 'release/0.2' either: # via the GitHub UI git push my-fork # via the GitHub CLI gh pr create --base release/0.2
-
Make a request below with the following format:
Link to landed trunk PR:
*
Link to release branch PR:
*
Criteria category and reasons:
*
- Someone from the release team will reply with approved / denied or ask for more information.
- If approved, someone from the release team will merge your PR once the tests pass. Do not land the release branch PR yourself.
Please note HUD Link with branch CI status and link to the HUD to be provided here. HUD
Versions
0.2.1
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3298
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3431
Criteria category and reasons:
- cmake file fix to make sdk tutorial work
@dbort: Since this makes code changes, don't merge this until closer to the 0.2.1 launch. Users are still instructed to check out the v0.2.0 tag, which won't contain this PR. And any docs changes that rely on this code change will break for those users.
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3391
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3432
Criteria category and reasons:
- Unbreak the cmake commands in sdk tutorial. This should be cherry-picked after the cherry-pick right above (the #3431 )
@dbort: Since this depends on code changes, don't merge this until closer to the 0.2.1 launch. Users are still instructed to check out the v0.2.0 tag, which won't contain the code changes. And any docs changes that rely on this code change will break for those users.
@Gasoonjia Merged into 0.2.1
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3438
Link to release branch PR:
- #3492
Criteria category and reasons:
- doc: simplify SDK tutorial doc
@dbort: Since this depends on code changes, don't merge this until closer to the 0.2.1 launch. Users are still instructed to check out the v0.2.0 tag, which won't contain the code changes. And any docs changes that rely on this code change will break for those users.
@Gasoonjia merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3152
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3175
Criteria category and reasons: Unblock nanogpt for dynamic export
@dbort merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3490
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3506
Criteria category and reasons: A bug for the backend delegate, hopefully it can be cherry picked soon. Fortunately no in tree backends are using it, but there are a few new out tree backends and I'm afraid they might use it.
@dbort merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3507
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3512
Criteria category and reasons:
- Fix #3502
@mcr229 merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3612
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3813
Criteria category and reasons:
- Fixes a pte export issue in some environments
@mergennachin merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3719
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3722
Criteria category and reasons:
- Documentation improvements
@mcr229 merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3736
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3738
Criteria category and reasons:
- Fixes a top-level documentation ordering. It's been a bit confusing.
@mcr229 merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3739
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3778
Criteria category and reasons:
- Replace buck with cmake for all docs
@mcr229 merged
Link to landed trunk PR:
- (None) This is Release Only PR to update third-party/pytorch
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3789
Criteria category and Reason:
- Since Pinning to PyTorch 2.3.1, we should update our third-party/PyTorch dep to match
@mergennachin merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3759
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3791
Criteria category and reasons:
Doc improvement based on users feedback
@mcr229 merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3782
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3806
Criteria category and reasons:
Doc improvement based on users feedback
@mergennachin merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3787
(seems like this is already merged into
release/0.2
?)
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3787
Criteria category and reasons:
Fix torch and torchaudio torchvision not compatible issue.
@mergennachin no action necessary, already merged into release branch
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3798
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3807
Criteria category and reasons:
- Doc improvement
@Gasoonjia merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3809
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3815/
Criteria category and reasons:
Bug fix
@Gasoonjia merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3816
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3817
Criteria category and reasons:
- Docs updates
@dbort merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3810
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3820
Criteria category and reasons:
- Bug fixes in demos/examples. This allows us to build prebuilt android package for release branch as well, so that users can use it.
@mcr229 merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3381
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3837
Criteria category and reasons:
- Bug fix. Fix a CI issue in release branch. Some setup is missing when we land https://github.com/pytorch/executorch/pull/3820
@Gasoonjia merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3840
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3841
Criteria category and reasons:
- Documentation and example improvements.
@Gasoonjia merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3847
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3852
Criteria category and reasons:
- Arm CI fix
@Gasoonjia merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3845
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3857
Criteria category and reasons:
- Update Docs for Quant
@Gasoonjia merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3855
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3862
Criteria category and reasons:
- Documentation improvements
@Gasoonjia merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3861
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3871
Criteria category and reasons:
- Doc fix
@mergennachin merged
Link to landed Trunk PR:
- Release Only PR
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3872
Criteria category and reason:
- Update docs for release
@mcr229 merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3879
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3881
Criteria category and reasons:
- docs
@mergennachin merged
Link to landed trunk PR:
- https://github.com/pytorch/executorch/pull/3885
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/3889
Criteria category and reasons:
- Documentation improvement for setup.
@mcr229 merged
Closing
https://github.com/pytorch/executorch/releases/tag/v0.2.1
https://pypi.org/project/executorch/0.2.1/