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
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