...
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 used.
Branch Tags
...
and tags on Branchs
I suspect there is a confusion, at least in my head, between the tags which are defining a branch, and the tags which are applied to some revision which is on a branch. I will try to distinguish between the former, which I will call "branch tags", and the latter, which I will call "tags on branches".
In some place related to the Release Manager, it is said that the tags v*r*p* should not be used on branches, and that the Release Manager is filtering out whatever tag is not v*r*p*, so to avoid branch tags. It is unclear if we mean branch tags, or tags on branches, or both.
On the other hand, sometimes we prepare a GlastRelease v*r*p*, with the p* which means one of the constituent package is branched. And the release manager HEAD is expected to be a preparation for this new GlastRelease v*r*p*, and the release manager LATEST is expected to be a preparation for HEAD... so it is expected that some tags on branches will be used in LATEST, then in HEAD, then for GlastRelease v*r*p*Here we should define how one should name a branch tag.