Whenever there is a need to branch out bahmni for a release, you can follow the below steps.
We should not do the branching for external dependencies. For example :
|
Run branch.sh with the version-to-be-released, new version and the repo_revisions.properties file as parameters.
(In all configs only default-config will be branched)
Usage is given below.
<version-to-be-released> is the current bahmni version which has to be released |
If we have to release 0.74 version, run the script with the following command. |
Emrapi needs to be released during the end of release of bahmni, create a card for it so that we don't forget to do it later. |
Basic idea - each release will have a pipeline group(s) that is suffixed by the release version. Master branch will be tracked by the future release name (so for example, if we are currently working on 0.81 and 0.80 is released, the master will be tracked as 0.81, and release-0.80 branches will have their own pipeline group. Upon branching for 0.81 release, we will start tracking the release-0.81 branch in all repositories for 0.81 pipelines, create(or copy) a new set of pipelines for 0.82 which will track master branch).
Now you are done, Go for a coffee.