Rolling a Release

Below is the process used for creating and publishing a release of OpenLMIS 3.x. These steps are being documented for 3.0 Beta, and this page should be used and updated for 3.0, 3.1, and subsequent 3.x releases.

Goals

What's the purpose of publishing a release? It gives us a specific version of the software for the community to test drive and review. Beta releases will be deployed with demo data to the UAT site (uat.openlmis.org). That will be a public, visible URL that will stay the same while stakeholders test drive it. It will also have demo data and will not be automatically wiped and updated each time a new Git commit is made.

Prerequisites

Before you tag and publish the release, make sure the following are in place:

• Demo data and seed data: make sure you have demo data that is sufficient to demonstrate the features of this release. Your demo data might be built into the repositories and used in the build process OR be prepared to run a one-time database load script/command.
• Features are completed for this release and are checked in.
• All automated tests pass.
• Release notes and other documentation/publicity is ready for distribution.
• The Release Manager has certifications for remote UAT environment and a docker client installed on the machine he'll be releasing to.
  
  

Steps

When you are ready to create and publish a release:

1. Select a tag name such as '3.0.0-beta' based on the OpenLMIS Releases guidelines in the wiki.
2. In each service, set the serviceVersion property in the gradle.properties file to the version you've chosen.  Tag this commit with that same version and push to GitHub.  Do this for each service/UI module in the project, including the API services and the AngularJS UI repo.  DON'T update Blue (reference distribution) yet.
   
   1. Do we need a release branch? For the 3.0 Beta release, we do not need a release branch, only a tag. If there are any later fixes we need to apply to the 3.0 Beta, we would issue a new beta release (eg, 3.0 Beta R1) to publish additional, specific fixes.
   2. Do we need a code freeze? We do not need a "code freeze" process. We will add the tag in Git, and everyone can keep committing further work on master as usual. Updates to master will be automatically built and deployed at the Test site (test.openlmis.org), but not the UAT site (uat.openlmis.org).
   3. Confirm that your release tags appear in GitHub and in Docker Hub.
      
      1. Look under the Releases tab of each repository, eg https://github.com/OpenLMIS/openlmis-requisition/releases.
      2. Look under Tags in each Docker Hub repository.  e.g. https://hub.docker.com/r/openlmis/requisition/tags/  .   You'll need to wait for the Jenkins jobs to complete and be succesfull so give this a few minutes.
3. Update docker-compose.yml for Blue with the release chosen
   1. For each of the services deployed as a the new version on DockerHub, update the version in the docker-compose.yml file to the version you're releasing.
   2. Commit this change and tag it with the release being made.
4. Update docker-compose.yml for the UAT deployment script with the release chosen which is at https://github.com/OpenLMIS/openlmis-deployment/blob/master/deployment/uat_env/docker-compose.yml
   
   1. For each of the services deployed as a the new version on DockerHub, update the version in the docker-compose.yml file to the version you're releasing.
   2. Commit this change and tag it with the release being made.
5. Kick off each *-deploy-to-uat Jobs on Jenkins
   1. Wait about 1 minute between starting each job
   2. Confirm UAT has the deployed service.  e.g. for the auth service:  http://uat.openlmis.org/auth  check that the version is the one chosen.
6. Load demo data manually into UAT host's postgres container
7. Navigate to uat.openlmis.org and ensure it works
   
   

Once all these steps are completed and verified, the release process is complete. At this point you can conduct communication tasks such as sharing the URL and Release Announcement to stakeholders. Congratulations!