<br><br><div class="gmail_quote">On Mon, Jul 6, 2009 at 07:51, M.-A. Lemburg <span dir="ltr"><<a href="mailto:mal@egenix.com">mal@egenix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Dirkjan Ochtman wrote:<br>
> In response to some rumblings on python-committers and just to request<br>
> more feedback, a progress report. I know it's long, I've tried to put<br>
> to keep it concise and chunked, though.<br>
<br>
</div>Two things:<br>
<br>
* We need some form of documentation of how committers are expected<br>
to work with the hg repo. (This is also missing for the Subversion<br>
repo, which due to the 3.x branch has gotten somewhat unclear - at<br>
least for me)<br>
</blockquote><div><br></div><div>I am planning to get a version of the dev FAQ written up that covers most of what it already does now for svn.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
It is currently not clear where to check in patches, whether and<br>
where to backport or forward-patch, which branches to consider<br>
closed, etc.<br>
<br>
E.g. if I check in something in trunk/ (Python 2.7), do I have to<br>
forward patch this change to the 3.0 branch (guess not), the py3k/<br>
branch (Python 3.1), or will someone else take care of this, so that<br>
it's better not to interfere by doing it myself ?<br>
</blockquote><div><br></div><div>This question is partially answered by <a href="http://www.python.org/dev/faq/#how-do-i-merge-between-branches">http://www.python.org/dev/faq/#how-do-i-merge-between-branches</a>, but I agree that we should have either this spelled out in the FAQ or a committer-specific doc at <a href="http://www.python.org/dev/">www.python.org/dev/</a> that makes this all very obvious.</div>
<div><br></div><div>-Brett</div></div>