Development - software release life cycle
In this short article we will try to explain next stages of software release life cycles.
Examples:
- Android 11 Beta 2
- Android Q Beta 2 update
- https://developer.android.com/jetpack/androidx/versions/all-channel
Life cycle table:Â
| No. | Terminology | Description | Type |
|---|---|---|---|
| 1 | Pre-alpha | Usually available only for developers as repositiry. Application is implemented. |
Testing (different versions that are improved in next cycles) Â |
| 2 |
Alpha (pre-beta) |
Working application, but not all features are avaialble. Sometimes we have many Aplpha versions (e.g. Alpha 2, alpha-2, etc.) | |
| 3 | Beta |
Application is used by first users, that reports bugs (users are called: beta testers). Sometimes we have many Beta versions (e.g. Beta 2, beta-2, etc.) | |
| 4 |
RC (Release Candidate) |
Application version that will be changed to RTM version if everything will pass author assumptions. Sometimes we have many RC versions (e.g. RC1, RC2, etc.) Last RC that passed verifications and test is called: Stable release | |
| 5 |
RTM (Release To Manufacture, Ready To Manufacture lub Ready To Market) | Stable application and ready for users - available after premiere. |
Stable / Release (can be used according to author assumptions) |