Page History

...

For what concerns the format of tags recognized by CMT, it appears that it is a lot more liberal that what one generally thinks. Actually, CMT only focus on the numbers in the tag names. It is up to the collaboration to choose one format or the other. The only advice given by CMT authors is to avoid dots, if the CMT is used together with CVS, because CVS will not like dots in the tag names.

Wiki MarkupThe format which is generally used in the CMT documentation can be expressed thanks to this perl expression : v\[0-9\]\+(r\[0\-9\]\+(p\[0\-9\]\+)?)?. For ease of reading, we will call it v*r*p* below, but one must note that v*r* can be used, but not v*p*. In some situations, CMT only focus on numbers in the tag name, so v3p1 could be considered equivalent to v3r1...

Also, CMT is meant to be used together with a version management tool, such as
CVS or subversion, but it tries not to depend on specific aspects of any of these
tools. In particular, CMT is not aware of CVS branches. Badly enough, CMT developers
uses the term "branches" for the subdirectories of a package.

...

This make me think that it is dangerous to rely on the ordering of
the output of "cmt cvstags", and dangerous to modify the cmtcvs pluggin without
consequences on the general behavior of cvs. Perhaps we could try to affect only the
selection of the first tag, but this would need to be done again each
time a new version of the pluggin is delivered by CMT authors.

Release Manager LATEST

...

The Release Manager is filtering out all the tags which do not match v\[0-9\]\+(r\[0\-9\]\+(p\[0\-9\]\+)?)?. This is a way not to take into account the tags which are applied on CVS branches, provided the developers do not use this format of tags
on the branches !

LATEST is said to be only for GlastRelease, and not for other check out packages. Actually,
I feel it as a place where to check that the head of each package stay up-to-date with
the head of its providers and clients. I would not say it is GlastRelease oriented or Engineering oriented. It is rather "cvs head" oriented, so to remember to each package owner he must keep in touch with other packages evolutions.

...