StORE Version Numbering

Precondition: Everybody of the developmentteam is responsible for merging their code into the teamcode.

Solution: When you publish a Pundle, the generated versionnumber tells you if your code needs an update/merge with somebody elses code.

Implementation: First you publish the Pundle. If the generated version number is branched you'll have to load the highest unbranched Pundle. Next, you'll have to update/merge the loaded Pundle with your just published (branched) Pundle. After the merge you publish the Pundle again.

Example: Your parent pundle version number is 0.3, when you publish and 0.4 is generated, everything is OK, however when 0.3.1 is generated, this tells you somebody else has published the Pundle under 0.4. After publishing under 0.3.1, load 0.4 and compare/merge this one with 0.3.1. After the merge publish the Pundle under 0.5.

version list will be as followed:
0.3
0.4 (b. loaded by you)
0.3.1 (a. published by you)
0.5 (c. published by you after merge of 0.4 with 0.3.1.)