Packaging and Releasing the OpenLMIS Reporting Stack

The release versioning for the reporting stack follows the same semver standards as OpenLMIS and is similarly released through the ref-distro.

Release Process

We will release the Reporting Stack following the same protocol as releases of microservices. The standard will be to release the Reporting Stack in the same release cycle as Ref Distro, with exceptions made for an individual Reporting Stack release in exceptional circumstances.

Active Development

Teams working on the reporting stack use gitflow to merge changes into master.

Code Freeze

Shift all work to cleanup and bug fixes, i.e. no new feature development. Write draft release notes.

Publish Release Candidate

Publish a release candidate and share it with the OpenLMIS community.

Review Period

Release candidate is reviewed by the OpenLMIS community, any bugs are entered into JIRA.

Fix Critical Issues

If there are any critical bugs or issues associated with this release candidate those are fixed and a new release candidate is released to the community for review.

Publish Release

If there are no critical bugs or issues, finalize the release notes and publish the release.

Implementation Release Process

TBD based on experience with an implementation.