[Python-Dev] My thinking about the development process (original) (raw)

Brett Cannon brett at python.org
Sat Dec 6 15:13:47 CET 2014

On Sat Dec 06 2014 at 2:53:43 AM Terry Reedy <tjreedy at udel.edu> wrote:

On 12/5/2014 3:04 PM, Brett Cannon wrote:

> 1. Contributor clones a repository from hg.python.org <_ _http://hg.python.org> > 2. Contributor makes desired changes > 3. Contributor generates a patch > 4. Contributor creates account on bugs.python.org > <http://bugs.python.org> and signs the > contributor_ _> agreement I would like to have the process of requesting and enforcing the signing of CAs automated.

So would I.

> 4. Contributor creates an issue on bugs.python.org > <http://bugs.python.org> (if one does not already exist) and uploads a patch I would like to have patches rejected, or at least held up, until a CA is registered. For this to work, a signed CA should be immediately registered on the tracker, at least as 'pending'. It now can take a week or more to go through human processing.

This is one of the reasons I didn't want to create an issue magically from PRs initially. I think it's totally doable with some coding.

-Brett

> 5. Core developer evaluates patch, possibly leaving comments through our > custom version of Rietveld > 6. Contributor revises patch based on feedback and uploads new patch > 7. Core developer downloads patch and applies it to a clean clone > 8. Core developer runs the tests > 9. Core developer does one last hg pull -u and then commits the > changes to various branches -- Terry Jan Reedy

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ brett%40python.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20141206/c1309385/attachment.html>

More information about the Python-Dev mailing list