Releasing a new version of a module

If you are planning to release a new version of a module:

Get privileges to deploy release artifacts to mavenrepo.openmrs.org
Actually release the module, using mvn release:prepare release:perform - more in Maven Release Process

If the reference application includes the latest a snapshot of this module (you can check here) then update openmrs-distro-referenceapplication/pom.xml to refer to the (new) latest snapshot

Possible automation...

Steps Made to Release/Commit from Bamboo

Releasing a Module from Bamboo

Should the referenceapplication have latest?

Upload the built omod file to modules.openmrs.org

Details...

The steps you ran above with the mvn release plugin will have created your official module-x.y.omod file under omod/target, and deployed this to our maven repository so that developers can access it programmatically. For implementers to be able to access it manually, you need to upload it to the Module Repository. (You can log in using your OpenMRS ID.)

Possible automation...

Using a REST call to modules.openmrs.org

Release the version in JIRA, and create the next fixVersion.

Possible automation...

Using a REST call to JIRA

If this module is part of the reference application (check here), especially if it includes a snapshot version, then email the dev-refapp mailing list so that other interested parties know to upgrade their distros (Mirebalais, Bahmni, etc.)

Possible automation...

Should it be automated?