We will be using the
CVS services of
SourceForge.
Both
anonymous and developer access is available, although updates to
anonymous CVS are delayed by up to 24 hours behind developer CVS, so
keep this in mind when checking out the project from anonymous CVS.
There are plenty of tutorials online about how to use CVS, as well as
books, so I will not duplicate those here. There are some good
tutorials online
here
and
here.
Project conventions:
Some basic rules we will follow for this project:
1) We will avoid branching as much as possible, limited to major
releases, and possibly some significant minor releases.
2) There shall be no features added to a branch other than the main
branch. Only bug fixes are allowed in a release branch.
3) No branches off of release branches are allowed.
Release branch tag conventions:
For a release branch, leading up to a "shipped"
release, we will use the following convention:
RB_
ver
example: RB_1_0, RB_1_0_1a
For a "shipped" release, we will use the following
convention:
REL_
ver
example: REL_1_0, REL_1_0_1a
Before a major refactoring of the code (ie, a code
"experiment"), we will tag the code in this way:
BREF_
initials_
mmddyyyy example:
BREF_JB_03142007
After a major refactoring of the code, we will tag
the code in this way:
AREF_
initials_mmddyyyy
example: AREF_JB_03152007
Project specific instructions:
A quick tutorial on using CVS on
SourceForge is available
here
and some
in-depth documentation is available
here. Here
is a summary
(please read the originals for details):
Checking out the project from anonymous CVS:
cvs -d:pserver:anonymous@greenengine.cvs.sourceforge.net:/cvsroot/greenengine login
(press the Enter key when asked for a password)
cvs -z3 -d:pserver:anonymous@greenengine.cvs.sourceforge.net:/cvsroot/greenengine co -P greenengine
After you have checked out the project, you can execute cvs commands in
the project directory without the -d parameter.
Developer Access to CVS:
export CVS_RSH=ssh
cvs -z3 -d:ext:developername@greenengine.cvs.sourceforge.net:/cvsroot/greenengine co -P greenengine
You can, of course, set your CVSROOT environment variable appropriately
to avoid typing the -d option for every cvs command.