The convention for package version numbers is Vxx-yy-zz where xx is the major version field, yy the minor field, and zz is a bug fix field incremented for small changes. This version number is also the CVS tag of that version. The first version is then V00-00-00. The code manager will install this tag on the initial version of the code in the repository, and either librarians or the code manager can tag subsequent versions using the CVS command rtag.
The convention for releases is x.y.z, where x is the major release number, y the minor release, and z is a bug fix number. Thus 1.0.0 would be a major release that is rigorously tested, 1.1.0 would be a minor release based on 1.0.0 and would require less testing, and 1.1.3 would be a bug fix or fast release based on 1.1.0 and might have almost no testing. The ``production'' release would generally be a symbolic link to a major release, like 1.0.0. The ``current'' release could be a minor release, like 1.1.0. The ``test'' release could be bug fix release, such as 1.1.3. There could be many major, minor, and bug fix releases, and only a few of them might have symbolic links pointing to them with names like ``production'', ``current'', ``test'', ``fast-tracking'', etc. This labelling system allows many different releases, and the level of validation is apparent from the number.