Taking over the Mercurial Migration
It seems that both Dirkjan and Brett are very caught up with real life for the coming months. So I suggest that some other committer who favors the Mercurial transition steps forward and takes over this project. If nobody volunteers, I propose that we release 3.2 from Subversion, and reconsider Mercurial migration next year. Regards, Martin
"Martin v. Löwis" writes:
It seems that both Dirkjan and Brett are very caught up with real life for the coming months. So I suggest that some other committer who favors the Mercurial transition steps forward and takes over this project.
I am not a committer, and am not intimately familiar with PEP 385, so not appropriate to become the proponent, I think. However, I am one of the PEP 374 co-authors, and have experience with previous transition to Mercurial of similar scale (XEmacs). I can promise to devote time to the transition in July and August, in support of whoever might step forward. I hope someone does.
If nobody volunteers, I propose that we release 3.2 from Subversion, and reconsider Mercurial migration next year.
In the absence of a volunteer, I think that's probably necessary.
Am 30.06.2010 07:37, schrieb "Martin v. Löwis":
It seems that both Dirkjan and Brett are very caught up with real life for the coming months. So I suggest that some other committer who favors the Mercurial transition steps forward and takes over this project.
If nobody volunteers, I propose that we release 3.2 from Subversion, and reconsider Mercurial migration next year.
IIUC, Dirkjan is only caught up for another month. I have no problems with releasing a first 3.2 alpha from SVN and then switching, so I propose that we target the migration for August -- I can help in the second half of August if needed. Georg
/me throws hat into ring. I'm in the middle of migrating fairly large chunks of an overgrown codebase from Subversion to Mercurial, so I might actually have worthwhile input :) -- ~Dan On Wed, Jun 30, 2010 at 10:41:51AM +0200, Georg Brandl wrote:
Am 30.06.2010 07:37, schrieb "Martin v. Löwis":
It seems that both Dirkjan and Brett are very caught up with real life for the coming months. So I suggest that some other committer who favors the Mercurial transition steps forward and takes over this project.
If nobody volunteers, I propose that we release 3.2 from Subversion, and reconsider Mercurial migration next year.
IIUC, Dirkjan is only caught up for another month. I have no problems with releasing a first 3.2 alpha from SVN and then switching, so I propose that we target the migration for August -- I can help in the second half of August if needed.
Georg
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/daniel.buch%40gmail.com
Am 01.07.2010 02:01, schrieb Dan Buch:
/me throws hat into ring. I'm in the middle of migrating fairly large chunks of an overgrown codebase from Subversion to Mercurial, so I might actually have worthwhile input :)
To all the volunteers: an issue that apparently requires immediate attention is that r21112 fails to convert. For details, see http://mail.python.org/pipermail/python-committers/2010-June/000977.html So somebody please reproduce the problem, propose a patch, and get in contact with Dirkjan to integrate it. Regards, Martin
On Thu, Jul 01, 2010 at 06:37:22AM +0200, "Martin v. Löwis" wrote:
Am 01.07.2010 02:01, schrieb Dan Buch:
/me throws hat into ring. I'm in the middle of migrating fairly large chunks of an overgrown codebase from Subversion to Mercurial, so I might actually have worthwhile input :)
To all the volunteers: an issue that apparently requires immediate attention is that r21112 fails to convert. For details, see
http://mail.python.org/pipermail/python-committers/2010-June/000977.html
So somebody please reproduce the problem, propose a patch, and get in contact with Dirkjan to integrate it.
Does anybody know if there's already an issue tracking the failure so that volunteers can better reproduce the issue? Is a full checkout of /projects/python via hgsubversion all that's required, perhaps? -- ~Dan
Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/daniel.buch%40gmail.com
On Thu, Jul 1, 2010 at 14:09, Dan Buch <daniel.buch@gmail.com> wrote:
Does anybody know if there's already an issue tracking the failure so that volunteers can better reproduce the issue? Is a full checkout of /projects/python via hgsubversion all that's required, perhaps?
I work from a full svnsync of the projects repo (including python). I can probably put up a tarball somewhere. Cheers, Dirkjan
Dirkjan, I assume having such a tarball available would be a good thing, but what do I know!? :) Are your steps for reproducing the referenced problem with cvs2svn-generated revs available on an issue, wiki page or PEP? -- ~Dan On Thu, Jul 01, 2010 at 02:19:06PM +0200, Dirkjan Ochtman wrote:
On Thu, Jul 1, 2010 at 14:09, Dan Buch <daniel.buch@gmail.com> wrote:
Does anybody know if there's already an issue tracking the failure so that volunteers can better reproduce the issue? Is a full checkout of /projects/python via hgsubversion all that's required, perhaps?
I work from a full svnsync of the projects repo (including python). I can probably put up a tarball somewhere.
Cheers,
Dirkjan _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/daniel.buch%40gmail.com
On Thu, Jul 1, 2010 at 15:23, Dan Buch <daniel.buch@gmail.com> wrote:
I assume having such a tarball available would be a good thing, but what do I know!? :)
I'm putting one up. I'll email you the address privately in order to preserve some bandwidth. Anyone else who wants a copy: just email me.
Are your steps for reproducing the referenced problem with cvs2svn-generated revs available on an issue, wiki page or PEP?
Install hgsubversion (tip) and get the pymigr repo, then just run this: $ hg clone -A pymigr/author-map --branchmap pymigr/branchmap file:///path/to/svn-repo/python Cheers, Dirkjan
Excellent! Much thanks, Dirkjan. -- ~Dan On Thu, Jul 01, 2010 at 04:14:16PM +0200, Dirkjan Ochtman wrote:
On Thu, Jul 1, 2010 at 15:23, Dan Buch <daniel.buch@gmail.com> wrote:
I assume having such a tarball available would be a good thing, but what do I know!? :)
I'm putting one up. I'll email you the address privately in order to preserve some bandwidth. Anyone else who wants a copy: just email me.
Are your steps for reproducing the referenced problem with cvs2svn-generated revs available on an issue, wiki page or PEP?
Install hgsubversion (tip) and get the pymigr repo, then just run this:
$ hg clone -A pymigr/author-map --branchmap pymigr/branchmap file:///path/to/svn-repo/python
Cheers,
Dirkjan
participants (5)
-
"Martin v. Löwis" -
Dan Buch -
Dirkjan Ochtman -
Georg Brandl -
Stephen J. Turnbull