[Python-Dev] Mercurial Schedule (original) (raw)

Brett Cannon brett at python.org
Fri Nov 19 19:52:03 CET 2010

On Fri, Nov 19, 2010 at 05:50, Nick Coghlan <ncoghlan at gmail.com> wrote:

On Fri, Nov 19, 2010 at 5:43 PM, Georg Brandl <g.brandl at gmx.net> wrote:

Am 19.11.2010 03:23, schrieb Benjamin Peterson:

2010/11/18 Jesus Cea <jcea at jcea.es>:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 18/11/10 18:32, "Martin v. Löwis" wrote: In general, I'm also concerned about the lack of volunteers that are interested in working on the infrastructure. I wish some of the people who stated that they can't wait for the migration to happen would work on solving some of the remaining problems. Do we have a exhaustive list of mercurial "to do" things?. http://hg.python.org/pymigr/file/1576eb34ec9f/tasks.txt Uh, that's the list of things to do at the migration.  The todo list is http://hg.python.org/pymigr/file/1576eb34ec9f/todo.txt That kind of link is the sort of thing that should really be in the PEP... (along with the info about where to find the hooks repository, specific URLs for at least 3.x, 3.1 and 2.7, pointers to a draft FAQ to replace the current SVN focused FAQ, etc)

I am spending my PSF grant time in January rewriting python.org/dev practically from scratch. Any needed updates to take Mercurial in account will happen no later than then.

-Brett

Target dates for the following specific activities would also be useful: - date a "final draft" of converted repository will be made available to Martin and Ronald to dry run creation of Windows and Mac OS X installers - date SVN will go read only - date Hg will be available for write access (it should be frozen for a while, to give the folks doing the conversion a chance to make sure buildbot is back up and run, commit emails are working properly, etc) So as long as we acknowledge that any migration problems may mean additional beta releases of 3.2 to iron things out, I don't see a problem with releasing beta 1 as planned to close the door on any other new features, and giving the Hg migration a clear run at the source repository before we start working seriously on dealing with bug reports (either existing ones, or those from the first beta). Cheers, Nick. -- Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org

More information about the Python-Dev mailing list