Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-9159

Figure out a strategy for handling downstream specific code.

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Obsolete
    • Icon: Normal Normal
    • None
    • None
    • Pipelines
    • 2
    • False
    • None
    • False
    • Testable
    • No
    • No
    • No
    • Pending
    • None
    • ML Ops Sprint 1.29

      With the new automation in place via rhods-devops-infra , we always ensure that downstream is behind upstream in commits. This opens us up to potential future issues where we may need to add changes specific to downstream that don't need to go upstream. We do not have a strategy around this, the purpose of this task is to have plan/process in place to resolve these sorts of issues, confer with devops team on their plan to handle this.

      Some additional context for discussion around this in slack: https://redhat-internal.slack.com/archives/C03UA0RLSQM/p1682626169732479

              Unassigned Unassigned
              humairkhan Humair Khan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: