Home Original page

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

Brett Cannon brett at python.org
Fri Mar 17 13:37:14 EDT 2017 
https://github.com/python/core-workflow/issues/13 already exists to track
this idea, so it can be discussed more over there.

On Thu, 16 Mar 2017 at 10:26 Barry Warsaw <barry at python.org> wrote:

> On Mar 16, 2017, at 04:14 PM, Brett Cannon wrote:
>
> >Ah, you didn't say you wanted this to be a status check. :) Do we want to
> >go so far as that rather than a comment or PR template?
>
> I like it for that on my other projects, so I'm pretty sure I'd like that
> for
> CPython.  I'm a big fan of more automated checks -when they are stable and
> robust- for doing the fiddly little checks that are a pain to do
> manually.  I
> like requiring bug reports for most things, plus style checks, etc.  It
> makes
> it so much easier for a submitter to conform because they get immediate
> feedback if they break some policy.  There's usually a strong drive to get
> all
> the lights green.
>
> Cheers,
> -Barry
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20170317/3eab827a/attachment.html>
More information about the python-committers mailing list