[python-committers] PEP 462: Workflow automation for CPython

[Eli Bendersky]

Interesting. Chromium has something kind-of similar, named "commit queue",
for developers without actual commit access. Once they get an LGTM, the
thing rolls automatically. In fact, core developers often find it useful
too because the Chromium tree is sometimes closed ("red"). We don't really
do the latter in Python, which carries a problem we'll probably need to
resolve first - how to know that the bots are green enough. That really
needs human attention.

Eli


On Fri, Jan 24, 2014 at 9:51 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:

> Hey all,
>
> Rather than leaving my ideas undocumented until the language summit in
> April, I wrote up what I see as the critical issues in our current
> workflow and how I believe Zuul could help us resolve them as a PEP:
> http://www.python.org/dev/peps/pep-0462/
>
> I don't think we should *do* anything about this until after PyCon US,
> but wanted to publish something that clearly explained my thinking
> rather than surprising people with it at the summit.
>
> Cheers,
> Nick.
>
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20140125/d83d1582/attachment-0001.html>