On 2017-05-25, nrickert <nrickert@no-mx.forums.microfocus.com> wrote:
> I should add that I’m just an ordinary openSUSE user. I do not have any
> special inside information. But my interpretation of the various
> nuggets of information is different from yours.
Thank you for the clarification. Even if you have no special inside information, I’m sure your interpretation is much
more likely to be correct than mine.
I have some fun insider information which adds to what nrickert said and hopefully really dispels the myth of who is the development platform for whom 
Because Leap is based on SLE, we need SLE packages and sources before we can start developing them in earnest.
SUSE have partners, and those partners are often working with them on exciting new stuff, covered under Non-disclosure agreements.
These NDAs end when SLE reaches its Beta period.
This beta period is therefore when Leap development really kicks off.
openSUSE Leaps Alpha phase is therefore starting when SLE is already at Beta, and this trend continues, with Leaps Beta period (now) starting around the same time as SLE reaching its RC phase.
Ultimately, we sync up near the end, because there are a lot more legal and partner/customer approval time required for SLE before it releases, so Leap and SLE have similar release dates.
but if you wanted to, you could argue that SLE is (part of) the development code base for Leap
in reality, the old ‘upstream’ vs ‘downstream’ arguments all really fall apart with openSUSE these days
Tumbleweed is upstream of SLE, with new SLE major versions based on TW and all minor version changes being contributed to TW first.
TW is upstream of Leap, with new Leap versions containing significant amounts of stuff from TW
Leap is downstream of SLE, with new Leap versions based on SLE
SLE is downstream of Leap, with new SLE minor versions adopting stuff from previous Leap minor versions
its a lot easier to say we’re all working on each other’s stuff together, and all of them should be working all the time, so there is no longer the excuse of “meh it’s just the development branch” when it’s not behaving right.
On 2017-05-30, RBrownSUSE <RBrownSUSE@no-mx.forums.microfocus.com> wrote:
> I have some fun insider information which adds to what nrickert said and
> hopefully really dispels the myth of who is the development platform for
> whom 
Thanks very much for your comprehensive and clear explanation. Just one clarification, when you say…
> but if you wanted to, you could argue that SLE is (part of) the
> development code base for Leap
… this suggests that openFATE would impact upon SLE development?
That’s exactly the problem galko_ferdinand](https://forums.opensuse.org/member.php/73901-galko_ferdinand) was trying to point out. Visitors of the “Roadmap” page expect information about the plans for the future and how things are done. A few years ago, the page clearly served this purpose. I guess from your reply that you see the page to be a history of how the current release came about. That’s also valid and I’ll move that information to a separate section with appropriate heading after adding information on Leap 15.
I’ve been checking the roadmap page many times over the last 6 months to see whether there is any new information on the next release. Only today I found out about Leap 15 because I specifically googled Leap 43.x.
Best regards,
Joachim
It also think this is an area needing improvement. I love the way Solus keeps their users informed on new development not just what packages were released. Definitely helps to grow popularity.
Completely agree.
I LOVE OPENSUSE !!! Never a dull moment here! Never forgetting “to have a lot of fun!”
How many other distros can make that claim?!
Even our numbering is a blast!
For those wanting to experiment, Built 65.1 of openSUSE 15.0 is now available HERE.
Yesterday, I installed into an existing encrypted LVM. The install went well. Unfortunately, the newly installed system would not boot. (The installer had failed to create “/etc/crypttab”). I managed to “repair” that, and the system is now up and running. I’ll report the bug shortly.