2013/4/5 Don Simons <[email protected]>: > PS: This complication validates my decision to postpone implementing > this until after releasing version 2.7.
There is a tiny but growing movement to standardize software release numbering. It is mainly useful in a situation where package managers need to know which versions of required packages are acceptable substitutes. Basically, one should always use three numbers, e.g. 2.7.0. Then 2.7.1, 2.7.2 etc are bugfix releases; 2.8.0, 2.9.0 etc are releases that introduce new features but remain backwards compatible; 3.0.0 etc are releases that in some way are no longer compatible with 2.x.x. So the package manager knows that anything after 2.7.0 is OK, as long as the first number is 2. A bug is defined as any discrepancy between the documentation and behaviour of a program. It can be fixed either way. As long as the first digit is 0, new versions need not be backwards compatible, but if the software is already used for production, the first digit should not be 0. I'm not saying PMX, MusiXTeX or M-Tx should switch to this standard. I'm just sharing this snippet of information which you can read up for yourself at <http://semver.org>. ------------------------------- [email protected] mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
