| Warning |
|---|
The current approach is not purely incremental. This page is moved to the 'archives' for reference. |
Epic: Legacy Migration Path
Description: Should the OpenLMIS community decide on an incremental re-architecture approach, the following document applies. The OpenLMIS Community commits to supporting countries with existing implementations in researching whether upgrading their implementation to a newer version of OpenLMIS makes sense for their situation. However, the community should understand that upgrading to OpenLMIS (post 3.0) will likely result in a decrease to the available feature set when compared to a country’s current implementation. The country or implementer driving the migration will be responsible for requesting extension points from the core team (as needed) and building any country specific functionality in one or more modules. As such, any decision to migrate should be thoroughly investigated. See the below table for activities the community can assist a prospective migrating party in undertaking.
Activity | Community will Assist |
Creation of a data migration script | Yes – via community forums |
Creating core extension points | Yes |
Creation of contributed modules (including functionality removed to achieve 3.0+) | No |
Provide training on 3.0+ feature set | Yes – via community forums |
Deploying 3.0+ code | No |
Modifying reference UI to meet country requirements | No |
Some definitions:
VIMS = The last pull from the VIMS BitBucket to the OpenLMIS master branch [December 2015]
...