Em Tuesday 02 September 2008 10:33:13 Florent Aide escreveu: > On 9/2/08, Alberto Valverde <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Sorry for being late to the party, I was on vacations. > > > > I'd also like seeing TG2 switching to mercurial. Most of the pro > > arguments have been already mentioned in this thread but I'll briefly > > repeat those that I find most valuable: > > I'm also in favor of a change to HG in regards of all the goodies that > it may give. _But_ I would like this migration to happen after the > official 2.0 release and 1.1 release. So that we don't provoke too > much turmoil in the dev tools right now.
Does anyone have a migration plan? I mean, a series of commands and configurations that would be run to migrate our repository? I did the change on one project here, but I had to use hgimportsvn to be able to get everything and the initial process seemed to be really slow (this project only had 2700 revisions). Also, for how long will we keep a read-only SVN repository (hgpullsvn can help keeping it up to date)? Because if we have branches and work being done on SVN (and don't have the same "plan" that TG followed on the main repository) we don't necessarily need / can / want to commit before the move. Having the read-only repository would help creating patches to apply over a new checkout using mercurial, when the "time constraint" allows the developer / company / team / whatever to do that (i.e., if I am in the middle of a certification / validation process I can't change the repository immediately). I know all this sounds too corporate, but that's the kind of planning I do everyday for a bank and for companies in the human health market... > I've got my toolchain working on windows, macos & linux with direct > access to the net and SSH tunneled only and I'd like to have time to > ponder the options for this migration. Can we get the migration done using a batch? I mean, one big script that woul dbe run to migrate our official repository, including users and etc.? If it is too hard, maybe part automated and part explaining how to change commands to accomplish the whole change. This would allow the change for personal repositories to follow the same process in the future... (Also extremely useful to document things and for widget authors that will want to migrate.) -- Jorge Godoy <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part.
