[issue14468] Update cloning guidelines in devguide

Ezio Melotti report at bugs.python.org
Sun Jan 13 10:11:14 CET 2013


Ezio Melotti added the comment:

I added more comments on bitbucket to indicate the new parts, the ones that have been moved, and the ones that have been removed.  That should make reviews easier.

I still haven't looked at the original FAQs (in faqs.rst), and still have to decide what should go where.  The general idea is that committers-specific FAQs should go in committing.rst, and the rest should go in faqs.rst.
Another option is to keep in committing.rst only the "4 fundamental FAQs" (i.e. "In what branches should I commit?", "In what order should I merge my commits?", "How do I merge between different branches (within the same major version)?", "How do I port a changeset between the two major Python versions (2.x and 3.x)?"), and move all the other stubs (including the one about null merges) on faqs.rst, possibly grouping them in two different sections: committers and contributors.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14468>
_______________________________________


More information about the Python-bugs-list mailing list