Showing content from http://mail.python.org/pipermail/python-dev/attachments/20170214/c595f29a/attachment.html below:
<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, 13 Feb 2017 at 14:43 Victor Stinner <<a href="mailto:victor.stinner@gmail.com">victor.stinner@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">2017-02-13 21:08 GMT+01:00 Brett Cannon <<a href="mailto:brett@python.org" class="gmail_msg" target="_blank">brett@python.org</a>>:<br class="gmail_msg">
> We now have two sets of labels for representing cherry-picking statuses:<br class="gmail_msg">
> "backport to N.M" and "cherry-pick for N.M". The former are to help keep<br class="gmail_msg">
> track of what branches a PR should be cherry-picked to and can be removed<br class="gmail_msg">
> once the PR for a cherry-pick has been created (you can add a comment like<br class="gmail_msg">
> "cherry-picked from GH-NN" to make the link between the PRs).<br class="gmail_msg">
<br class="gmail_msg">
The first time I looked at the "backport to 3.6" flag, I understood<br class="gmail_msg">
that the change was written on the 3.6 branch and asked to rebase the<br class="gmail_msg">
change on 3.6. If I was confused, I'm sure that someone else will be<br class="gmail_msg">
confused as well :-)<br class="gmail_msg">
<br class="gmail_msg">
What do you think of renaming the label to "need 3.6 backport" (or<br class="gmail_msg">
"need backport to 3.6")?<br class="gmail_msg"></blockquote><div><br></div><div>That's fine by me. Anyone else have an opinion? </div></div></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4