We agreed on this already, so don't worry.
But can we also please use the procedure I proposed:
"""
After the release of 2.0.0 a sunrise period for SVN is announced well in advance
for migration to SVN. This period is started off with a fresh migration of the
dbmail CVS repository into SVN, and a full notification to all developers with
write access which includes their logins. During the sunrise period we have
write access to both CVS and SVN and developers are responsible for making sure
SVN is up-to-date.
After the sunrise period, we enter a sunset period for CVS. During this period,
again announced well in advance, CVS is closed for write access. This is the
last chance to move code changes from CVS to SVN.
Finally, CVS is closed all together and we're all happy in a brave new
SVN world.
"""
Ilja Booij wrote:
Hi all,
I know I'm not making myself really popular by mentioning this..
We would really like to make the move from CVS to Subversion. Since
the last time that we (IC&S) mentioned this, all our other projects
have been moved to Subversion. We'd like to move DBMail to Subversion
as soon as possible.
Personally, I don't see any problems in migrating, as Subversion works
quite similar from the client's point of view.
I'll put on my armor now.. ;)
Ilja
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
________________________________________________________________
Paul Stevens [EMAIL PROTECTED]
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands_______________________________________www.nfg.nl
