...
| Wiki Markup |
|---|
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 considers the numbers in the tag names. The only advice is to avoid dots. It is up to the collaboration to choose one format or the other. The 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\]\+)?)?. Yet, only the numbers are really meaningfull to CMT, and we do not know to what extent the tag v3p1 could be considered equivalent to v3r1, or even to MyPackage-v3p1. I suspect it is not fully consistent, as seen in some bugs, and it must be investigated. |
Release Manager LATEST
Here we should define/describe how the release manager is selecting
the package tags for the assembly of LATEST.
Release Manager HEAD
| Wiki Markup |
|---|
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 ! |
Release Manager HEAD
The tags which are used in a HEAD build are explicitly defined one by one, under the controll of Navid. I guess the same rules as LATEST apply, but perhaps it is possible, for specific cases, that branches tas will be usedHere we should define/describe how the release manager is selecting
the package tags for the assembly of LATEST.
Branch Tags
Here we should define how one should name a branch tag.