Once we have decided that we have a release candidate from the Go pipeline, we need to ensure that the following things are taken care of. The responsibilities of the following items lies with multiple team members.
- Ensure that new relic performance data has been looked into and any severe issue reported by it has been taken care of. [One of tech leads, keep in mind that the build running at JSS may not be the last one]
- Run the pipeline (or any other automated scripts in place) to publish the artefacts to https://bahmni-repo.twhosted.com/artifacts/. Also /wiki/spaces/BAH/pages/27459587 on dropbox. [Developer]
- Deploy to the demo environment. Ensure that demo environment is working after the deployment. [Release Manager]Once the release build is finalized, run the pipeline to publish the artifacts to bintray (Release_To_Public_<branch name> pipeline in CI).
- Connect artifacts currently needs to be manually copied..Once the ci pipeline is setup to copy the artifacts, this task is not needed.
- Complete release notes. Release notes should use hyperlinks as much as possible to the implementers and features guide. [Product Managers] Also All bahmni releases page in wiki needs to be updated with details.
- Every release is likely to complete some items in the roadmap. Such item should start showing up in the features list. Hence update features pages accordingly - detailing out the items being moved. [Product Managers]Move cards completed in the release from Bahmni Development to Bahmni History. [Release Manager]
- Announce the release on #community, #tw-private in slack. [Release Manager]
- Publish a completely setup the updated Bahmni Developer VM to Atlas after testing. [DeveloperBindu]
- Tell Gurpreet (Community Lead) about the release. [Release Manager]
- Update soak test environment with the released build [Release ManagerDeploy to the demo environment. Ensure that demo environment is working after the deployment. [Bindu]