RE: [Tcllib-devel] Tcllib development and release policy discussion ...

[Jeff H. <Je...@Ac...>]

I think that you are asking for a lot of extra management work
that will in the end be placed on the maintainer without a very
significant benefit.  Was the current system to anarchic to
find good checkpoints?

Jeff

> *	Whenever a maintainer for a module and/or package is
> 	satisified with the current state of his module/package
> 	an internal release is done which merges the relevant
> 	parts of the HEAD into RELEASE.
> 
> 	After the internal release the version number of the merged
> 	packages and/or modules is incremented to distinguish the
> 	current development version from the released version.
> 
> 	For each internal release the developer doing the release
> 	has to add a note to the file MERGES (in the RELEASE branch).
> 
> *	The release manager (RM) of tcllib uses the MERGES file to
> 	determine if enough or important changes have accumulated
> 	to warrant a patch, minor, or major release of Tcllib itself.