[v0.15] Release Tracker

[NicolasHug]

We cut a release branch for the 0.15 release. (common commit with main is a192c95)

This issue is for tracking cherry-picks to the release branch.
The POC for the TorchVision team is @NicolasHug

Cherry-Pick Criteria

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

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)

Hud: https://hud2.pytorch.org/hud/pytorch/vision/release%2F0.15/0

[NicolasHug]

main: #7288
release branch: #7298

[NicolasHug]

#7334 cherry-picks all PRs made to main from #7295 to #7330 (included). They're all doc or tests / fix PRs.

[NicolasHug]

main: #7333
release branch: #7344

[NicolasHug]

main (actually fbcode): 2336aec
release branch: #7343

[NicolasHug]

main #7332
release branch: #7353

[NicolasHug]

#7352 cherry-picks various unit-test fixes #7347 #7351 #7350 #7348

[NicolasHug]

CI-fixies:

main: #7357
release-branc: #7358

[NicolasHug]

Fix flaky tests + smoke test
main: #7365 and #7362
release branch: #7367

EDIT: Actually, #7365 turned out to be failing on the release branch, so it's being reverted in #7368

[NicolasHug]

Follow-up from above:

#7365 should still be cherry-picked but we need to wait for the RC2 build to be available:

This is expected to work in PyTorch-2.0 branch, but only after RC2 build (that includes cherry-pick for kulinseth/pytorch@4886ab1 ) becomes available

#7365 (comment)

[NicolasHug]

Smoke test:

main: #7359
release-branch: TODO

[NicolasHug]

CI Fix
main: #7370
release branch: #7371

[NicolasHug]

Fix error message:

main: #7394
release branch: #7395

Not sure we'll trigger a new RC. I'm still including it in case we do because it's still nice to have.

[ddelange]

is torch>=2.0 support planned for torchvision 0.15.x?

torchaudio 2.0.1 already requires torch==2.0.0

[NicolasHug]

Hi @ddelange , yes pytorch 2.0 is supported by torchvision 0.15. Following our install instructions should get you those latest versions with either pip or conda: https://pytorch.org/get-started/locally/

[NicolasHug]

The release is done so this tracker is obsolete now - closing!