Magma Release Lifecycle
Last updated at 7:45 pm UTC on 27 June 2008
This page explains the process by which improvements to the Magma software are delivered.
Each Magma release is numbered sequentially. "Release 41" is frequently abbreviated "r41".
There are usually just three "active" versions of Magma, "stable," "gamma," and "development". Stable is an older version that has undergone more testing and is one-click installable from SqueakMap. "Gamma" is the version that is about to become the stable version as soon as there is sufficient comfort with its stability. Gamma versions are installable as a Monticello Configuration. Long-time gamma versions are also sometimes available from SqueakMap. The "Development" version, designated as "Alpha" or "Beta" originates from the stable or gamma version and undergoes a series of improvements.
Each set of improvements are posted to the squeaksource repository during the iteration lifecycle. Later, when a sufficient number of improvements have accumulated, a new development Monticello Configuration is posted to the same squeaksource repository. The configurations are named as follows:
[abbreviated release designation][alpha|beta|gamma||][sequence number]
for example:
r41Beta5
means, release 41, beta-level expectations, and the sequence number for indicating progress of the project relative to local individual configurations.
The expectation designations:
- alpha (analysis) - Experimental, certain things may be broken. The purpose of this version is to "try" something. The improvement may or may not be accepted.
- beta (design) - Betas are expected to "work". The entire test suite must pass for a beta to be posted. Indicates general acceptance of at least the idea of the improvement, if not the implementation.
- gamma (final testing) - The final version that becomes the next "stable". Passes test suite of course but also tested with at least one application. Further functionality will be added to a branch of this version, only bug fixes are allowed to this version.
When the goals of the entire iteration have been achieved and sufficient testing creates enough confidence to make it the "stable" release, it is made so.
