[Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

[Steve Holden]

Georg Brandl wrote:
> Am 02.07.2010 16:17, schrieb anatoly techtonik:
>> On Fri, Jul 2, 2010 at 4:53 PM, Georg Brandl <g.brandl at gmx.net> wrote:
>>>> What is the problem with realtime synchronization and working with
>>>> already up to date Mercurial mirror of central SVN repository?
>>> The specifics of the conversion process are not nailed down yet.
>>> Therefore, the exact translation of SVN to Hg commits will change,
>>> and with it the Mercurial revision IDs, for example.
>> Does anybody here know how Mercurial calculates the IDs? From that I
>> remember it is author + message + diff content. What can change there?
> 
> The parents IDs also are part of that hash.  Apart from that, author and
> message can change as well, since SVN/CVS-style committer names will be
> mapped to Mercurial-style name + email, and the message can have
> "[rev ...]" appended or prepended or not.
> 
>>>>>> Development will continue in SVN
>>>>>> repository until everybody is ready for final migration in X weeks
>>>>>> later. Is that right?
>>>>> No; as soon as we switch, SVN will be read-only.
>>>> Why don't allow people who already know Mercurial use Mercurial and
>>>> those who prefer Subversion use that. If Mercurial allows to submit to
>>>> Subversion - why people can't use that while we writing tutorials and
>>>> answering question about workflow?
>>> I don't think that we have enough manpower to maintain such a bridge
>>> indefinitely.
>> It doesn't require manpower. It requires automation.
> 
> And who, do you think, is going to implement that automation?
> 
>> Considering that the biggest problem now is to get sane lossless
>> conversion, we should elaborate on getting this in place.
> 
> Ah, the mysterious "we".
> 
>> After that I would still follow
>> the path of setting realtime mirror for X weeks that could be
>> replicated by bitbucket, launchpad and other services to see how
>> people pickup the changes.
>>
>> As PEP 384 says - the transition is mostly to make lives of outside
>> contributors easier. Core developers can wait for a while.
> 
> Anatoly, I don't know what you are trying to achieve here.  The decision
> to switch to Mercurial as soon as possible given our manpower restriction
> has been made at PyCon 2009.  Since then, there has been progress, albeit
> slow, towards that switch, and now that has come into reach, you start
> questioning anything and everything.  This is neither productive, nor
> have you shown any willingness to actually *do* something to help.  You
> claim you do not have enough time for that; looking at the multitude of
> topics you're trying to force a discussion about, I wonder if you couldn't
> write one decent patch instead of ten complaining mails, and make both
> you and us happier in the process.
> 
+1

That's the spirit, Georg.

Anatoly, I had an email along these lines saved pending transmission,
but I have deleted it now. Let's make things better rather than dwell on
how rotten everything is and how it could be /so/ much better if "we"
would get off our butts and do {stuff}. ;-)

The more {stuff} done I can point to as PSF chairman the easier it will
be to justify raising funds to help make things better still. I'd rather
see devs developing than administering systems.

regards
 Steve
-- 
Steve Holden           +1 571 484 6266   +1 800 494 3119
DjangoCon US September 7-9, 2010    http://djangocon.us/
See Python Video!       http://python.mirocommunity.org/
Holden Web LLC                 http://www.holdenweb.com/