Status: Stable
3.1.2 is a stable release, and all users of OpenLMIS version 3 are encouraged to adopt it.
Release Notes
The release of 3.1.2 is primarily a bug-fix and performance release, with over 20 bugs fixed since 3.1.0 and major improvements in performance.
This release also includes notable new features:
- capture VVM (vaccine vial monitor) values while recording stock data
- OLMIS-2654Getting issue details... STATUS and - OLMIS-2663Getting issue details... STATUS - new admin screens to view Supervisory Nodes
- OLMIS-2280Getting issue details... STATUS
All changes are backwards-compatible. Any changes to data include automated migrations from previous versions back to 3.0.1. Any exceptions are identified in the Components sections below.
For background information on OpenLMIS version 3's new micro-service architecture, extensions/customizations, and upgrade paths for OpenLMIS versions 1 and 2, see the 3.0.0 Release - 1 March 2017.
Download or View on GitHub
OpenLMIS Reference Distribution 3.1.2
Components
Version 3.1.2 of the Reference Distribution has updated versions of the components listed below. The Reference Distribution bundles these component together using Docker to create a complete OpenLMIS instance.
For background info about how components and the Reference Distribution are versioned, see Versioning and Releasing.
Reference UI 5.0.2
The reference UI bundles the following UI components together:
ui-components 5.x.y
blah...
auth-ui 5.0.0
b
referencedata-ui 5.0.0
b
fulfillment-ui 5.0.0
b
report-ui 5.0.0
b
requisition-ui 5.0.0
b
stockmanagement-ui 1.0.0-beta
same
Requisition Service 4.0.0
This ...
This list of changes comes from the Requisition CHANGELOG.
Fulfillment Service 4.0.0
This c...
This list of changes comes from the Fulfillment CHANGELOG.
Stock Management 1.0.0-beta
BLAH
Reference Data Service 7.0.0
Breaking changes (impact APIs and developers, but not impact to users and their data):...
This list of changes comes from the Referencedata CHANGELOG.
Auth Service 3.0.3
This component includes improvements which are backwards-compatible:
- OLMIS-2155: Migrated service to Spring Boot 1.4.1
- Performance issue with custom ZonedDateTimeAttributeConverter.
- OLMIS-2267: Remove email from auth-user, pull email from referenceda service
- This change was part of making email optional for user setup.
Dev and tooling updates made in a backwards-compatible manner:
- OLMIS-1972: Update Postgres from 9.4 to 9.6
- This upgrade will apply automatically and all data will migrate.
- Update Docker Dev Image for builds from v1 to v2
- Moves the sync_transifex.sh script out of each service and into the Docker Dev Image.
This list of changes comes from the Auth CHANGELOG.
Notification Service 3.0.2
This component includes bug fixes, security and performance improvements (backwards-compatible):
- OLMIS-1972: Update Postgres from 9.4 to 9.6
- Update Docker Dev Image for builds from v1 to v2
This list of changes comes from the Notification CHANGELOG.
OpenLMIS PostgreSQL Docker Image
PostgreSQL has been upgraded from 9.4 to 9.6 in the docker image that is used by the Reference Distribution.
This upgrade will apply automatically and all data will migrate.
Components with No Changes
Other tooling components have not changed, including: the logging service, the tailored docker-ized distribution of nginx and postgres, and a library for shared Java code called service-util.
Contributions
Thanks to the Malawi implementation team who has contributed a number of pull requests to add functionality and customization in ways that have global shared benefit:
Reference Data pull requests #11 (adding extraData to Facility entity) and #12 (Requisition Group endpoints allow associating facilities and schedules)
Requisition pull requests #17 through #22, including additional Demo Data, new report filter parameters, and new facility search parameters
Requisition UI pull request #1 (Add Program Filter to Approve Requisition Page)
Also, thanks to everyone who contributed to OpenLMIS 3.0.0.
Further Resources
View all JIRA Tickets in 3.1.2.
Learn more about the OpenLMIS Community and how to get involved!