Versioning

Each release should have an unique assembly version. This make it a little more work to update the assemblies, but it enables to easily determine which version is used.

Generic Principal

Version Numbers

The version is a standard .Net version existing of 4 digits: major.minor.build.revision

The major and minor version corresponds with the version number of the corresponding eHealth component. If the eHealth component has more then 2 version parts, only the first 2 are taken into account.

Even build number are instable version. Each revision can break existing code. At one point the build will be increased making it an odd number, this means stable. Revisions of a stable versions are always backward compatible. Stable versions only get bug fix updates, extra functionality is always done in the unstable build (even when it is backward compatible)

Revision numbers are there to indicate that the library has changed. What the impact is depends if it is a stable or unstable build.

Releases

Each time the library or one of the modules changes a new release is published. The release always has the version number of the library. When a release is published where only the modules are updated, the release name will be extended with "update x". These updates are sequential numbered.

Main library

Since eHealth has no official version for the security scheme and arbitrary number is selected. The current assigned version is "1.0".

Modules

RN-Modules

Each RN services have each an individual version, all of them being "1.0". The version in the namespace of the web service takes precedence over the version indicated in the documentation.

Last edited Feb 24, 2011 at 7:55 PM by egelke, version 1

Comments

No comments yet.