Subversion is a free/open-source version control system. That is, Subversion manages files and directories, and the changes made to them, over time. This allows you to recover older versions of your data, or examine the history of how your data changed. In this regard, many people think of a version control system as a sort of “time machine”.

In early 2000, CollabNet, Inc. (http://www.collab.net) began seeking developers to write a replacement for CVS.

A free online book. This is the only resource you will need to learn all things about Subversion, including best practices when working with a team. Highly recommended. [ subversion overview ]

[ Subversion Clients & Plug-in Index ]

[Ankh Client for VS .Net]

If you want to ensure source control, bug tracking, requirements planning, project planning, continuous integration, a full development tool stack would have about twenty or twenty-five different tools. A lot of them require installing several different pieces—a database server, running database scripts, installing the code, installing Apache, Tomcat. One tool can be compatible with Tomcat 5, some won’t be. Just to get up with a basic life-cycle tool stack could take days or even weeks.

Once you’ve got the individual pieces, you have to provision projects across all those tools, and having the tools to work across those projects is additional work. When things are checked into source control, the right things should happen, such as running a continuous integration build, running unit tests, running code metrics, aggregating code metrics over time so the team can see a trend around code quality, and generate metrics that are important for their project.

And you normally don’t have a single place to go to get that information. Instead, you have to open each tool and work in that tool, then jump out and into some other tool. Even if those tools are all hosted inside Eclipse, they are discrete.

With Project Assist, a team runs through a simple admin tool, and with one click installs the entire stack, deploys the entire project, and then gives each developer on the team an XML file that configures Eclipse for work on the project. Developers don’t have to know URL endpoints, access codes, or project names. It’s all bundled up for them. They just open one file, and can immediately pull code, check in code, and are up and running.

http://openid.net/

this may be an answer for Single Sign On more many situations…

Those who cannot remember the past are condemned to repeat it.
– George Santayana

CVS is a version control system. It is used to record the history of your source files.

Bugs can creep in when software is modified, and may not be detected until a long time after the modification is made. With CVS, you can retrieve old versions to find which change caused the bug.

CVS can also help when a project is being worked on by multiple people, where overwriting each others changes is easy to do.

CVS solves this problem by having each developer work in his/her own directory and then instructing CVS to merge the work when each developer is done.

The CVS files are stored using RCS. For additional information regarding the format of these files see the RCS tutorial.

( tremendous CVS Guide here )

Installation:

Please read the INSTALL file for installation instructions.  Brief summary:
Save [source] file to /home/INSTALL and install from here
if it’s a *****.tgz
run ::
gzip -d cvs-1.11.17.tar.gz

then tar it out with ::
tar xvf cvs-1.11.17.tar

cd cvs-1.11.17

Next configure ::.
$ ./configure

$ make
(run the regression tests if desired)

$ make install
(create a repository if you don’t already have one)

The documentation is in the doc subdirectory.
cvs.texinfo is the main manual;

——————————————————————————-

On the web, http://www.loria.fr/~molli/cvs-index.html.

See also http://www.cvshome.org

The mailing list for CVS is info-cvs@gnu.org.  Send
subscription and removal requests for that list to
info-cvs-request@gnu.org.

CVS can do a lot of other things - I hope to learn to use it for email migration.

The official CVS site is at http://www.cvshome.org/, and the manual is here.

Ximbiot is a consulting and support company for CVS (The Concurrent Versions System).

It fills a similar role to the free software RCS, PRCS, and Aegis packages.

Cvsplot is used for collecting statistics from CVS controlled files.
Simple statistics such as how the total number of files and lines of code change against time. http://cvsplot.sourceforge.net