I’m happy to share that releasing a platform just got a lot easier!
I got rid of a number of manual steps in the process and releasing artifacts is now done entirely by CI. You do not have to checkout code and run a single build locally nor you have to deploy artifacts to sourceforge. It all happens automatically by triggering just two CI builds (one for core and one for platform).
See updated instructions at https://wiki.openmrs.org/display/docs/OpenMRS+Platform+Release+Process#OpenMRSPlatformReleaseProcess-MaintenanceRelease
What’s next?
- Apply the config to other branches, because currently it’s done just for Platform 2.x and update wiki for other types of releases.
- Apply the same to the Reference Application release process.
- Create the release notes page automatically (script finding db diffs, committers, issues).
- Add javascript to http://openmrs.org/download page so it fetches the latest versions and download links automatically from GitHub.
- Add integration tests for platform (only Reference Application is currently covered by UI tests).
Thanks @cintiadr for your quick help with the sourceforge issue!
Those big sourceforge uploads were a blocker for many volunteer release managers!