Configuration Management

Products are identified with a name and a version number. A version number is composed following the pattern

<branch>.<seqno>(.<branch>.<seqno>)*

No promises are made regarding development releases. They are simply snapshots taken straight from the CVS head. Both product interfaces and implementation will change between versions.

Development releases are numbered like 'b.x', where b = 0, 2, 4, ... and x = 1, 2, 3, ...

Development serie: 0.1, 0.2, 0.3, 0.4, ..., 2.1, 2.2, ..., 4.1, 4.2, ...

If a development release has become important to users, and need to be maintained without modifying the interfaces, a pl branch is created for the development release with the number b.x.pl.y, where y = 1, 2, 3, ...

Patch serie for version 2.3: 2.3.pl.1, 2.3.pl.2, 2.3.pl.3, ...

A number of commitments are made regarding stable releases.

• The release goals are met and the feature set is stable.
• Bug fixes are released in point releases.
• Product interfaces are unmodified between point releases.

Stable releases are numbered like 'b.x', where b = 1, 3, 5, ... and x = 0, 1, 2, ...

Stable serie 1: 1.0, 1.1, 1.2, 1.3, ...

Stable serie 2: 3.0, 3.1, 3.2, ...

T.B.D