question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[v0.12] Release Tracker

See original GitHub issue

We cut a release branch for the 0.12 release.

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

Cherry-Pick Criteria

Phase 1 (until 02/17/22):

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

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

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
jdsgomescommented, Feb 24, 2022

Link to landed main PR: https://github.com/pytorch/vision/pull/5472 Link to release branch PR: https://github.com/pytorch/vision/pull/5474

Criteria Category: 2 Critical fix (class should not be exposed at package level)

1reaction
jdsgomescommented, Feb 16, 2022

New cherrypick

Link to landed master PR: https://github.com/pytorch/vision/pull/5427 Link to release branch PR: https://github.com/pytorch/vision/pull/5434

Criteria Category: 4 fix for tests

Read more comments on GitHub >

github_iconTop Results From Across the Web

Python Tracker 0.12.0 Released - Discourse – Snowplow
We are pleased to announce the release of the Snowplow Python Tracker v0.12.0. This release contains breaking changes with updates to the ...
Read more >
OppiaMobile Server Change Log for v0.12.x
In this release, a field was added to record the course_version of the course in each tracker, see the upgrading notes to populate...
Read more >
v0.12.1 release notes — Wagtail CRX documentation
Search results when using the database search backend without specifying specific search models (default behavior) are now returned based on date last published ......
Read more >
Release v0.12 (#2328) · Issues · Xiph.Org / Opusfile · GitLab
Tracking issue for the 0.12 release. ... Release v0.12. Tracking issue for the 0.12 release. ... Changes since the v0.11 release.
Read more >
Upgrade Terraform v0.12 to v0.13 (#13338) · Issues - GitLab
Since Terraform supports upgrading from one major release at a time, all terraform modules should be updated from v0.12.X to v0.13.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found