jalopeura at hotmail.com
Sat Nov 29 00:07:15 MST 2008
Tonny Kohar wrote:
> If by any chance that the project is moving to use some kind of
> revision control system eg: as suggested SVN. I think it might be
> better to use the third generation of revision control aka
> distribution revision control eg: Mercurial/HG or GIT rather than SVN
> or CVS.
I know I'm new on the list, but having used CVS, SVN, and Git, I would
vote no. Even with a distributed version control system (DVCS), a
project necessarily needs a main repository to house release code.
Because of the decentralized nature of a DVCS, it invariably requires
more human hours to maintain this main repository. And from what I've
seen in the short time I've been on this list, humans with the requisite
skills are quite few, and thus human hours are limited.
(This is, of course, just my opinion, and I should mention that I've
never used Mercurial, but I assume it's similar to Git.)
Besides, the project already has an SVN repository for the source code,
and it should probably use the same one for modules.
More information about the sword-devel