action #127883
closedcoordination #127031: [saga][epic] openQA for SUSE customers
coordination #127028: [epic] openQA on SLE+packagehub
Cleanup OBS project devel:openQA:Leap:15.4
Description
Motivation¶
In https://build.opensuse.org/project/show/devel:openQA:Leap:15.4 we link several packages to Factory, because we need - or at some point needed - a newer version.
There are currently 47 packages.
- Whenever one of those modules gets updated, our openQA CI checks fail because we test with a specific version, and this repo only keeps one version at a time. (I believe this is different for packages we get from Tumbleweed?)
- If we want to run openQA on SLE backports, we have to submit all 47 packages by saying that we all need those in their current version. But that is not anymore true for all packages.
I think it's sensible to keep packages there like Mojolicious-*, but I don't see why we should keep all modules there where we required a certain version in the past, if that version has reached Leap 15.4 in the meantime.
Just saying that we get bugfixes immediately would imply that we should actually add all our requirements there.
And whenever we add a module there, the list grows, but it will never shrink, unless we decide to clean it up. It's a maintenance burden.
I just went through a couple of the modules and believe some of them can be removed.
Unfortunately we don't have a history that tells us why a certain module was linked there. I wonder if this could be made easier in the future somehow.
If we ever need a newer version of one of the modules again, we can always link it, that's a fast thing to do and not something that will block us.
Suggestions¶
- Use the comment feature to add information to every linked package why we need it, which versionw e need and possibly a related ticket. I just did an example for YAML-LibYAML