|
There are many different versioning systems in use by software. Some use suffix
alpha
or
beta
to reflect how close the software is to full release. Some use versioning
starting at say 1.0, and going up from that until some release e.g 1.0.4 that is considered
the full release. DataNucleus uses the following versioning policy
-
When we start a release lifecycle for a product it starts at 1.0 Milestone 1 (1.0.0.M1)
-
Subsequent releases increment the milestone ... 1.0.0.M2, 1.0.0.M3 etc
-
When we feel we are close to a full release we have 1.0 Release Candidate 1 (1.0.0.RC1)
-
We have as many release candidates as necessary for stability
-
The full release is 1.0.0(.Release)
-
Any subsequent releases in that lifecycle increment the revision number,
so 1.0.1, 1.0.2 etc
The use of "Milestone" rather than "alpha" or "beta" is because all DataNucleus releases
are run against all unit tests and TCKs and so stability is typically inherent.
|
|
