Although OpenMRS Platform 2.0 was released in August of 2016, and our latest release is 2.1.3, many implementations still run on the 1.x release lines. Some of these implemenations would like to upgrade, but haven’t been able to make time to test out the process, ensure that modules are upgraded, etc.
The purpose of this sprint is to help people upgrade, by providing a common time for people to look at this, and by getting community developers to help with the work we identify.
Dates: 7-19 May 2018
Objectives
Implementations running Platform 1.x are ready to upgrade to Platform 2.x
As an implementation you can work on upgrading, and share any problems you run into.
How to Join
We’ll have a kickoff on Monday 7 May 2018, details TBD.
But you can also just try to upgrade your implementation, and share you experiences on this thread, or just pick up tickets to work on, even if you haven’t attended the kickoff.
@darius thanks alot for the updates.I would like to avail sometime and help out on priority tickets / implementations that would like to upgrade to 2.x
Thinking about how exactly to approach this sprint, instead of the usual Monday kickoff, I think we can do the following:
If you are trying an upgrade then say so on this thread. (“Hi, I’m testing the upgrade from VERSION to VERSION in an implementation in LOCATION”.) As you run into any issues (or if you’re successful), then report that back here.
If you want to help out then keep a watch here and on IRC to see what problems people are reporting. Also, you can work on the tickets that we already have.
We at eSaude Mozambique, are trying to upgrade our implementations which are majorly on OpenMRS version 1.9.2 but we recently upgraded our test environment to 1.11.5. We tried upgrading to 2.x but ran into issues that started this thread. One reason was about the community modules that were outdated and could NOT be compatible. Our upgraded implementation uses docker and one can test our platform here.Thanks @valvijo@emabota@janflowers
@ningosi see comments on the thread, we are using all the mentioned modules with 2.x u may just need to upgrade to snapshots in some cases, getting them released should not be a show stopper
That changeset is in 2.0.5, so I took the manual way of dropping that constraint and I was able to upgrade my 1.11.5 database to 2.0.5. The problem occurred when I tried to restore the constraint back, this is the error