On Thu 2021-04-29, Axel Braun wrote:
-> In the end, the answer is pretty simply: You
create a submit request
against the next openSUSE Leap version.
Thats what I did for 'my' applications, they are pretty much up to date
Thank you for that!
But obviously we missed many package (KDE/qt just to
mention one. AFAIK
KDE was never part of SLE, only via backports).
Up to and including SLES 11 KDE was part of the regular distribution;
the change/consolidation came with version 12.
As said before, this 'miss' may be due to
the difficulties in merging
the SLE basis into Leap from the binary side.
...and merging from Leap 15.2 into SLE, which was some effort, too, from
what I have heard. To some extent much of this hopefully was a kick off
effort and things will be smoother going forward.
One idea I had reading this thread is to establish a list of packages/
components that shall explicitly and transparently be considered for an
update with every point release.
And then do a little web page / Wiki whatever that shows plan and status:
Component curr avail Y/N status
Digikam 83 91 Y already submitted, passes openQA
KDE 47 49 ? awaiting update to Qt 2027
Qt 2001 2027 Y comes via SLE, prepared, two openQA failures
Xaboom 432 500 N new version requires binary-only modules
for the top 50 (or whatever number).
That still requires volunteers to do the actual work (like you described
above); it does help us keep things on the radar, documents decisions, and
in turns supports timely and transparent discourse.
What do you think?