Details

    • Type: Epic
    • Status: Waiting on Information
    • Priority: TBD
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Complexity:
      High
    • Epic Name:
      Begin migrating legacy UI in openmrs-core master

      Description

      After one or two administration features have been migrated to the Legacy UI and our approach has been vetted – e.g., by Darius and other /dev/5(s) – we should shift to performing the migration within the master branch rather than in a forked repository. This will ensure that any subsequent commits to Legacy UI features are applied to the module instead of to openmrs-core.

      • Transfer the openmrs-module-legacyui repository under the OpenMRS org in GitHub.
      • Commit changes to core so that the main admin screen and the first one or two administration features are removed from openmrs-core.
      • Ensure the Legacy UI module is distributed with the platform for now (e.g., in OpenMRS downloads, standalone, etc.).

      Once the initial migration has begun to take place in openmrs-core, this Epic can be closed and all subsequent migration steps can be performed within branches of openmrs-core and/or openmrs-module-legacyui repositories.

        Gliffy Diagrams

          Attachments

            Attachments-Category-Modification

              Activity

                People

                • Assignee:
                  mmehari Misikir Mehari
                  Reporter:
                  burke Burke Mamlin
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated: