[core-workflow] "backport needed" status

[Brett Cannon]

On Tue, 28 Mar 2017 at 07:39 R. David Murray <rdmurray at bitdance.com> wrote:

> If there is objection I will happily revert it, but I needed to mark an
> issue on bugs.python.org as still needing backport, since I'd merged
> the fix and the PR is now closed but I have no time currently to learn
> about how to do backports(*).  So I added a 'backport needed' status
> to the tracker.
>
> I there is agreement that this is a good idea and should remain, we can
> maybe get rid of it later after backports are automated.  But I
> have a feeling we'll want it long term, given the new workflow
> and the fact that not all backports can be done automatically.
>

I'm fine with it personally. I have had a couple of instances where I
wanted to merge something but I didn't want to lose track of the fact that
I had some cherry-picking to do, so I waited until I got home. WIth this
flag I can just assign the issue to myself as a reminder and then do the
merge immediately while still doing the cherry-picking when I get home.


>
> --David
>
> (*) Or, to be more accurate, I'm waiting until you all figure out how
> to automate it.
>

:) https://github.com/python/core-workflow/tree/master/cherry_picker actually
automates a lot of it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20170328/5afff214/attachment.html>