Repository navigation
Document backport and cherry-pick labels #126
Description
There should be a documentation explaining what to do with the labels needs backport to X.Y and cherry-pick for X.Y. Perhaps as a new section in committing.rst?
I think this is the current workflow: (as discussed in python/core-workflow#23)
- Apply
needs backport to X.Ylabel to the PR againstmaster. - Once
masterPR is approved and merged, create the cherry-pick PR. - Remove
needs backport to X.Ylabel frommasterPR - Apply the
cherry-pick for X.Yto the cherry-pick PR. - Prefix the cherry-pick pr description with
[X.Y] - Issue can be closed once all cherry-pick PRs have been merged.
Where X.Y is one of the maintenance branches, e.g. 2.7, 3.5, 3.6
Related question: Can I assume that the core developer who merged the master PR will do the backport?
Thanks :)
Activity
berkerpeksag commentedon Feb 21, 2017
+1 from me. We probably need to wait for a bit to settle on the exact workflow before starting to document it.
We could probably cover the GitHub part in http://cpython-devguide.readthedocs.io/committing.html#backporting-changes-to-python-3-6-or-older-version (or split it to two separate subsections?)
+1. This is also my assumption.
Improvements to Committing.rst
Improvements to Committing.rst (#149)
Improvements to Committing.rst (python#149)
Improvements to Committing.rst (#149)