This page contains outdated information. Please contact Abiquo Customer Service in regard to version numbering
From now on, Abiquo will be using the * semver* release numbering system.
A full specification of semver is available at http://semver.org/
Release numbers will now include three digits, for example 2.2.x, representing:
- major version
- minor version
The key to this version system is the compatibility of the Abiquo REST API. In short, major API versions will not be backwards compatible, whereas minor versions and patches will be backwards compatible. From now on, patches will only include bug fixes, not improvements or mini-features.
An example of the new release system is given in the following table.
|2.2.0-RC.1||Release candidate that we delivered for our Beta program|
|2.2.0||Our Abiquo 2.2 product released on 17 October, also known as Abiquo 2.2 GA|
|2.3.0 ||Version of Abiquo with a new mini-feature (could have been 2.2-HF1 under the old system)|
|2.3.1||Patch (could have been be 2.2-HF2 under the old system)|
|2.3.2||Patch (could have been 2.2-HF3 under the old system)|
This new system is better aligned with software standards and ensures transparent API compatibility.
Abiquo is committed to maintaing backwards compatibility for 2 minor releases. If for some reason, backwards compatibility were not possible to maintain, Abiquo would detail the changes in the API Changelog. For example, Abiquo 2.6 should be compatible with 2.4 and 2.3. The best practice to ensure compatibility is to use the version number in the header of your API request with the media type and content type.
For major versions such as 3.0, Abiquo will make a best effort to maintain compatibility with at least the previous version. Abiquo will provide details of any changes in the API Changelog.