The failed messaging job should be fixed now. I need to remove the dalmatian jobs from the set of required jobs then we can merge this.

I have removed Dalmatian jobs from the list of required checks. I also trivially reworded a commit message and force pushed to cause these changes to get picked up.

per the release candance adjustment resolution
https://github.com/openstack/governance/blob/master/resolutions/20220210-release-cadence-adjustment.rst
and the unmainened branch policy https://github.com/openstack/governance/blob/master/resolutions/20230724-unmaintained-branches.rst

each openstack release is only maintained for 18 months.

after 18 months form release if the release is a skip level upgrade reelase (the 20**.1 releases) it is eligable to move form a stable/20**.1 branch to unmaintaiend/20**.1
however it is intened that the preire unmaintaned/ branch will move to EOL when the next is created.

non slurp release i.e. the 20**.2 release are not eligiable to move form stable to unmaintained and go eol once they are 18 months old.

with that context i woudl recomemnt only testing master and the most recent SLURP release which iscurrently stable/2025.1

when 2026.1 is released then that woudl replace stable/2025.1

this way you are testing the most recent long term supproted release and the current development release.

also of relevent to this are

https://github.com/openstack/governance/blob/master/resolutions/20231114-amend-unmaintained-status.rst
and https://github.com/openstack/governance/blob/master/reference/project-testing-interface.rst#linux-distributions
in particalre https://github.com/openstack/governance/blob/master/reference/project-testing-interface.rst#upgrade-testing

effectivly what thise all mean for gophercloud is when openstack add a new disto to the testign runtime when a new major release happens we try to supprot teh new and old for at least 1 release

ideally we try to to also do that on a slurp release although that is not strictly required.

so by stickign to master and the most recent slurp you shoudl minimise the impact on when you have to update the ci job to effectivly once a year with the disto changing every 2 years or so.

that a long way to say you shoudl probably remove the caracal 2024.1 job as well as it is not unmtianeed with the release of falmingo 2025.2

current supported or stable reelase are 2025.2(flamingo), 2025.1(epoxy) and 2024.2(dalmatian)

coverage: 63.823%. remained the same
when pulling 3260d63 on shiftstack:add-epoxy
into 1b200e1 on gophercloud:main.

Failed to backport PR to v2 branch. See logs for details.