In order to allow partners to make use of components developed by other partners, for example using them for testing their own components, it is necessary that all partners manage appropriately the different versions of the components they develop.

Thus, based on the fact that each component has its own git repository it is proposed to use tags in the master branch (the default one) to do so. This branch contains the last version of the component that has passed your unitary tests.

Then, each stable component version should be tagged (with annotated tag) using the same numbering to the one specified in their Component Manifest (e.g. 0_0_9, 1_0_0, 1_0_1).

Example of how creating an annotated tag:

git tag -a 1_0_0 -m "Version 1_0_0 that ..."

Later on, do not forget to push the tag to the remote repository (usually named origin):

git push origin 1_0_0

In the future, it is foreseen the usage of a branch named production, so please do not use it for naming your working branches.