Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
30 lines (17 sloc) 1.93 KB

Version numbers policy

This software version number policy is used for all OpenFLUID softwares, plugins and components. This policy is applied since the 1.3.1 version (included).

The full version number is made of the following parts:

  • the MAJOR number of the version
  • the MINOR number of the version
  • the PATCH number of the version
  • an optional status (STATUS) that can be :
    • rc (release candidate) : stable version, released for users testing, some non-functional features may be incomplete (docs, translations, ...)
    • beta : almost stable version, with main features, few bugs left
    • alpha : development version, with some of the main features, maybe many bugs

Version compatibility

This software compatibility policy based on version numbers is used for both framework and software applications. This policy is applied since the 1.5 version (included).

API compatibility

The OpenFLUID API using the same MAJOR.MINOR version are compatible, whatever is the PATCH version.
This means that a source code (e.g. simulators source code) developed with a MAJOR.MINOR.x version (e.g. 1.5.2) can be linked and compiled against any of the MAJOR.MINOR versions (e.g. 1.5.0, 1.5.1, 1.5.3) without any modification. Nevertheless, a compilation/link of the source code built using the API is strongly recommended, as the MAJOR.MINOR versions are not ABI always compatibles (see below).

ABI compatibility

The ABI using the same MAJOR.MINOR.PATCH version are compatible. This means that a compiled code (e.g. binary simulators files .so or .dll) developed with a MAJOR.MINOR.PATCH version (e.g. 1.5.2) can be only used with an application using the same MAJOR.MINOR.PATCH versions (e.g. 1.5.2), without rebuilding.

You can’t perform that action at this time.