Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-4396

Blocking changesets when upgrading to 1.10 should direct to better explanations

    XMLWordPrintable

    Details

    • Complexity:
      Low
    • Sprint:
      Release 1.10 beta

      Description

      There are a several liquibase changesets that serve to block the upgrade to 1.10 if you don't have your DB in a known-upgradable configuration. These need to give better explanations of what is happening.

      At a minimum, we should:

      • Break the changeset introduced in TRUNK-4283 into separate changesets so you are warned of the precise error, not "error 1, 2, or 3".
      • Any changeset that blocks the upgrade needs to its failure message point to an OpenMRS permaurl, to a wiki page that describes all manual things you might need to do while upgrading.

      See https://groups.google.com/a/openmrs.org/d/msg/dev/f6RlsNx3M4w/Wljwb7qOqZgJ

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              wyclif Wyclif Luyima
              Reporter:
              darius Darius Jazayeri [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 4 hours
                  4h
                  Remaining:
                  Time Spent - 1 hour Remaining Estimate - 3 hours
                  3h
                  Logged:
                  Time Spent - 1 hour Remaining Estimate - 3 hours
                  1h