recentpopularlog in

therobyouknow : convention   15

Software versioning - Wikipedia, the free encyclopedia
I like this approach, as drupal uses it and it is quite clear: "major and minor numbers, along with an alphanumeric string denoting the release type, i.e. "alpha", "beta" or "release candidate". A release train using this approach might look like 0.5, 0.6, 0.7, 0.8, 0.9 == 1.0b1, 1.0b2 (with some fixes), 1.0b3 (with more fixes) == 1.0rc1 (which, if it is stable enough) == 1.0. If 1.0rc1 turns out to have bugs which must be fixed, it turns into 1.0rc2, and so on. The important characteristic of this approach is that the first version of a given level (beta, RC, production) must be identical to the last version of the release below it: you cannot make any changes at all from the last beta to the first RC, or from the last RC to production. If you do, you must roll out another release at that lower level."
software  versioning  version  release  numbering  number  computing  development  convention  howto  programming  reference  issue  versioncontrol  control  deployment  system 
march 2010 by therobyouknow

Copy this bookmark:





to read