> Ummm - maybe I don't understand but, how can you make a RELEASE from > STABLE? Isnt STABLE following the patch branch? And RELEASE is jsut that > - what's on the CD? > > If i'm correct - then you can't do that. If I'm correct, think of it this > way: > > RELEASE = what you buy. > STABLE = is what you follow for security patches > CURRENT = is what you run as a developer. It's kinda like a Beta of the > next RELEASE.
3.7-release is what is on the cd. it is the result of building a release(8) from the source when 3.6 became 3.7-beta, solidified and changed to just 3.7. 3.7-stable is a branch of 3.7 made at the same time as 3.7-release was tagged. one can make a release(8) of the source in the branch at any date. the output would be similar base37.tgz, comp37.tgz, etc. sets to that of the 3.7-release, but with the minor -stable fixes in it. this is what the original poster is attempting. 3.7-current is the main development line of 3.7. one can make a release(8) of the source in the main development line at any date (assuming nothing is broken) and produce disk sets with new stuff from recent developments. this is what is done periodically to produce the snapshots that are available on the ftp mirrors. eventually 3.7-current turns into 3.8-beta, solidified, and then becomes 3.8. the tree is tagged as 3.8-release and branched as 3.8-stable and a release(8) is made with base38.tgz, comp38.tgz., etc. sets. these sets are put on a cd and distributed to the ftp mirrors. rinse, repeat every ~6 months.
