On 6/28/22 15:01, Richard Brown wrote:
Proving you wrong is somewhat easy
We’ve been here before
The openSUSE regular release died due to lack of contributions
While the numbers of USERS of Leap are very good, the number of CONTRIBUTORS to Leap have not
And that is how we ended up in the spot - if Leap had the contributors to do what you want, we’d have done it during Leap 42 and earlier 15 releases
Leap was initially intended as a codebase which could be shaped by contributions
That seems a bit misleading. After being with SuSE then openSUSE since 7.0 pro, I don't recall and major announcement of this type or any push or request that more contributors were needed, much less what type contribution was being elicited. If the ultimate goal here is to simply nuke Leap to save manhours and just put out SLE in a community version, that has always struct me as somewhat backwards. Prior to the recent openSUSE/SLE realignment, openSUSE served as the lead and bugfix variant of what would settle down and become SLE to ensure paying customers avoided the bugs fixed in openSUSE. And many many community members contributed with QA and bug reports. That has served SuSE well. The aging nature of what comes out in Leap hasn't gone unnoticed. How Leap 15.4 was released with gcc 7.5 (which lacks many five year old C++17 features) was an indication of the problem. Python and other base development packages just makes matters worse. I don't know what the answer is. 15.4 is a damn fine release despite some package being long-in-the-tooth. The Leap model has server openSUSE well. I'd caution against throwing the baby out with the bathwater here. Somehow reasoned minds prevail, and good guidance decisions are made. I have faith that will continue here as well. -- David C. Rankin, J.D.,P.E.