Re: CVS gripes?

>From my perspective (Installer and part-time-maintainer of CVS in a company
with 400 engineers) the primary problems are

1) Non-transactional checkins/rollbacks

  Engineers are ALWAYS doing partial checkins by mistake and it is difficult
to roll them back out

2) Branch management/merging is very painful

   We have maybe 7 different "versions" of the software a patch might need
to get checked into and it is incredibly painful to check them into all
versions. Also, doing major merges between branches is a struggle as well
especially when somebody has put a patch into both branches.

  We would also love to be able to have "stable" and "development" branches
and make it easier to move changes between them automatically...

3) No wide-area mirroring support

  We have engineers all over the country but CVS only in california. The
rest have to suffer with remote access. It would be nice to set up a
distributed locking/mirroring model but currently it isn't there.

4) No alternate authentication schemes

  I hacked our CVS to support LDAP/AD/SAMBA authentication even through it
is running on a linux box

5) No good bug management support

  Currently CVS really isn't integrated into a bug management tool... 'nuff
said

Of course, CVS is INCREDIBLY easy to maintain and runs quite well dispite
the above...

         --josh

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:46 2006