Skip to content

[v0.2.0] Release Tracker  #2666

Closed
Closed
[v0.2.0] Release Tracker #2666
Labels
triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

Description

@guangy10
guangy10
opened on Mar 25, 2024

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}
    Details 
    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.

    Details 
    # 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

Activity

  1. guangy10
    added
    triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
    on Mar 25, 2024
  2. mergennachin
    pinned this issue on Mar 26, 2024

  3. GregoryComer commented on Mar 28, 2024

    @GregoryComer
    GregoryComer
    on Mar 28, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

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

    @guangy10 merged via fast-forward.

  4. mergennachin
    added a commit that references this issue on Apr 8, 2024

    Update docs for the demo app. (#2921)

    9ba8bc9

  5. kirklandsign commented on Apr 8, 2024

    @kirklandsign
    kirklandsign
    on Apr 8, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Documentation improvements. Better readability for markdown.

    @guangy10 merged

  6. kirklandsign commented on Apr 8, 2024

    @kirklandsign
    kirklandsign
    on Apr 8, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

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

    @guangy10 merged

  7. GregoryComer commented on Apr 9, 2024

    @GregoryComer
    GregoryComer
    on Apr 9, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

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

    @mergennachin merged

  8. mergennachin commented on Apr 9, 2024

    @mergennachin
    mergennachin
    on Apr 9, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Update documentation for Llama2

    @mergennachin merged

  9. mergennachin commented on Apr 9, 2024

    @mergennachin
    mergennachin
    on Apr 9, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Update documentation fix for Llama2

    @mergennachin merged

  10. mergennachin commented on Apr 9, 2024

    @mergennachin
    mergennachin
    on Apr 9, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Update documentation for Llama2

    @mergennachin merged

  11. mergennachin commented on Apr 9, 2024

    @mergennachin
    mergennachin
    on Apr 9, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Fix speed generation calculation for iLlama app

    @mergennachin merged

  12. cccclai commented on Apr 9, 2024

    @cccclai
    cccclai
    on Apr 9, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:
    Exclude mutable buffers in constant tagging

    @mergennachin merged

  13. GregoryComer commented on Apr 10, 2024

    @GregoryComer
    GregoryComer
    on Apr 10, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    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

  14. GregoryComer commented on Apr 10, 2024

    @GregoryComer
    GregoryComer
    on Apr 10, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    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

  15. Olivia-liu commented on Apr 10, 2024

    @Olivia-liu
    Olivia-liu
    on Apr 10, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Doc changes, refine The LLM Manual

    @guangy10 merged

  16. 69 remaining items

  17. mergennachin commented on Apr 25, 2024

    @mergennachin
    mergennachin
    on Apr 25, 2024
    Contributor

    Link to landed trunk PR:

    • N/A

    Link to release branch PR:

    Criteria category and reasons:

    • Update performance numbers

    @mergennachin merged

  18. guangy10 commented on Apr 25, 2024

    @guangy10
    guangy10
    on Apr 25, 2024
    ContributorAuthor

    No outstanding cherry-picks.
    Done creating the "v0.2.0-rc4" tag and kicked off prebuilt binaries from this tag.

  19. mergennachin commented on Apr 25, 2024

    @mergennachin
    mergennachin
    on Apr 25, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Disclaimer

    @mergennachin merged

  20. dbort commented on Apr 25, 2024

    @dbort
    dbort
    on Apr 25, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Fixes tag pattern matching to trigger docs build/push

    @dbort merged

  21. dbort commented on Apr 25, 2024

    @dbort
    dbort
    on Apr 25, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Fix flaky macos wheel builds

    @dbort merged

  22. svekars commented on Apr 25, 2024

    @svekars
    svekars
    on Apr 25, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Doc build fix

    @mergennachin merged

  23. dbort commented on Apr 25, 2024

    @dbort
    dbort
    on Apr 25, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Reword the "Preview only" message at the top of the ET website. Instead say that this is an alpha release and that the .pte format and APIs may change in a breaking way before Beta, later in 2024

    @dbort merged

  24. dbort commented on Apr 25, 2024

    @dbort
    dbort
    on Apr 25, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Fixes tag pattern matching to trigger docs build/push

    @dbort merged

  25. mergennachin commented on Apr 26, 2024

    @mergennachin
    mergennachin
    on Apr 26, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Arm documentation fixes

    @mergennachin merged

  26. mergennachin commented on Apr 26, 2024

    @mergennachin
    mergennachin
    on Apr 26, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • README documentation

    @mergennachin merged

  27. dbort commented on Apr 26, 2024

    @dbort
    dbort
    on Apr 26, 2024
    Contributor

    No more outstanding cherry-picks. I plan to create the v0.2.0-rc5 tag against 4f79832, the current release/0.2 HEAD

    Done: https://github.com/pytorch/executorch/releases/tag/v0.2.0-rc5

  28. svekars commented on Apr 27, 2024

    @svekars
    svekars
    on Apr 27, 2024
    Contributor

    Link to landed trunk PR:

    Link to release branch PR:

    Criteria category and reasons:

    • Doc build fix

    @dbort merged. Note that this doesn't need to be in the tagged RC/release to still be helpful.

  29. dbort commented on Apr 29, 2024

    @dbort
    dbort
    on Apr 29, 2024
    Contributor

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

  30. dbort
    closed this as completedon Apr 29, 2024
  31. dbort
    unpinned this issue on Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions