Release Process

 

On this page:

Overview

 

Release Planning

How do things make it into a specific release or on the Detailed Technical Roadmap  See the page on Technical Roadmap Planning.

OpenMRS has two "products" that are released:

  • OpenMRS/Reference Application – this is the web application (reference application) that people generally think of when they think about OpenMRS as an application. For specifics on releasing a new version of the reference application, refer to the OpenMRS Reference Application Release Process page.


  • OpenMRS Platform – this is the API and web services used by OpenMRS and made available so that it can be used by other web applications.

Being the Release Manager

Release Process

OpenMRS develops two software products OpenMRS Platform and OpenMRS Reference Application based on OpenMRS Platform. The release process for both the products is different. The release process for OpenMRS Platform and OpenMRS Reference Application are as described in detail in these links:

Release Manager Selection

Before applying for being a Release Manager please note that release process is quite involved and requires time commitment in bursts.

The selection process of release manager involves announcing the requirement for a new volunteer release manager for a specific release, time till which responses will be accepted and announcing a mentor that will guide the new volunteer release manager. After new volunteers respond for being the release manager, these following criteria are taken into consideration for selecting a candidate:

  • First Time  Release Manager? (they are given first preference)

  • Previous Engagement with OpenMRS community in OpenMRS Talk

  • Previous development work in the community (any contributions to code visible in github) 

  • Basic DevOps Experience (Creating an SSH Key, logging into a remote server, sending and receiving a file from a remote server, managing tomcat in a remote server)