If we have OpenMRS dependencies, need to release the snapshot versions and then upgrade them in Bahmni Distro.
Find the current versions of the dependencies here
In some cases, if we are dependent on SNAPSHOTs, make sure that other release branches are not deploying snapshots with the same snapshot versions.
Ensure all repositories are appropriately tagged/branched, feature branches merged, all artefacts pushed to repositories (e.g. npm registry), all dependencies (like dependent libraries) reflected appropriately.
Jira cards must reflect such tasks clearly.
Ensure that all artefacts are traceable for a particular build - usually done in CI/CD
As of now, for many repositories (like bahmnniapps, bahmni core etc), we usually branch out before release, i.e when all the dev work is done and before the QA process starts. The release version refers to the name of the branch that we going to create (eg: release-0.91). Once the branching is done we will not be doing active development on that branch, only the fixes which are found as part of QA process will go into the branch (and also to master).
All other active development changes (usually for cards that for next releases) have to go into master/feature branch.