Uploaded image for project: 'RH Developer Hub Planning'
  1. RH Developer Hub Planning
  2. RHDHPLAN-853

Migrate all build infrastructure to support 2.y

Create Doc EPIC from R...Prepare for Z ReleasePrepare Test Plan (Y R...XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • 2.1
    • 1.9.0, 1.10.0, 1.11.0
    • Build
    • False
    • Hide

      None

      Show
      None
    • False
    • L

      Today we have 100s of places where 1.y is hardcoded in the bash, python, js scripts. Moving to 2.y will require refactoring scripts and in many cases we will need branching logic for 6mo while we continue to support the 1.y releases until they're EOL.

      This Feature blocks doing a 2.y release, including updates to:

      • pyxis
      • konflux-release-data
      • rhdh (gitlab)
      • rhdh-plugin-catalog (gitlab)

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              RHDH Cope
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated: