When DragonFly hits release..

[Matthew Dillon]

   Well, I think for at least the next year and a half we are not going
   to have branches.  Instead we will have slip tags.  It's just as well,
   because we do not have the developer resources to track multiple branches
   yet.

   If people have suggestions for tag names I'm all ears.  I was thinking:

   releaseX_Y	Specific official release, build and regression tested,
		including security fixes.  A sub-sub version (Z) would
		be embedded in the uname to differentiate between updates
		to a release, but not be incorporated into the tag name.

   release	Current official release.

   developer	Developers who want to be cutting edge but still be
		'reasonably' stable, with occassional glitches.

   HEAD		Absolute latest work, might have build and other issues.

   
   Not being branches, slip tags are limited in scope.  It might not be 
   possible to incorporate a security fix into a particular release tag,
   for example, all we would be able to do is tell people to upgrade to
   a later release.  When we are able to stabilize the system interfaces
   (about a year and a half from now) this won't be a big deal.

						-Matt