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

[Antoine Pitrou]

Le 10/03/2017 à 23:13, Brett Cannon a écrit :
> I can't believe it's been 4 weeks. It feels like it was ages/yesterday
> when we moved. :)
> 
> First, I hope people are not regretting letting/having me make this
> migration. I know there have been some things to work through (and
> others still to come), but I hope this is all a net positive (either now
> or in the near future).
> 
> Second, I wanted to get initial feedback on things we can easily tweak:
> 
>   * Requiring Travis to pass (I *really* don't want to turn this off as
>     we already had a broken build when I temporarily turned it off at
>     someone's request when Travis was backed up from the AWS S3 outage;
>     I also don't plan to make AppVeyor required unless there's a way to
>     make it be skipped for doc-only changes)
>   * Cherry-picking working out? (We can go back to forward merging if
>     people really want to, but I think long-term cherry-picking will
>     allow for more automation)

Right now, the way cherry-picking works (or doesn't really work, rather)
makes me likely to do "blind cherry-picks", that is try to fix conflicts
and trust the script's output without really bothering to inspect the
code locally, instead relying on Travis and AppVeyor.
I don't know if that's good for long-term quality.

I am more or less used to git, but it's the first time I have a
cherry-picking workflow (the other projects I work on don't really have
a notion of bugfix branch, or only an ephemeral one).  git seems to make
that extremely painful.

Really

Antoine.