Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. OpenMRS ID: This is the basic account that you create when associating with OpenMRS.
  2. OpenMRS.org account: This is not your OpenMRS ID, it is a WordPress account where you will need to create a blog post once you release the OpenMRS version. Create a new case at OpenMRS helpdesk requesting access for the OpenMRS.org account. Help desk will create the account for you.
  3. CI Bamboo Account: The actual release takes place here. You will need your access to this account to finally release the version. Create a new case at OpenMRS helpdesk requesting access for this account.
  4. Administrator role in JIRA for Reference Application Project: Request for being an administrator of the Reference Application project in JIRA from a current Administrator - Presently Darius Jazayeri is an administrator for the project.

Release Process:

Begin the process of release management:

  1. Analyse the release stage requirements for the particular release by following  Technical Road Map.
  2. Attend and organize Project Management Meeting and Design Forum to communicate and decide on what needs to be done throughout the release process.
  3. Try to create a release management process to help you and others understand the tasks to be done. This can be done on OpenMRS Talk as done here.
  4. Search for tickets in JIRA that have the release version or having tag as OpenMRS 2.x(The version to be released)  and have them fixed before having that module released.
  5. Make sure that for each module that needs a new version to be released, that the user documentation in the new wiki page has been updated to reflect the UI changes if necessary.
  6. Set an initial deadline to release all the modules scheduled to be included in the release and request each modules owner to release the modules in that time. Excepting the Reference Application, Reference Application distro , Reference Application, reference demo data, reference metadata, all the other module can be released by this time. For the modules already existing in the release bundle check in OpenMRS github account if any new changes have been made after the previous release if don't request the any action just include it in the release management process that it is in a release ready state. If there are changes request the module owners if they would like to release a new version to be included in the new OpenMRS release.
  7. A module should be released and available via Addons to be considered released. Please verify that each module has been released properly.

Releasing the Reference Metadata module:

Each release of Reference Application should be preceded with a release of the Reference Metadata module in a version matching the Reference Application version. The release is typically done by the Reference Metadata module maintainers, but as a release manager you need to make sure it happens.


Required accounts:

  1. CIEL dictionary dropbox account (optional for releasing the Reference Metadata module)account This account is updated with the latest CIEL dictionary and each OpenMRS 2.x release includes the latest released CIEL dictionary. 
    Andrew Kanter manages the account and you would need to mail him  requesting the access for the account. CIEL dictionary is an SQL dump file.
  2. mdsbuilder (optional for releasing the Reference Metadata module): It is an OpenMRS server and you would need access to the server, an account in the OpenMRS account and also the mysql openmrs_user/root credentials, please create a new case requesting these accounts at OpenMRS helpdesk . For requesting server access you need to have an SSH key pair. (For windows users new to using an SSH key pair for accessing a linux server , this guide might help you create one. You will have to request helpdesk to give access to this SSH key).

Release steps: