Software Versioning

Major

• All features across the same version should be either 100% compatible or in rare conditions gracefully degrade.
• File formats should be compatible, all 1.x versions should open, save and edit 1.x versions.
• You will find in a new major version 
  • the flow of the application has been noticeably changed,
  • there are a significant number of new high-visibility, high-usability features,
  • the user interface has drastically changed.
• New major versions should always be able to import or open older versions.

Minor & Fixes

• New non-breaking small feature, meaning it still works with other version with the same major version
• Bug fixes that apply to everyone
• Tech support should usually make sure the end-user is on the latest minor version before going further

Build

Developer Snapshots represent the most recent status of the Centreon Development and will be released often.
Please help us to improve the product quality of Centreon. Download and test the latest versions.

Important:
These builds have not been fully tested and are under continuous development. It is not recommended for production use.

How not to get lost?

Below some examples. 
Compared to a previously released software version (if any), a new release:

• Major : 2 ou 2.0
• Minor : 2.1, 2.2, 2.3 etc ....
• Fix Release (FR) : 2.0.1, 2.0.2, 2.0.3 etc ...
• Beta : 2.1-b1 ...
• Release candidate : 2.1-RC1, RC2 2.1 ...