[0.6 Release] Quality testing

[metascroy]

We plan to release ExecuTorch 0.6 on 4/24/24, and we need everything finalized by 4/17/25 (this includes cherry picks for the release branch, as well as documentation and tutorial changes).

We have cut the 0.6 branch, and now we need your help testing it!

If you're interested, go to the Google sheet we're using to track documentation and QA for the 0.6 release and request access. Then do the following:

1. Find a documentation or readme section that is up-for-grabs, put your name down in the "QA tester" column, and change the "QA status" column to "testing".

2. Read through the documentation / tutorial, and test out the code examples in it against the release/0.6 branch of ExecuTorch. Optionally leave any comments in the "QA comments" column.

3. If things look good, change the "QA status" column to "Looks good". If you find an issue, change the status to "Found issues", create a GH issue on the ExecuTorch v0.6 release blocker with more detail, and link to this issue in the the "QA comment" section. Someone from the ExecuTorch team will review.

[mergennachin]

For AOT flow, try this first instead of building from source (e.g., ./install_executorch)

pip install --extra-index-url https://download.pytorch.org/whl/test/cpu executorch==0.6.0 torch==2.7.0 torchaudio==2.7.0 torchvision==0.22.0

[zhenyan-zhang-meta]

We could probably mention that, for any questions please discuss in the discord channel #releases.

[metascroy]

Closing issue. Release 0.6 is code-finalized.