




To initialy establish an RCS file type

	ci -r0.0 file

You will be promted for a description of the file and for a log
message.  The description will generally a line containing the words
"KSOS-32 Kernel source file".  The log message might be something like
"A mechanical translation of KSOS-11 Modula code into Modula-2." or
"This file was written to complement KPRa.mod."

************************************************************

Every N.N revision will be a release.  Thus, revision 2.3 would be the
3rd minor release of major release 2.  The first "real" release will
be revision 1.1, which should happen late in July 1987.

Early releases are expected correspond to project milestones as
follows:

	0.0: Milestone 7 (Modula-to-Modula2 translation)
	0.1: Milestone 8 (table initialization)
	0.2: Milestone 9 (clock & interrupts)
	0.3: Milestone 10 (setup initial process)
	0.4: Milestone 11 (support Kernel call trap)
	0.5: Milestone 12 (additional Kernel calls)
	0.6: Milestone 13 (RM05 disk driver)
	0.7: Milestone 14 (support process creation)
	0.8: Milestone 15 (DMF32 terminal driver)
	1.1: Milestone 16 (full system initialization)
	1.2: Milestone 17 (TU78 magtape driver)
	1.3: Milestone 18 (LP26 line printer driver)
	1.4: Milestone 19 (LH-DH/11 interface driver)
	2.1: Milestone 23 (demonstrate KSOS-32 system)

************************************************************

Non-released versions will have N.N.N.N[.N.N...] revision numbers.

************************************************************

Normally you will want to check out only the latest version of
KSOS-32, regardless of its release status.  The RCS "co" command has
been modified to accept a -b switch that causes selection of the
latest revision on the latest branch, rather than the latest revision
on the trunk.  The -b switch is overridden by any explicit revision
number, so it is relatively painless for csh users to alias "co" to
"co -b".
