Derek Wright wrote:
... keep in mind that the *file* names have nothing to do with this discussion. the subject says "CVS branch/tag conventions". the filenames will be like so:
signup-5.x-0.1.tar.gz # official 5.x-0.1 release # 1st patch update release on stable DRUPAL-5 branch, from DRUPAL-5--0-1 tag
signup-4.7.x-1.0.tar.gz # official 4.7.x-1.0 release # initial release off the DRUPAL-4-7--1 branch, from DRUPAL-4-7--1-0 tag
signup-4.7.x-2.0-dev.tar.gz # nightly snapshot tarball from the DRUPAL-4-7--2 branch (no release tag) # (assuming there's no 4.7.x-2.0 release yet) once there's a 2.0 release, the snapshots will start being called "signup-4.7.x-2.1-dev.tar.gz, etc). ...
make sense? Not quite. Why is there an x in the filename and not the release tag? Since there should always be a 1-1 mapping between a given (official) tar ball and a given tag, there shouldn't be any difference in the way the version numbers appear (modulo case, and in other situations, some special character mappings).
Gary