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
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.
See my Wiki on it at http://wiki.php.net/svnmigration, I'm planning
to get back to it this weekend.
-- Gwynne, Daughter of the Code
"This whole world is an asylum for the incurable."
Gwynne Raskind 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.See my Wiki on it at http://wiki.php.net/svnmigration, I'm planning to
get back to it this weekend.
Yes, I read that. But the conversion of the repository itself is only
half the battle. There are a bunch of scripts in CVSROOT that need to
be ported over to SVN somehow.
-Rasmus
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.
See my Wiki on it at http://wiki.php.net/svnmigration, I'm
planning to
get back to it this weekend.
Yes, I read that. But the conversion of the repository itself is
only half the battle. There are a bunch of scripts in CVSROOT that
need to be ported over to SVN somehow.
My plan was to work on those next.
-- Gwynne, Daughter of the Code
"This whole world is an asylum for the incurable."
Yes, I read that. But the conversion of the repository itself is
only half the battle. There are a bunch of scripts in CVSROOT that
need to be ported over to SVN somehow.My plan was to work on those next.
not only CVSROOT, there are also some vcs-specific script in php-src
(like cvsclean or scripts for snaps building), scripts on the snaps box
to build snaps, on master to generate docs and websites, .... which all
have to found, analyzed, rewritten.
So a rather long running project where he repository conversion is one
of the smallest problem (enough big projects did that so if there are
problems there are many places to ask, whereas the whole infrastructure
around has to be analyzed...) :-)
johannes
Do we have a preference of Apache's SVN or svnserve?
The former requires Apache 2+, AFAIK.
S
Do we have a preference of Apache's SVN or svnserve?
The former requires Apache 2+, AFAIK.
I'd like to kick this discussion over to the svn-migration@ list;
there are a lot of points to consider in this question and internals@
has enough threads as it is.
-- Gwynne, Daughter of the Code
"This whole world is an asylum for the incurable."
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?
You can count me in. I converted all of my websites and inside
projects from CVS to SVN earlier this year. It seemed a daunting
task, but it was trivial at best. I didn't use any of the automated
tools, though, I did it all manually.
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.
Not to mention the community of developers for SVN, add-ons, et
cetera, and the ease of use via Apache.
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.
I'd agree. It may not hurt to write a quick script to do
real-life commits to both services from the command line, as well, in
the beginning.
--
</Daniel P. Brown>
Better prices on dedicated servers:
Intel 2.4GHz/60GB/512MB/2TB $49.99/mo.
Intel 3.06GHz/80GB/1GB/2TB $59.99/mo.
Dedicated servers, VPS, and hosting from $2.50/mo.
I spoke to helly about this just there. I'm more than willing to help.
We converted a test repository while developing the re2c stuff.
Scott
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
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:rasmus@lerdorf.com]
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
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"...
Is this something with which we'd want only folks with existing
CVS accounts to help? If we were to open up the initial SVN to people
not (or not yet) affiliated with the group, we may be able to garner
some responses from well-versed SVN folks (specifically CVS-to-SVN)
who may just not have time to dedicated to the advancement of PHP as a
whole.
--
</Daniel P. Brown>
Better prices on dedicated servers:
Intel 2.4GHz/60GB/512MB/2TB $49.99/mo.
Intel 3.06GHz/80GB/1GB/2TB $59.99/mo.
Dedicated servers, VPS, and hosting from $2.50/mo.
I've done a bunch of stuff with svn commit hooks and am willing to
lend a hand.
-lucas (mobile)
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
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
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.
Yes, I'm interested, as we acutally provide a GIT tree for the current
5.3 CVS and therefore I like to see it the SVN as a GIT tree, too. As
Lukas already mentioned, it would be great to support a official dvcs
infrastructure on php.net for experimental branches.
Travis Swicegood wrote:
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.
That would certainly be nice! I would normally advocate a full switch
from CVS to Git, but since it seems the general consensus is to SVN, a
parallel Git repository would greatly aid those of us stuck on Windows
with bjorked git-svn installs.
--
Edward Z. Yang GnuPG: 0x869C48DA
HTML Purifier http://htmlpurifier.org Anti-XSS Filter
[[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]]
Hello Edward,
to be honest, what is wrong with svn for you? Do you branch off your own
PHP? No, so what's wrong? To easy to use for 99.99% of people using PHP
repository? But please (everyone) just think of it and don't comment
anymore.
The decision has been made we are going for SVN and nothing else at this
point. And yes. Once that is done and works for everyone we might look into
more complex solutions. Just to make the about 10 developers like myself
who really need their own branching support happy. ... dreams can get true
:-)
marcus
Tuesday, July 29, 2008, 5:46:51 AM, you wrote:
Travis Swicegood wrote:
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.
That would certainly be nice! I would normally advocate a full switch
from CVS to Git, but since it seems the general consensus is to SVN, a
parallel Git repository would greatly aid those of us stuck on Windows
with bjorked git-svn installs.
--
Edward Z. Yang GnuPG: 0x869C48DA
HTML Purifier http://htmlpurifier.org Anti-XSS Filter
[[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]]
Best regards,
Marcus
Marcus Boerger wrote:
to be honest, what is wrong with svn for you? Do you branch off your own
PHP? No, so what's wrong? To easy to use for 99.99% of people using PHP
repository? But please (everyone) just think of it and don't comment
anymore.
As I said previously, my personal opinion has no matter in it. I'm just
saying that Travis's proposal is a good one and retains many of the
benefits of Git (esp. in patch preparation) especially if it's
officially blessed.
Cheers,
Edward
--
Edward Z. Yang GnuPG: 0x869C48DA
HTML Purifier http://htmlpurifier.org Anti-XSS Filter
[[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]]