[v0.2.0] Release Tracker

[guangy10]

The v0.2.0 release has been cut, and this issue is closed. Use #3409 for cherry-picking into the v0.2.1 release.

---

v0.2.0 release branch was cut. The branch name is "release/0.2", with tag "v0.2.0-rc4" atm.

Our release plan from this point is roughly:

• Phase 1 (until 4/5/24):
  -- work on finalizing the release branch for stability for soft-launch.
  -- initial set of documentations and reproducible instructions, including Llama.
  -- apply release-branch specific changes (changes not in main but directly in release/0.2 branch like pins).
  -- Coordinate with PyTorch v2.3 release milestones, and prioritize to get PyTorch PRs needed by ExecuTorch v0.2.0 cherry-picked into PyTorch release v2.3.0. It will be very hard to do so after 04/01.

• Phase 2 (after 4/5/24, until 4/24/24 by 12:00pm PDT):
  -- perform extended integration/stability/performance testing based on Release Candidate builds.
  -- fix critical bugs based on early feedback from our soft-launch
  -- enhance our documentation.

This issue is for tracking cherry-picks to the release branch.

Cherry-Pick Criteria

Focus on stability. 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.0

[GregoryComer]

Link to landed trunk PR:

• Restore CMake configure comment #2723

Link to release branch PR:

• Restore CMake configure comment #2749

Criteria category and reasons:

• Docs: Restore build instructions in CMakeLists.txt top-level comment.

---

@guangy10 merged via fast-forward.

[kirklandsign]

Link to landed trunk PR:

• Update docs #2919

Link to release branch PR:

• Update docs #2923

Criteria category and reasons:

• Documentation improvements. Better readability for markdown.

---

@guangy10 merged

[kirklandsign]

Link to landed trunk PR:

• [Android] Use unified path /data/local/tmp/llama #2899

Link to release branch PR:

• [Android] Use unified path /data/local/tmp/llama #2924

Criteria category and reasons:

• Documentation improvements. For Android, only use path /data/local/tmp/llama to avoid confusion.

---

@guangy10 merged

[GregoryComer]

Link to landed trunk PR:

• Refine LLM getting started guide for uniformity, fix critical errors #2911

Link to release branch PR:

• Refine LLM getting started guide for uniformity, fix critical errors #2939

Criteria category and reasons:

• Documentation improvements and critical fixes for LLM getting started guide.

---

@mergennachin merged

[mergennachin]

Link to landed trunk PR:

• Update iphone 15 pro benchmarking numbers #2927

Link to release branch PR:

• Update iphone 15 pro benchmarking numbers #2929

Criteria category and reasons:

• Update documentation for Llama2

---

@mergennachin merged

[mergennachin]

Link to landed trunk PR:

• Fixing minor issues in llama2 7b repro #2926

Link to release branch PR:

• Fixing minor issues in llama2 7b repro #2941

Criteria category and reasons:

• Update documentation fix for Llama2

---

@mergennachin merged

[mergennachin]

Link to landed trunk PR:

• Update docs for the demo app. #2921

Link to release branch PR:

• Update docs for the demo app. #2942

Criteria category and reasons:

• Update documentation for Llama2

---

@mergennachin merged

[mergennachin]

Link to landed trunk PR:

• Fix generation speed calculation. #2932

Link to release branch PR:

• Fix generation speed calculation. #2943

Criteria category and reasons:

• Fix speed generation calculation for iLlama app

---

@mergennachin merged

[cccclai]

Link to landed trunk PR:

• exclude mutated buffer #2876

Link to release branch PR:

• exclude mutated buffer #2946

Criteria category and reasons:
Exclude mutable buffers in constant tagging

---

@mergennachin merged

[GregoryComer]

Link to landed trunk PR:

• Make minor updates to LLM guide setup instructions #2940

Link to release branch PR:

• Make minor updates to LLM guide setup instructions #2959

Criteria category and reasons:

• Documentation updates to LLM getting started guide to fix blockers in ExecuTorch installation on mac when not using Conda. Minor other doc fixes.

——-
@guangy10 merged

[GregoryComer]

Link to landed trunk PR:

• resolve_buck.py: Add an entry for darwin-x86_64 #2868

Link to release branch PR:

• resolve_buck.py: Add an entry for darwin-x86_64 #2960

Criteria category and reasons:

• Support auto-downloading buck from CMake on Intel Macs. Needed to streamline CMake builds in OSS, since without this, users will have to download the appropriate version of buck2 and explicitly pass in the path.

---

@mergennachin merged