[v0.2.1] Release Tracker

[dbort]

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:

1. Critical fixes in core components: build, exir, backends, runtime, sdk
2. Bug fixes in demos/examples. No new features/experiments
3. Critical bug fixes based on community feedback
4. Documentation improvements
5. Test/CI fixes
6. 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

1. Ensure your PR has landed in master. This does not apply for release-branch specific changes (see Phase 1 criteria).

2. 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
   
   

3. Make a request below with the following format:

Link to landed trunk PR:
* 

Link to release branch PR:
* 

Criteria category and reasons:
* 

1. Someone from the release team will reply with approved / denied or ask for more information.
2. 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

[Olivia-liu]

Link to landed trunk PR:

• Fix sdk_example_runner.sh #3298

Link to release branch PR:

• Fix sdk_example_runner.sh #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.

[Olivia-liu]

Link to landed trunk PR:

• Fix the broken cmake commands in sdk integration tutorial #3391

Link to release branch PR:

• Fix the broken cmake commands in sdk integration tutorial #3432

Criteria category and reasons:

• Unbreak the cmake commands in sdk tutorial. This should be cherry-picked after the cherry-pick right above (the Fix sdk_example_runner.sh #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.

[Olivia-liu]

Link to landed trunk PR:

• Simplify SDK tutorial by moving cmake commands to a script #3438

Link to release branch PR:

• Simplify SDK tutorial by moving cmake commands to a script #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]

Link to landed trunk PR:

• make op_split_with_sizes_copy support dynamic shape #3152

Link to release branch PR:

• make op_split_with_sizes_copy support dynamic shape #3175

Criteria category and reasons:
Unblock nanogpt for dynamic export

---

@dbort merged

[cccclai]

Link to landed trunk PR:

• fix the temp allocator for backend #3490

Link to release branch PR:

• fix the temp allocator for backend #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

[dbort]

Link to landed trunk PR:

• Only unset HOME when running cmake as root #3507

Link to release branch PR:

• Only unset HOME when running cmake as root #3512

Criteria category and reasons:

• Fix Buck 2 Error on running ./install_requirements.sh #3502

[dbort]

Link to landed trunk PR:

• Ignore the FLATC_EXECUTABLE env var when empty #3612

Link to release branch PR:

• PLACEHOLDER

Criteria category and reasons:

• Fixes a pte export issue in some environments