Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

CMT Tags

Wiki Markup
For what concerns the format of tags recognized by CMT, it appears that it is a lot more liberal that what weone generally thinkthinks. Actually, CMT only considers the numbers in the tag names. The only adviceisadvice is to avoid dots. It is up to the collaboration to choose one format or the other. The format v\[0-9\]+(r\[0-9\]+(p\[0-9\]+)?)? (expressed as a perl regular expression) is just on possibility. It could also be  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\]\+)?)?.
It is up toYet, only the collaborationnumbers toare choosereally onemeaningfull format or the other. Yetto CMT, ifand CMTwe onlydo focusednot onknow theto numberswhat withinextent the tag names,v3p1 this could explainbe theconsidered bugequivalent whereto itv3r1, isor checkingeven out GlastPolicy tagged GR-v4r5 whento MyPackage-v3p1. I suspect it is askednot forfully v4r5consistent, becauseas theseen numbersin aresome thebugs, same.and Thisit must be investigated. with tests.

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

Here 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.