Re: [boost] How to know if CVS ready for new release?

From: Gregory Seidman (gseidman_at_[hidden])
Date: 2001-01-05 12:21:41

Beman Dawes sez:
} CVS allows multiple developers to be independently updating libraries.
} 
} But how does the Boost webmaster know if the libraries are in a consistent 
} state for a release?
} 
} How do other CVS users deal with this problem?
} 
} I guess the webmaster could post a notice of pending release a few days 
} beforehand.  Maybe it is as simple as that.
} 
} Ideas?

CVS provides version tagging, such that one can identify a particular
version as release1.9 or something. The project manager (i.e. you) sends
out a message to the various subproject maintainers asking for a consistent
version of the code to be tagged with whatever tag within the next week or
something, then checks out (or exports) with the particular version tag.
(Naturally, the subproject maintainers must cooperate in a timely manner,
but that is the case for any project with multiple developers.)

This allows the developers to continue to work beyond the stable version
being tagged but provides a stable checkpoint for release. Look into the
cvs docs for cvs tag.

} --Beman
--Greg