[v0.14] Release Tracker

[YosuaMichael]

We cut a release branch for the 0.14 release. (common commit with main is 07ae61b)

This issue is for tracking cherry-picks to the release branch.
The POCs for the TorchVision team are @YosuaMichael and @datumbox

Cherry-Pick Criteria

Phase 1 (until 10/10/22):

Only low-risk changes may be cherry-picked from master:

1. Fixes to regressions against the most recent minor release (e.g. 0.13 for 0.14 release);
2. Critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
3. Fixes to new features introduced in the most recent minor release (e.g. 0.13 for 0.14 release)
4. Test/CI fixes
5. Documentation improvements
6. Compilation fixes or ifdefs required for different versions of the compilers or third-party libraries
7. Release branch specific changes (e.g. change version identifiers)

Phase 2 (after 10/10/22):

Note that changes here require us to rebuild a Release Candidate and restart extended testing (likely delaying the release). Therefore, the only accepted changes are Release-blocking critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks

Changes will likely require a discussion with the larger release team over VC or Slack.

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 a PR against the release branch.

   # Find the hash of the commit you want to cherry pick
   # (for example, abcdef12345)
   git log
   
   git fetch origin release/0.14
   git checkout release/0.14
   git cherry-pick abcdef12345
   
   # Submit a PR based against 'release/0.14' either:
   # via the GitHub UI
   git push my-fork
   
   # via the GitHub CLI
   gh pr create --base release/0.14

3. Make a request below with the following format:

Link to landed master PR (if applicable):
* 

Link to release branch PR:
* 

Criteria Category:
* 

1. the POC will reply with approved / denied or ask for more information.
2. If approved, the PR can be merged once the tests pass.

NOTE: Our normal tools (ghstack / ghimport, etc.) do not work on the release branch.

Please note HUD Link with branch CI status and link to the HUD to be provided here.
HUD

Versions

0.14

[pmeier]

Link to landed master PR (if applicable): #6694 - MERGED

Link to release branch PR: #6701 - MERGED

Criteria Category: Documentation improvements

[jdsgomes]

Link to landed master PR: #6672 - MERGED

Link to release branch PR: #6703 - MERGED

Criteria Category: Bugfix

[YosuaMichael]

Link to landed master PR: #6700 - MERGED

Link to release branch PR: #6706 - MERGED

Criteria Category: Bugfix

[atalman]

Link to landed master PR (if applicable):

• Fix windows python 3.8 required dlls not found #6715

Link to release branch PR:

• Fix windows python 3.8 required dlls not found (#6715) #6716

Criteria Category:

• CI fix

---

@atalman merged

[atalman]

Link to landed master PR (if applicable):

• Fix for windows and python 3.8 call to add_dll_directory #6742

Link to release branch PR:

• Fix for windows and python 3.8 call to add_dll_directory (#6742) #6743

Criteria Category:

• Critical CI fix

---

@atalman merged

[YosuaMichael]

Link to landed master PR: #6789 (MERGED)

Link to release branch PR: #6849 (CLOSED)

Criteria: Test/CI Fixes

We cancel cherry-pick this one because it is not critical (dont affect the binary build)