next message in archive
no next message in thread
previous message in archive
previous message in thread
Index of Subjects
Index of Subjects On Tue, 14 Jan 1997, Landon Boyd wrote: > Attn. CCN developers: > > tupdate is no longer going through CVS on CCN. This means that changes > made on CCN won't get automatically added to the distribution, and changes This has the upside that we don't have to have specific concerns about corrupting the distribution while making test and/or local changes. Unfortunately, the downside is that functionality that is added to CCN will have to be "intentionally" exported to csuite, so we had better be sure to implement adequate documentation of changes to CCN that might in future be moved to csuite. > to the distribution won't automatically take affect on CCN. Changes to How do we decide which "distribution" changes get migrated back to CCN? > the distribution should now be made on the csuite machine instead. This strikes me as introducing an additional workload in maintaining CCN, as CCN's resources are effectively diverted to producing a csuite which, although a valuable entity in its own right, benefits CCN only indirectly, as changes get migrated back to CCN. Done well, that can be a two way street, and we can evaluate the advantage of the strategy ;-) > I'm working on a mechanism which will go through the CVS log and produce a > report of what files have been changed in the last day, including the log > entries. This report will either be sent to a mailing list, made > accessible on a web page or both. Excellent. Please also bear in mind that the IP committee has requested that kind of functionality in respect to CCN, so try to make your scheme general enough to also produce a report of changes to CCN. That would probably be a useful tool to include in the distribution, so that user sites can maintain documentation of their system! > Landon This represents a paradigm shift in our understanding of CSuite development, from the model of using CCN as a live testbed for production and development, to the model (previously proposed, but not then successfully implemented) of "development environment", with results of development being a new Version which can be installed (in whole or in part) on new or existing systems. With this model we can now treat CCN as still having a dual role: First, as a "CSuite Site" that needs to be regularly and selectively upgraded, using the distribution techniques that we devise; Second , as a "pilot platform" on which we can try new ideas, under production stress, and migrate successful ideas to CSuite. + Ed Dyer Ed Dyer aa146@chebucto.ns.ca (902) H 826-7496 CCN Assistant Postmaster http://www.chebucto.ns.ca/~aa146/ W 426-4894 CSuite Technical Workshop Religion Page Editor, Chebucto Community Network http://www.chebucto.ns.ca
next message in archive
no next message in thread
previous message in archive
previous message in thread
Index of Subjects