Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> writes: > over time, I've grown a bit irritated over the misfeatures of CVS, > and I've been looking long and hard for something to use instead.
Ever since I discovered SCCS (my first SCM, 1980 or so?) I've been trying to find something better... I went from SCCS to RCS to CVS (as many people did). I didn't go (yet) to SVN. I also worked with big commercial tools like Continuus/Synergy. There have been several 'improvements' for SCCS/RCS/CVS, but none of them really survived. That's why I would be very careful selecting a non-mainstream SCM. Most problems I encountered in CVS (no atomic commits, no file/tree state versioning, no offline working) seem to be dealt with in SVN. So my question would be: what is it that makes SVN (the current mainstream SCM in our part of the software-world) unsuitable, and would it be feasible to improve SVN for that. > 9 months ago, I stumbled upon monotone (see > http://www.venge.net/monotone/), and it was basically love at first > sight. Looks nice. However, at a quick glance: - after years of development, it's still at a 0.xx version - single developer who doesn't seem to be very present at the mailing list - I cannot guess its maturaity. Any idea how many real project are actually using monotone? -- Johan
