Yes, a possible way is to restart SCCS history. But there is another way, which
will save the existing SCCS history untouched, and expose new SCCS history to
all developers. It can be done with a help of newest TW feature, which is
called
TW-CVS Bridge. Here is a scheme how it can be done:
Initial steps:
==========
1. Create a snapshot of current sources and checkin as revision 1.1 in CVS
repository (without old delta comments).
Solaris workspace ---> TW-CVS Bridge ---> CVS repository
2. Create OpenSolaris workspace, synchronized with CVS repository
CVS repository ---> TW-CVS Bridge ---> OpenSolaris workspace
Regular steps:
============
1. After each putback update CVS repository workspace
(with delta comments)
Solaris workspace ---> TW-CVS Bridge ---> CVS repository
(To avoid "bottleneck" this can be done with a help of autofreezepoints.)
2. Propagate the same changes to OpenSolaris workspace
CVS repository ---> TW-CVS Bridge ---> OpenSolaris workspace
For now this new OpenSolaris workspace cannot be used by external developers,
but if we provide free TW binaries with "remote bringover" (RemBo) and
put this workspace on web, developers will be able to do bringover directly
from OpenSolaris workspace.
Nikolay Molchanov
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
