[updated 25.08.]
If you sometimes get a little bit nervous about the particular behaviour of CVS and it's features like reanaming or directories in general, then Subversion could be your cure. One amazing feature is the binary diffing algorithm it uses…
Goal of the Subversion project is to build a revision control system that is a compelling replacement for CVS in the open source community. Interims release 0.28 is available since today, features planned for 1.0 include:
These features look pretty interesting and after 1.0 there shall be even more:
If you are using Eclipse then this Subversion Eclipse plugin or Plugin for Eclipse – Svn4Eclipse will be your thing. But there are lots of other plugins for Visual Studio, IDEA, Emacs etc. available (check the bottom of this post).
These aspects could make your software configuration management (SCM) even better, but I fear that adoption of Subversion against CVS requires time and budget and that is good because already Steve McConnel already pointed out in his amazing 36 classic mistakes for failing software projects the "silver bullet" syndrom kills a project more often than a not so optimal SCM... Silver bullet syndrom: nerds think they can make up lost time in the project by adding new and better tools – really dumb-asses (I know one) think that even for adding a bulk more people …
And Subversion: The Definitive Guide is under development and open available, is going to be published by O'Reilly and Associates later in 2003. Maybe grab a copy and give the author feedback – I like this book-beta work.
Comments
Subversion release 0.28 - the better CVS - also for Eclipse, Ema
Also Subversion's features are fully accessible through a set of nicely designed shared libraries. This makes writing new clients and language bindings a whole lot easier.
Subversion release 0.28 - the better CVS - also for Eclipse, Ema
i have used tortoise and it is APTLY NAMED.
subversion may be a good idea but the implementations are currently less attractive than cvs.
and cvs wasn't broken, you know?
perfect example of building something for the sake of building it -- not because anyone really needs it. did we REALLY NEED ANOTHER VERSIONING SYSTEM...? NO, NO, NO, WE DID NOT.
the proper way to build a better cvs would be to CONTRIBUTE TO CVS DEVELOPMENT.
less == more.