On Tue, 2022-11-29 at 10:18 +0100, Bjoern Voigt wrote:
On 25.11.22 16:10, Dominique Leuenberger / DimStar wrote:
All the ports are up to the larger community and interested parties to be maintained. So if Factory moves to v3, and somebody really cares to maintain a v2 port at that time, we'll have to tripple efforts (or hopefully give up on v1 by then)
I don't think we will have tripple efforts. How likely is it, that a package bug only appears in the x86-64-v1 or x86-64-v2 package variant, but not in x86-64-v3? Maybe 2%? I think for nearly all RPM packages only some compiler switches are different.
There is at least tripple the OBS resource consumption to build a package three times, instead of once. There is at least tripped the openQA resource consumption to test three flavors instead of one. The openQA test results are, in most cases, expected to be the same. Yet, somebody has to do the work to review the failures and tag them with the corresponding bug reports (most frequently probably copying them from the STandard Tumbleweed port). Doing this on 2 extra ports is definitively more work than not doing this. And the occasional (albeit rare) case of something really being specific to x86-64-v1 (and i586, as announced, this won't be part of Tumbleweed anymore) will need to be analyzed and fixed. I hope this is not news for you - but nothing comes for free in this world. At least some heartbeets and sweat-pearls need to be invested in everything. The expectation that 'somebody is doing it' only works until there is nobody else volunteering todo the work. Cheers, Dominique