Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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

  • Update openmrs-distro-referenceapplication to refer to the (new) latest snapshot
 Automation could be done ...

 

 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.)

 Automation could be done ...

 Using a REST call to modules.openmrs.org

 

  • Release the version in JIRA, and create the next fixVersion.
 Automation could be done ...

 Using a REST call to JIRA

 

  • Email the dev-refapp mailing list so that other interested parties can upgrade their distros (e.g. Mirebalais would need to switch from 1.3-SNAPSHOT to 1.4-SNAPSHOT)
 Automation could be done ...

Should it be automated?

  • No labels