Framework Release Cycle

The Colibrio Reader Framework release cycle

We very much respect the fact that our framework is infrastructure in our customers systems. Our releases are always rigorously tested before distribution, both by unit testing, and end-to-end testing by real users.

In order to make your product management and developer experience as predictable as possible our release strategy has two phases, and two corresponding distribution channels, Release Candidate and Stable.

The RC phase for each new major release is at least 60 days. This gives you good time to plan if and how to implement new features, as well as doing the actual development and testing.

Versioning methodology

Colibrio uses Semantic Versioning (https://semver.org/) in order to make it explicitly clear how a release may affect your project.

In short Semantic Versioning works as follows:

CODE

Given a version number MAJOR.MINOR.PATCH:
* MAJOR version includes incompatible API changes,
* MINOR version adds functionality in a backwards compatible manner, and
* PATCH version make backwards compatible bug fixes.

NOTE:

Release Candidates are suffixed with "-rc.VERSION". Incompatible API changes may occur between Release Candidate versions. Any such changes will be documented in the release change log.

Experimental Releases are suffixed with "-experimental.VERSION".

Experimental Release:

An Experimental Release is an early preview release of the Framework Modules, distributed with the explicit purpose of letting you give us early feedback on features and developer experience.

Note that a Experimental Release is not covered by the Framework Modules Warranty, so do not use these releases in your public apps!

RC releases

A Release Candidate (RC) contains new, well tested features. It is the precursory step of every new major Stable release.

We encourage you to start integrating these releases into your own pipeline at your earliest convenience.

Once the 60-day RC period has passed, the release is promoted to its Stable phase.

Stable releases

A Stable release has gone through a 60-day period as a Release Candidate in which time any lingering issues will likely have been resolved.

Stable still receives bug fixes as patch releases. Please note that bug fixes will only be applied to the latest Stable release.