TRUNK-3909, backport edit_privilege fix to 1.9.x #622
Conversation
|
@cioan is it possible to have different pull requests for each ticket? |
|
@dkayiwa Hi Daniel, I have posted the same question to @mseaton and @djazayeri and here is Darius answer: |
|
@cioan since TRUNK-3909 is not yet released, how about creating a separate pull request for it, reopen the ticket, add a new fix version, and then add a comment about the pull request for this particular ticket? Then create a separate pull request for TRUNK-3386 which is in a Ready for Work status. What do you think of that? :) |
…in a separate pull request)
|
@cioan just like you have just done a pull request for a back port of TRUNK-4025, do you mind also doing a new pull request that has only the contents of the two commit for TRUNK-3909? That way i will back port exactly was was committed for that ticket. If you feel that there are more changes which are not covered by the existing commits for those two tickets, then create a third pull request. We shall then look for a corresponding ticket, or create a new one. :) |
While working on upgrading Malawi database from 1.7 to 1.9.x I ran in the problem that is described in these openmrs core tickets: TRUNK-3386 and TRUNK-3909. I just backported into 1.9.x liquibase-update-to-latest.xml the changes included here.
Once I made this small change the database upgrade completed successfully (still testing to make sure all malawi features still work).