Re: CVS Access Method

Anant Narayanan wrote:

I doubt that internals will have the necessary trust in a student to do this. More importantly I have personally argued about this with Rasmus, Ilia, Derick and several others. They simply do not see much of an advantage from switching to SVN. They only see a lot of "unnecessary" work and a huge risk (they keep pointing to the initial stability/reliability issues of SVN).

The student doesn't have to be someone from outside; there are plenty of students involved in PHP projects already. Yes, I am aware of the huge debate on "why switch". Essentially their argument seems to be: "if it ain't broke, why fix it?". Which is fair to some extent; but CVS does seem quite broken to me.

While I'm in great favour for SVN in many cases, I don't exactly know if SVN is the right thing for the PHP project, even less if it is for PEAR. In my eyes, CVS fits the needs we have for branching and tagging better than SVN does. Nevertheless, the advantages of SVN are clear (and that branch/tag issue is the only one I can think of, CVS has over SVN) and I'd love to see more secure transport channels, no matter wether it is CVS via SSH or SVN via SSH/HTTPS. - Sebastian