Newsgroups: php.internals,svn.migration
Path: news.php.net
Xref: news.php.net php.internals:44411 svn.migration:354
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain darkrainfall.org from 208.97.132.145 cause and error)
Message-ID: <BA50C379-D922-4D92-9245-40FA531E8E16@darkrainfall.org>
To: svn-migration Migration <svn-migration@lists.php.net>,
	PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 22 Jun 2009 09:18:26 -0400
Subject: CVS to Subversion move progress
From: gwynne@darkrainfall.org (Gwynne Raskind)

In the last two days I've made some significant improvements to the  
migration process for CVS -> SVN. I know many have been proponents of  
Git, but SVN is closer to being viable at this point. Crossposting to  
internals@ so that more people have a chance to look into it, I'm  
calling for everyone to slam the hell out of the SVN repository  
(synchronized to CVS HEAD as of "2009-06-20 10:46:00 GMT", BUT NOT  
SYNCHRONIZED SINCE). To answer a FAQ, the SVN and CVS repositories  
will NOT be automatically synchronized, EVER. Throw everything you can  
at it. See if anything's wrong with it, see whether there are packages  
missing or mis-converted or needing adjusment or anything at all. If  
you have an issue, tell me and I'll do my best to deal with it. When I  
say torture it, I mean go freaking nuts. Commit to things you  
shouldn't have access to. Muck with the avail files. You get the idea.

A short quick&dirty guide to using PHP's SVN can be found at <http://darkrainfall.org/phpsvn-guide.html 
 >. It is STRONGLY recommended, even for those who've helped with  
testing SVN before. There are some new gotchas to be aware of.

This is a good time to start thinking about dealing with converting  
your scripts to SVN where they depend on CVS. This means cronjobs,  
revision number processors, changelogs, etc. The result of  
"intval(`svn cat http://svn.php.net/SVNROOT/trunk/svn-switch`)" can be  
used as a runtime switch to choose between CVS and SVN behavior; it  
will always be zero before the switch and one after it. (Keep in mind  
that this approach involves network I/O and the availability of the  
svn command on the server the script runs on.)

When the time for the move comes, here's what'll happen (rough  
outline, subject to change):

1) All CVS write access will be disabled. Read-only access will remain.
2) The SVN conversion script will be run (this takes roughly 18 hours).
3) Any scripts that need to be manually switched will be so switched.
4) The content of svn-switch will be changed to 1.
5) SVN write access will be enabled.
6) ???
7) Profit

P.S. If someone could crosspost this to pear-dev@, I'd be quite  
grateful; I can't seem to get subscribed to it.

-- Gwynne