Subversion: The new-generation CVS (DevChannel)
Posted May 31, 2004 1:23 UTC (Mon) by
gdt (subscriber, #6284)
In reply to:
Subversion: The new-generation CVS (DevChannel) by riel
Parent article:
Subversion: The new-generation CVS (DevChannel)
Subversion never claimed to be more than a better CVS. That was the project goal. They've succeeded in meeting that, although taking much longer than anyone expected. I've attempted to configure a secure CVS server for updates with anonymous access for reads and been stunned that CVS can't do this without a huge amount of effort (or simply giving up and having two rsynced repositories). So I'm glad to see an alternative to CVS.
You also write of open source development as if it were a monolithic design methodology. This is hardly so; projects vary widely in their methodologies. For example, Samba's "core team" approach might well only see the costs of distributed version control without seeing the benefits.
I've tried arch. A nice idea, but too many limitations for deployment at this time.
I do get frustrated with the "editor wars" aspects of configuration control. Especially since the most useful parts of configuration control are the analysis add-ins, something no open source system seems to have much of. To pick a simple task, rebuild the project each night, e-mailing owners and those that modified failing code with compile and regression test errors. Or, tell me which modules don't have a regression test. Or, who checks in the greatest proportion of failing code. Or, which module has had the most field issues raised against it.
(
Log in to post comments)