Uploaded image for project: 'OpenShift Over the Air'
  1. OpenShift Over the Air
  2. OTA-722

Spike to figure out what openshift/release changes are needed for custom branching strategy

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • 5
    • False
    • None
    • False
    • OTA 223

      Now that we're moving off of the default OpenShift branch strategy (i.e. work we did as part of OTA-578) , we may need to make changes.  Dropping unused CI config like this.  Somehow opting out of getting new 4.y branches cut?  Maybe docs.ci has some guidelines?

       

      Definition of Done: Creating tickets to opt out of OCP release branching strategy. 

        1. screenshot-1.png
          screenshot-1.png
          7 kB

              trking W. Trevor King
              trking W. Trevor King
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: