Transitioning to Subversion

[Robin Dunn]

Hi all,

Now that the test server has been available for a couple weeks, I'd like 
to begin to move forward on the subversion plan soon so I thought I 
would propose a few more details of the plan.

First of all, although nobody has really objected about it so far I 
thought I would still give one more chance.  Is there anybody who uses 
the current CVS server (either read-only or with commit access) who is 
strongly opposed to moving to subversion?  If so, why?

Secondly, does anyone have an objection to hosting the SVN server on the 
VPS where I have the wxPython sites and the current SVN test server 
located?  If so, why?  Where would you suggest to host it instead?  Once 
I get everything setup I'll be able to give admin logins to others who 
would like to help administrate this and any other wx sites/services we 
move to this box, so that should take care of the main concern I have 
with using a private server account instead of yet another big 
overloaded open source service provider like SourceForge for example.

Ok, on to the plan.  DotSrc has a cron job running that makes a tarball 
of the wx CVS repository once per week.  It runs Sunday mornings and 
appears to usually finish around 4am (UTC+1 I think).  So if we decide 
to move ahead with this and make the switch next weekend then that gives 
about a week to prepare.  My proposal is that I'll lock-down the CVS 
Saturday evening my time (UTC-8) wait for the regularly scheduled 
tarball to be made, and then use that to do the conversion, upload the 
results to the new server, set it up and then give the go ahead to start 
using it.  I expect that it shouldn't be any later than next Monday 
before it's ready to go.

Developers with commit permission should try to finish up what they are 
currently working on before Saturday night and to make whatever commits 
need to be done before making the transition to SVN.  For anything that 
isn't ready to check-in by Saturday you can just make a patch using cvs 
diff and then apply the patch in your new SVN workspace to pick up where 
you left off.

Next step: user names.  My first inclination is to keep the same names 
we have now, (RD, VZ, RR, JS, etc.) in order to keep continuity with the 
revision history.  However since they'll be based on real user names on 
this system I think it will just convert them to lower case.  So we can 
either have lower-case versions of the current user IDs, or we can 
switch to something like using everybody's SourceForge ID or something. 
What do you think?


-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!