[v0.13] Release Tracker

We cut a release branch for the 0.13 release. (common commit with main is 69ce452)

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

Cherry-Pick Criteria

Phase 1 (until 06/06/22):

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

1. Fixes to regressions against the most recent minor release (e.g. 0.12 for 0.13 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.12 for 0.13 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 06/06/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.13
   git checkout release/0.13
   git cherry-pick abcdef12345
   
   # Submit a PR based against 'release/0.13' either:
   # via the GitHub UI
   git push my-fork
   
   # via the GitHub CLI
   gh pr create --base release/0.13
   

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

[YosuaMichael]

Refactor swin_transformer so it can be compatible with the 3d version (hence we dont introduce BC changes in the future release)

PR for main: https://github.com/pytorch/vision/pull/6088 PR for release/0.13: https://github.com/pytorch/vision/pull/6100 (MERGED) category: backward compatibility

[YosuaMichael]

Handling edge cases on test_backbone_utils when the tracer sample nodes that is buffer with integer dtype, in this case the function Tensor.mean() will raise error since it does not accept integer. We add .float() before .mean() with this PR.

PR for main: https://github.com/pytorch/vision/pull/6090 PR for release/0.13: https://github.com/pytorch/vision/pull/6091 (MERGED) category: bugfix