...
| Child pages (Children Display) |
|---|
For more about Release Numbering
...
Version 3 follows the Semantic Versioning standard :
- Patch releases with bug fixes, small changes and security patches will come out on an as-needed schedule (3.0.1, 3.0.2, etc). Compatibility with past releases under the Major.Minor is expected.
- Minor releases with new functionality will come out quarterly and will be backwards-compatible (3.1, 3.2, 3.3, etc). Compatibility with past releases under the same Major number is expected.
- Major releases would be for non-backwards-compatible API changes. None is planned at this time (4.0 and above).
Version 2 also followed the above above standards.
Goals
Predictable versioning is critical to enable multiple country implementations to share a common code base and derive shared value. This is a major goal of the 3.0 Re-Architecture. For example, Country A's implementation might fix a bug or add a new report, they would contribute that code to the open source project, and Country B could use it; and Country B could contribute something that Country A could use. For this to succeed, multiple countries using the OpenLMIS version 3 series must be upgrading to the latest Patch and Minor releases as they become available. Each country shares their bug fixes or new features with the open source community for inclusion in the new Patch or Minor release.
Pre-Releases
Starting with version 3, OpenLMIS supports pre-releases following the Semantic Versioning standard.
Currently we suggest the use of beta releases. For example, 3.0 Beta is: 3.0.0-beta.
Note: the use of the hyphen consistent with Semantic Versioning. However a pre-release SHOULD NOT use multiple hyphens. See the note in Modifiers on why.
Modifiers
Starting with version 3, OpenLMIS utilizes build modifiers to distinguish releases from intermediate or latest builds. Currently supported:
...