For several reasons (see below) I would like to upgrade our version of CVS
from 1.3 to 1.9. Since jumping this many version numbers is not always
easy, I would like to minimize the problems by asking everyone to
check in all of your changes by Tuesday, April 14, at 6 pm
==========================================================
and then
delete all your old checked out versions
========================================
and then
don't check anything out until Wednesday, April 15, noon.
=========================================================
The situation I'd like to avoid is checking out code under CVS 1.3 and
checking it back in under 1.9.
The "delete" step may not be necessary, but I am not sure about that. I
include it in the procedure to be on the safe side. If you keep your old
1.3 checkouts around, and then try to update later with 1.9, you do so at
your own risk.
So here are the reasons:
1) CVS 1.9 is really a lot better than 1.3. The most important feature is
that newer versions of CVS mark a file as dead, rather than "deleting" it.
That way you can resucitate it later much more easily. The info messages
are much better and more complete as well.
2) In looking at migrating our EPICS to the sun and R3.13, I need to do
some fancier than usual CVS manipulations. Having the modern version will
make some of these tricks easier.
3) I'd like to make clas10 a CVS server so that ACC folks can check out
our code directly on to ACC machines. Might as well invest this work on a
modern version.
4) CVS 1.9 is already installed on clas10. I just have to modify the Hall
B EPICS directory path to use it.
As point (4) implies, to make the change you should not have to do
anything. On Wednesday after lunch, when you setup_epics, you'll be using
CVS 1.9.
I hope.
-- Mark
Mark M. Ito, Thomas Jefferson National Accelerator Facility
12000 Jefferson Ave., Mail Stop 12H, Newport News, VA 23606
Email: marki@jlab.org, Office: (757)269-5295, Pager: (757)680-7175
WWW: http://claspc2.cebaf.gov/~marki/