...
| Note | ||
|---|---|---|
| ||
Please leave comments if you have input/feedback. |
Submitting an issue/bug related to an OpenLMIS Release Candidate
OpenLMIS release process is outlined http://docs.openlmis.org/en/latest/conventions/versioningReleasing.html#
Add information around notifying the community. Can point implementers to the manual test cases if they want to leverage. Assigning bugs to the appropriate epic.
Potential text:
OpenLMIS will alert the community via Slack and the listservs of an upcoming release and candidate.OpenLMIS will do a full regression on release candidates. The team will follow a detailed regression test plan for each release. An example test plan: 3.2.1 Regression Test Plan. Implementers are welcome to review and leverage OpenLMIS test cases.Implementers are expected to follow the Implementation Release Process in testing the release candidate within the review period. If a bug is identified, implementers shall do a root cause analysis to ensure the bug is indeed a core bug versus any implementation specific components and code. If the bug is from the release candidate, implementers should submit a bug in the OpenLMIS Jira project and associate it to the Release Candidate Epic. For instance, the 3.2.1 Release Candidate is associated with this epic.
Updated the Review Period on ReadtheDocs on .
Submitting an issue/bug to OpenLMIS
...