About OpenFLUID software version numbers
From OpenFLUID
Contents |
Version numbers policy
This software version number policy is used for both Engine and Builder version numbers. This policy is applied since the 1.3.1 version (included).< /br>
The full version number is made of the following parts:
- the major number of the version (MAJOR)
- the minor number of the version (MINOR)
- the patch number of the version (PATCH)
- 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).< /br>
API compatibility
The API using the same MAJOR.MINOR version are compatible, whatever is the PATCH version. This means that a source code (e.g. simulation functions source code) developed with a M.m.x API version (e.g. 1.5.2) can be linked and compiled against any of the M.m API 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 M.m API version are not ABI-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 simulation functions .sompi or .dllmpi) developed with a M.m.p API version (e.g. 1.5.2) can be only used with an application using the same M.m.p API versions (e.g. 1.5.0, 1.5.1, 1.5.3), without any rebuild.
