Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-46995

Build from a downstream fork

XMLWordPrintable

    • downstream-fork
    • 77
    • Yellow
    • To Do
    • CNV-12969 - Release fast - every week, every z-stream
    • 100% To Do, 0% In Progress, 0% Done
    • Hide

      2024-11-11:
      Will need to move after onboarding 3 new products to the team...

      Show
      2024-11-11: Will need to move after onboarding 3 new products to the team...

      Goal

      Build CNV 4.18.z from a downstream fork of KubeVirt, which has upstream-incompatible backports

      User Stories

      • As CNV Product Manager, I would like to introduce a feature which is not available upstream into CNV 4.16.z, in order to satisfy urgent customer demand.
      • As a CNV developer I would like to have a downstream git fork of KubeVirt, possibly under the openshift github org, where I can introduce downstream-only PRs into stable branches.
        • I would like these PRs to be rebased periodically on top of the upstream content
        • When I propose a new PR, I would like to receive an immediate feedback that the PR builds and passes sanely
        • When the PRs are rebased, I would like to receive an immediate feedback that the PR builds and passes sanely
        • As a container owner, I would like to configure CPaaS to build from the downstream fork if I choose so.

      Non-Requirements

      • List of things not included in this epic, to alleviate any doubt raised during the grooming process.

      Notes

      • Any additional details or decisions made/needed

              thason@redhat.com Tal Hason
              dkenigsb@redhat.com Dan Kenigsberg
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: