Uploaded image for project: 'OpenShift Console'
  1. OpenShift Console
  2. CONSOLE-3607

Strategy for removing ACM integration code from console repository

    XMLWordPrintable

Details

    • Spike
    • Resolution: Done
    • Major
    • None
    • None
    • Multicluster
    • None
    • HAC Infra OCP - Sprint 235

    Description

      Since there was decision made stop with the ACM integration, we as a team decided that it would be better to remove the unused code from console repository, in order avoid any confusion or regressions.

      Since the work on the ACM integration was quite extensive it would be good to come up with a strategy how to remove all the code. Either by going back in the history and removing the code per story that introduce it or removing it per domain it was introduced in (... or different approach)

       

      AC:

      1. Identify all the code that was introduce during the ACM integration in the console repository and other dependent repositories (eg. release repository)
      2. Create stories that would cover removal of that identified code
      3. Based on the amount of created stories, evaluate which of them is feasible to remove in 4.14 and which we could move to 4.15 (create an epic for that if needed)

      Attachments

        Activity

          People

            rh-ee-jonjacks Jon Jackson
            jhadvig@redhat.com Jakub Hadvig
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: