[python-committers] 4 weeks with the new workflow: what needs changing?

[Brett Cannon]

On Mon, 13 Mar 2017 at 12:36 R. David Murray <rdmurray at bitdance.com> wrote:

> On Mon, 13 Mar 2017 12:48:30 -0400, Yury Selivanov <
> yselivanov.ml at gmail.com> wrote:
> > Yesterday I was working on a few asyncio PRs and a bug in async/await.
> > All PRs required cherry-picking.  Again, I was spending significant
> > amount of time just creating branches/PRs for cherry-picking.  Again
> > waiting for CI checks (even thougn I always run the test suite before I
> > push).  In the end of the day, I was so frustrated and discouraged that
> > I just stopped working on CPython.
>
> Branch management was always the most time consuming part of committing,
> even under HG.  But github has clearly made it worse.  Personally I doubt
> I'm going to do any backports if I'm required to go visit some web pages
> to do it.  That doesn't matter much, since I don't have much time for
> contribution and have done very few checkins in a good while (even before
> the switch).  But Brett was hoping that github would make it *easier* to
> get stuff merged, and from my perspective that is only true for doc fixes
> (which, granted, is a help :), while making it harder for code fixes.
>
> So, I think the backport-bot should probably be the top priority of
> whoever has time to work on this (which, unfortunately, is not me :(
>

It's #2 after the Misc/NEWS solution.

-Brett


>
> Being able to backport without going through the PR process would also
> make sense to me (and I thought we were going to be able to do that),
> but I'm not involved enough in the conversations to know the downsides
> of that.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20170314/5b264e38/attachment.html>