[Python-Dev] Update on labels to be used on GitHub
Brett Cannon
brett at python.org
Mon Feb 13 15:08:55 EST 2017
More information about the Python-Dev mailing list
Mon Feb 13 15:08:55 EST 2017
- Previous message (by thread): [Python-Dev] Heads-up, I've rejoined
- Next message (by thread): [Python-Dev] Update on labels to be used on GitHub
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
We now have two sets of labels for representing cherry-picking statuses: "backport to N.M" and "cherry-pick for N.M". The former are to help keep track of what branches a PR should be cherry-picked *to* and can be removed once the PR for a cherry-pick has been created (you can add a comment like "cherry-picked from GH-NN" to make the link between the PRs)*.* The latter labels are to signify that the PR is a cherry-pick *itself*. As with all aspects of the new GitHub workflow, we will give this a solid try for about a month and then we can re-evaluate whether we like this approach or want a more traditional prefix format in the title to represent the same thing. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170213/225558f5/attachment.html>
- Previous message (by thread): [Python-Dev] Heads-up, I've rejoined
- Next message (by thread): [Python-Dev] Update on labels to be used on GitHub
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list