![](https://seccdn.libravatar.org/avatar/a4139df10120ce151e457fd1faff018d.jpg?s=120&d=mm&r=g)
On 9/4/23 19:04, Richard Brown wrote:
On 2023-09-04 10:37, Michal Suchánek wrote:
On Mon, Sep 04, 2023 at 10:13:43AM +0200, Richard Brown wrote:
On 2023-09-04 10:04, Michal Suchánek wrote:
I thought I said this clearly enough, but I'll say it very bluntly
If we do for 15.7, we won't be able to rely on the SUSE-paid employees who work on Leap to help with the Leap replacement, because they'll be busy with 15.7
And how does that change between 15.6 and 15.7?
Won't people be busy with 15.6 at 15.6 time as much as they would be busy with 15.7 at 15.7 time?
The difference is only on the ALP side - at 15.7 time it will be much more mature base to build on.
Leap 15.6 is being bootstrapped right now (https://build.opensuse.org/project/show/openSUSE:Leap:15.6)
It will be completed and off the desk of the majority of the SUSE-paid Leap folk in time for them to get something like Slowroll in place and well established by the end of Leap 15.6's end of life
If we do a 15.7, they'll be spending their time on that instead.
Meanwhile ALP will not magically become a 'more mature base to build on'
openSUSE Leap is a very Desktop-centric distribution.
None of SUSE's planned ALP products have any intention of being a Desktop-centric offering.
If openSUSE doesn't start the work now, then ALP will never be ready for the Desktop use cases we currently enjoy with Leap. (the Server use cases should be well served by the 1:1 copies of SUSE's ALP products we'll be doing)
I actually aimed to start on this a good few weeks back, but at the time SUSE's ALP packages weren't being synced to the public build service, has there been any change there? because really that's all i'm waiting on to start spending some time here. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B