[python-committers] 4 weeks with the new workflow: what needs changing?
Barry Warsaw
barry at python.org
Thu Mar 16 13:25:46 EDT 2017
More information about the python-committers mailing list
Thu Mar 16 13:25:46 EDT 2017
- Previous message (by thread): [python-committers] 4 weeks with the new workflow: what needs changing?
- Next message (by thread): [python-committers] 4 weeks with the new workflow: what needs changing?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: <http://mail.python.org/pipermail/python-committers/attachments/20170316/e66ecb8e/attachment.sig>
- Previous message (by thread): [python-committers] 4 weeks with the new workflow: what needs changing?
- Next message (by thread): [python-committers] 4 weeks with the new workflow: what needs changing?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list