[python-committers] Create a Mercurial repository with a branch per issue

[Nick Coghlan]

On Fri, Feb 4, 2011 at 11:57 PM, Tarek Ziadé <ziade.tarek at gmail.com> wrote:
> I'd rather have a best practice guide *now* and refine it later. e.g.
> "how to contribute to python via mercurial."
>
> I think we have people here with a decent expertise of Mercurial that
> can come up w/ this, even if it's changed after.

Yes, please. Having a best practices document *in advance* will help
keep things productive, especially with the Pycon sprints coming up
shortly after the anticipated switchover.

Aside from the basics (how to checkout, how to generate a patch file),
things I'd personally like advice on:
- how best to work with multiple branches to support the forward
porting model for bug fixing
- how to clean a history ready for commit
- how to set up a feature branch for collaborative development

Policy decisions on release management can be deferred for now, since
they will be largely in the hands of the Python 3.3 Release Manager.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia