Source Code Change Control Procedures

Setting up to use CVS on your cobra account for the first time
(There's no need to do these steps again if you've already done them once)

1) Add the following lines to your .cshrc file
setenv CVSROOT ~team_4/cvsroot
setenv RCSBIN /usr/local/bin

2) Type those same two lines at the command prompt

3) Type the following two lines at the command prompt
cd
mkdir csc206
These two lines will create a sub-directory in your home directory called csc206 where your working copies of the ETA source code will be stored.

Typical CVS session

1) Switch to your csc206 directory (type cd ~/csc206)

2) Type cvs co ETA. This will checkout a copy of ETA and place a directory called ETA in your csc206 directory

The next two steps are VERY IMPORTANT

3) Type cvs editors and check to make sure the .java file you want to edit isn't being edited by someone else. If it is, call the person who's editing and ask for a time estimate on when he'll finish. You can then either skip to step (10) and end your session, or pick a different file that isn't being edited by someone.

4) Type cvs edit ETA/edu/calpoly/cpe205/fetter/src/FileName.java, where FileName.java is the name of the .java file you want to edit.

5) Use an ftp program to copy the entire ETA directory on to your home computer

6) Edit FileName.java on your home computer, compile, run, test out, etc.

7) When you're satisfied with your changes to FileName.java, ftp the copy of FileName.java on your home computer to the the ETA/edu/calpoly/cpe205/fetter/src directory on your cobra account. Make sure that your updated FileName.java compiles correctly and doesn't cause the entire ETA program to crash!

8) Back at your cobra account, type cvs commit ETA/edu/calpoly/cpe205/fetter/src/FileName.java. A vi session will pop up asking you for a description of your revision (ultra short vi tutorial: press i to enter input mode, type your description, press ESC to enter command mode, type ZZ to save and exit). Make sure you type in a meaningful description of what you changed about FileName.java

9) If you want to continue coding more .java files, type cvs update ETA, then repeat steps 3 - 8.

10) When you're all done coding for the day, type cvs release -d ETA. It should say you have 0 unaltered files. If it doesn't, then you probably forgot to commit a file you were editing. If that's the case, refer back to step 8 on how to commit files.

If during any part of this process you come across a strange error, call or email Configuration Management. Suggestions to this document that would increase clarity are welcome.