[976] in Moira
CVS
daemon@ATHENA.MIT.EDU (Dan Winship)
Mon Jun 3 17:56:13 1996
Date: Mon, 3 Jun 96 17:55:59 -0400
From: danw@MIT.EDU (Dan Winship)
To: moiradev@MIT.EDU
Certain people (well, ok, just me actually) have suggested that the
moira source should be put under CVS control instead of RCS.
The big advantage is that it would make it much much easier for
different people to work on different sections (or even the same
section) of the tree at once without having to worry about stepping on
each other's toes, and without having to worry about scribbling on the
current working copy of the sources, or how to merge the changes back
in afterwards if they're working on some other copy of the sources. So
Karl and I could work on the Oracle server port, Dave can do whatever
he was doing with dbck, and other people can do other things, etc. CVS
also has much better facilities for branches and releases than RCS
does.
The big disadvantage is that people would have to learn cvs (not hard:
the two important commands are cvs checkout and cvs commit, and most
of the rest is automatic), and that switching it over would take some
effort.
Some propaganda from the FAQ:
| 1A.4 What is CVS useful for?
|
| CVS is intended to handle source control for files in three major
| situations:
|
| 1. Multiple developers working on the same files.
|
| The major advantage of using CVS over the simpler tools like
| RCS or SCCS is that it allows multiple developers to work on
| the same sources at the same time.
|
| The shared Repository provides a rendezvous for committed
| sources that allows developers a fair amount of flexibility in
| how often to publish (via the "commit" command) changes or
| include work committed by others (via the "update" command).
|
|
| 2. Tracking a stream of releases from a source vendor.
|
| [deleted since we're not doing that in this case]
|
| 3. Branching development.
|
| Aside from the "Vendor Branch", there are three kinds of
| "branches in development" that CVS can support:
|
| a. Your working directory can be treated as a private branch.
|
| b. A Development branch can be shared by one or more developers.
|
| c. At release time, a branch is usually created for bug fixes.
|
| (See 1D.9 and Section 4C for more info on branches.)
|
| CVS's branch support is a bit primitive, but it was designed to
| allow you to create branches, work on them for while and merge
| them back into the main line of development. You should also
| be able to merge work performed on the main branch into the
| branch you are working on. Arbitrary sharing and merging
| between branches is not currently supported.
(from http://www.loria.fr/~molli/cvs-FAQ/FAQ)
dkk says: Sounds like a good idea to me.
jweiss says: Probably, but I want to learn more about CVS first.
What do the other people currently involved in moiradev think?
-- Dan
