Mercurial > ~dholland > hg > ag > index.cgi
comparison doc/devel/versions.txt @ 0:13d2b8934445
Import AnaGram (near-)release tree into Mercurial.
| author | David A. Holland |
|---|---|
| date | Sat, 22 Dec 2007 17:52:45 -0500 |
| parents | |
| children | 12171da8943f |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:13d2b8934445 |
|---|---|
| 1 Theory of AG version numbers (as of 20060806, updated 20070603, 20070613) | |
| 2 | |
| 3 | |
| 4 - Any version of AG has a "base version number". This is 2.01 for | |
| 5 2.01, 2.40 for the first public open source version, 2.50 for the | |
| 6 stable open source version, and 3.00 for the first GTK version, | |
| 7 whenever that appears. This version goes into the Windows registry. | |
| 8 | |
| 9 - Development snapshots leading up to the first release with a | |
| 10 particular base version number are numbered with the new base version, | |
| 11 a dash, and the date or a release candidate number. Examples: | |
| 12 2.40-20070610; 2.40-RC2. | |
| 13 | |
| 14 - Stable versions have the base version followed by a dot and the | |
| 15 build number, aka patchlevel. For example: 2.40.01. | |
| 16 | |
| 17 - Every changeset committed to the stable branch causes a new build | |
| 18 and increments the build number. Needless to say, you don't commit to | |
| 19 the stable branch lightly. | |
| 20 | |
| 21 - A development version built directly from a CVS or Mercurial | |
| 22 working directory will be numbered 2.40-current, because it's difficult or | |
| 23 impossible to ascertain the proper date. Assuming the proper date is | |
| 24 even well defined. | |
| 25 | |
| 26 - A stable version built directly from a CVS or Mercurial working | |
| 27 directory will be numbered 2.40.01-current. | |
| 28 | |
| 29 - If we set up anoncvs, which if properly managed is equivalent to | |
| 30 issuing a devel snapshot every night, it should be possible to inject | |
| 31 the date. | |
| 32 |