Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39290
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 208.113.200.5 as permitted sender)
Message-ID: <48892A10.9070905@php.net>
Date: Thu, 24 Jul 2008 20:19:12 -0500
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: PHP Developers Mailing List <internals@lists.php.net>
References: <488918E3.90705@lerdorf.com>
In-Reply-To: <488918E3.90705@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Volunteers for Subversion 1.5 conversion of cvs.php.net?
From: tswicegood@php.net (Travis Swicegood)

If it's not happening in the next month, I'd be happy to help.  I did 
the SimpleTest CVS to SVN conversion in about 5 minutes (including 
waiting on the history to be converted).  I've also worked with the hook 
scripts and such in SVN so I might be able to help out there if someone 
else doesn't already have it covered.

On a slightly related note, would anyone else be interested in seeing a 
Git repository along side Subversion?  Even if people can't commit to 
the Git repo, I'd be happy to help set it up with the ability for them 
to push changes back to the SVN repo once they've prepared their patches.

-T



Rasmus Lerdorf wrote:
> 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
>