Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-25592

Setup a branch tracking upstream's stable/2025.2 "Flamingo" release

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • openstack-manila
    • None

      Goal: 

      • As a step to upgrade OpenStack Manila in RHOSO 18 from Antelope ("stable/2023.1") to Flamingo ("stable/2025.2"), we'll need a branch to exist on gitlab.
      • This branch must be seeded with content from stable/2025.2 "Flamingo" version of openstack/manila: https://opendev.org/openstack/manila/src/branch/stable/2025.2/ 
      • It must contain any downstream-only fixes that have been carried over from past releases of RHOSO/RHOSP's OpenStack Manila component
      • The branch will have to replace "rhoso-18.0-trunk-patches" and the "rhoso-18.0-patches" branches eventually. However, doing this right away will impede the team from producing maintenance releases.

      Acceptance Criteria:

      • A branch with code from the "flamingo" release of the openstack/manila component is available on https://gitlab.cee.redhat.com/eng/openstack/manila 
      • Any downstream-only changes are cherry-picked into the branch
      • This branch inherits ACLs for code submissions from the existing branches

       

      Open Questions:

      • We are yet unsure when to merge the new branch into "rhoso-18-trunk-patches" and "rhoso-18-patches" branch. This part will need to be coordinated so that ongoing maintenance or feature releases continue to use the old content

              Unassigned Unassigned
              rhn-engineering-gpachara Goutham Pacha Ravi
              rhos-product-reldel
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: