![](https://seccdn.libravatar.org/avatar/d977e460744bc9591586ffd46b60adf0.jpg?s=120&d=mm&r=g)
On 2023-09-04 04:09, Simon Lees wrote:
On 9/3/23 15:54, Richard Brown wrote:
On 2023-09-03 02:45, Simon Lees wrote: With Granite not coming until 2025 and there being no plan for a Leap 15.7, there would be a high risk of having no option for Leap users for a year or two while your idea takes form, gets developed and then released
Well from my maths a 15.6 mid 2024 + 18 months of support lands us at the end of 2025 and while now is probably too early to work on something I'd hope that we'd be able to work on something in parallel with granite development through 2025 so that we have something viable by the end of 2025, As long as all the key components of Granite are in place I also wouldn't rule out trying to release something a little before the granite release maybe within the Beta period if it helps with time frames. This might not meet every need of every existing Leap user but it would certainly be my goal to meet the needs of as many as we reasonably can so there is atleast some choice for people who don't wish to move to full tumbleweed.
Of course from these numbers we might not get the general 6 months we have for migration between current point releases but unless Granite releases in December of 2025 hopefully we can get more then a month. If toward the end of 2025 we look like we have a viable replacement but might ideally need a little more time for migration then i'd certainly consider getting the board to approach SUSE about maybe the possibility of moving from 18 months of support to maybe 21 for 15.6. But either way at this stage i'm certainly not seeing a period where there'd be a year or two of completely unsupported systems.
Given how similar the planned approach is to Leap and the fact we were able to put together a prototype in a week based off just the Marble codebase the design is mostly there and really all we are waiting for is some up to date ALP sources to hit OBS it doesn't really need to be all of Granite either if we just start working with a smaller subset of packages until the core of ALP starts to land and we build more on top of it.
There are teams (including one with your dayjobs Teamlead) looking at topics for Granite like: - reducing the packages delivered in Granite to make it more sustainably supportable - “compartmentalising” software stacks so SUSE may use different versions of stuff from the users, enabling different lifecycles either for SUSE or the users over the lifespan of Granite Neither of the above will apply to Marble. If either of these efforts has any impact on the Granite codebase then I expect your proposed timeline above to be utterly infeasible. I expect both efforts to have a dramatic impact on the internals of Granite even if the end goal is that users won’t see much of a difference compared to a SLES major release. I really do not share your optimism at all that the openSUSE Project will have the time, resources or capability to design, build, and make a reliable new distro based on Granite before the end of life of Leap 15.6 If I thought that was a viable option I absolutely wouldn’t be doing what I have been trying to bring folk together to build a Leap replacement. -- Richard Brown Distributions Architect SUSE Software Solutions Germany GmbH, Frankenstraße 146, D-90461 Nuremberg, Germany (HRB 36809, AG Nürnberg) Managing Directors/Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich