Software Life Cycle: Branch Example

Software Life Cycle Policy | MPI Release Types | MPI Version Numbering |
General Example | Branch Example

Suppose an OEM requires several new features to be added to the existing software version 01.02.00. A branch is created, the new features are developed, a Beta release is sent to the customer for feedback, and a final release is delivered. Later, a bug is found in the field and a Patch release is built:

01.02.00.b1.Dev0 – Branch number 1, Development release number 0, of the 01.02.00 release
01.02.00.b1.Beta0 – Branch number 1, Beta release number 0, of the 01.02.00 release
01.02.00.b1.0 – Branch number 1, Release number 0, of the 01.02.00 release
01.02.00.b1.1 – Branch number 1, Release number 1 (Patch), of the 01.02.00 release

Suppose another OEM requires one additional feature in the existing software version 01.02.00, but does not want the features from branch number 1. Another branch is created from 01.02.00. And later, another required feature is added to the same branch in Release number 1.

01.02.00.b2.0 – Branch number 2, Release number 0, of the 01.02.00 release
01.02.00.b2.1 – Branch number 2, Release number 1, of the 01.02.00 release

And one more OEM requires the features from 01.02.00.b2.1, plus another new feature.

01.02.00.b2.b1.0 – Branch number 1, Release number 0, of Branch number 2, Release number 1, of the 01.02.00 release