> -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 13, 2004 2:01 AM > To: [EMAIL PROTECTED] > Subject: VOTE; Installation of Subversion > > > I hereby propose that we request infrastructure to set up Subversion for > Avalon. I furthermore propose that we don't bother with migration of CVS, > and instead have SVN available for a few weeks, and then when we feel > comfortable, we move across the Merlin platform manually, after the next > set of releases.
If we can get a rather quick turnover for the CVS -> SVN import, could we do that and save the history? I'm not sure if we need to move everything over to SVN. For example, the avalon-excalibur module will hopefully go to the new Excalibur TLP. And avalon-phoenix could remain in CVS. That just leaves things like avalon, avalon-components, avalon-sandbox, and avalon-site. +1 to SVN, but let's see what infrastructure says about the CVS import. J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
