The purpose of this page is describing module release practical procedures. Mainly these steps are based on general "Release Procedure" but contains some of refinements found in the process of recent release procedures.
This page could be updated after every new Release if it's needed to provide practically proven steps of the procees. That allows to avoid waste of time to understand some terms and steps of these processes.
All release processes as a rule consist of common steps, but can have some differences which can lead to possible issues in both - the process itself and final result.
Recently there were several kind of releases been completted, therefore both of them will be described here.
- General Release of Feature Release.
This kind of Release performed to rollout some scope of planned changes, as usual it carried out on regular basis, at the end of group of sprint's cycles etc.
Let assume that we need to prepare a new release with the number: 2.2.1 and the tag: v2.2.1. In term of mentioned above general instruction, perepared release number is: X.Y.1.
- Create a new release branch out of
master- main development branch:
git checkout master (swith to the main development branch)
git pull (retrive latest changes to branch)
git checkout -b tmp-release-X.Y.0 (create a new release branch)
2. Bugfix Release.