RetroSearch Browse

Tue Feb 14 12:32:37 EST 2017 · https://mail.python.org/pipermail/python-dev/2017-February/147394.html

On Mon, 13 Feb 2017 at 14:43 Victor Stinner <victor.stinner at gmail.com>
wrote:

> 2017-02-13 21:08 GMT+01:00 Brett Cannon <brett at python.org>:
> > 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 first time I looked at the "backport to 3.6" flag, I understood
> that the change was written on the 3.6 branch and asked to rebase the
> change on 3.6. If I was confused, I'm sure that someone else will be
> confused as well :-)
>
> What do you think of renaming the label to "need 3.6 backport" (or
> "need backport to 3.6")?
>

That's fine by me. Anyone else have an opinion?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20170214/c595f29a/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2017-February/147394.html below:

[Python-Dev] Update on labels to be used on GitHub