I'd love to see this conversion. Let's make sure we get enough folks to volunteer to check the history of our source trees although we should in any case keep the CVS one around for browsing "just in case"...
Andi > -----Original Message----- > From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 24, 2008 5:06 PM > To: PHP Developers Mailing List > Subject: [PHP-DEV] Volunteers for Subversion 1.5 conversion of cvs.php.net? > > Now that Subversion 1.5 has been out for a little while and it is at the > point where it might actually have some benefit to us, do we have some > volunteers who have some time to try converting over the repository and > all the post-commit and ACL rules from CVSROOT? > > Talking to people here at OSCON, the consensus seems to be that moving > to Subversion at this point would worthwhile. The Git/Bzr/Merc folks > have better tools to deal with a central svn repository than cvs at this > point, and the svn workflow and Windows tools won't leave all our less > technical committers floundering. > > I think the most convenient approach would be to do the conversion > directly on the cvs.php.net machine and run the two side-by-side with > periodic imports to svn while we test things and then a freeze and a > switchover at some point. > > -Rasmus > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
