1. A periodic release is made, and accordingly a new tag is created.
After that codelines must be merged.
During the iteration the build is run and a new deployment package is created.
The build is tagged with a release number (Performix xMES <major version>.<build number/ commit Id>).
The periodic build is deployable in Test server #1 system.
Every iteration cycle, a script will create a new tag for the codebase, this will be used by the build system.
2. In the above situation, the Performix xMES project moves from xMES Ver1.0 to xMES Ver2.0.
After the iteration cycles, the integration and testing begins. After UAT, the xMES Ver1.0 branch is closed and no further activity takes place.
During UAT there could be hotfixes but it should be avoided. After the xMES Ver1.0 branch is frozen, the xMES Ver2.0 branch is created.
The xMES Ver2.0 branch is going to represent the same Performix xMES project and will have the same deployment packages.
Any hotfixes needed on the deployed xMES Ver1.0 project will be handled on the xMES Ver2.0 branch.
The bi-weekly iteration cycles will begin on the xMES Ver2.0 branch.
xMES Ver1.0 Release & xMES Ver2.0
