Am Dienstag, 28. März 2017, 19:07:26 CEST schrieb Richard Brown:
I would like to take this point in the thread to
theoretical, thought experiment.
I want to make something absolutely clear, I'm asking the below as
'Richard the contributor', not 'Richard the SUSE employee', and what
am about to suggest should not be taken as an indication that SUSE
are even considering the below.
Similar disclaimer from me - nothing I say below is from "Christian the
- Release schedule that lags SLE (would only be
able to release
*AFTER* SLE, whereas Leap we can develop it WITH SLE because we're
There would be no guarantee of a release-lifecycle any different from
Leap, because such an idea could rely entirely on the sources made
available to openSUSE via SUSE's contributions to Leap.
Lifecycle is an interesting point here.
Since this would basically be "SLE recompiled": I know SLE has a much
longer lifetime, and SLE customers get security updates for several
years. Would SUSE be willing to hand out those updates for free? ;-)
(In theory, it shouldn't cause much work - but I also understand that
there's a risk that some SLE customers could switch to the free
With very rare exception SLE's longer lifetime fixes go into a LTSS
repository, only certain customers who pay for additional LTSS support
these packages aren't currently in openSUSE's obs (from what I can tell)
and I doubt that these would be added given the potential loss of a
significant revenue stream.
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