Anyone knows if the lifetime for leap is two releases + 2 months is correct.
so a lifetime of 2years + two months?
Hi
It will go via service packs which since it’s based around SLE would be ~18months and ~6 months to update to the next service pack which is usually 4.
On 2015-09-15 17:46, heelstraf wrote:
>
> Anyone knows if the lifetime for leap is two releases + 2 months is
> correct.
> so a lifetime of 2years + two months?
No. It is tied to the SLE basic lifetime cycle, whatever that may be. 
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Is there any use in repeating what was already posted 2½ hourse ago?
On 2015-09-15 21:46, hcvv wrote:
> Is there any use in repeating what was already posted 2½ hourse ago?
IMO, what I said is slightly different.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
it’s better info because i don’t understand your comment quit good.
in Roadmapis other info. what is correct 
You “think” 30months = based on 4 service packs that normally come out (18 months + each 6 months service pack)
The problem is you are asking in the wrong place. The development discussions happen on the ML’s, and the Wiki/roadmap should reflect those, and announcements get made on openSUSE News.
The Roadmap is probably the current “Plan”, it also mentions the link to current Life cycle for the normal distribution i.e. three point releases. What we know so far is those could map to three SLE service packs (“tied” is not a word I would use yet) i.e. Leap 42.1/2/3. However that’s just my interpretation based on comments read on the ML’s. So it could change between now and a formal announcement!
it was possible to select prefix leap 42.1
https://en.opensuse.org/openSUSE:Roadmap
can anyone remove the word leap of this page or add correct information?
48 days left…
And you received a response pointing you to the developers’ ML.
https://en.opensuse.org/openSUSE:Roadmap
can anyone remove the word leap of this page or add correct information?
48 days left…
Why would you want to do that?
The standard release cycle for openSUSE’s regular release **Leap **is every 12 months. The life cycle of openSUSE is documented in The Lifetime Wiki Page.
The current stable version of openSUSE is openSUSE 13.2, which was released on November 4th 2014.
The next scheduled version of openSUSE is Leap 42.1, which is scheduled to be released Nov. 4, 2015.
incorrect info for users and possible new users…
(maby for me it’s time to move to another distribution after 11 years) before the users get good information about the “plans”
48 days left to a big milestone for openSUSE and no one can answer a question for a user…
if i read the English pages and dutch pages there are very different, no more correct info and that is now months/years.
https://nl.opensuse.org/openSUSE:Roadmap
https://en.opensuse.org/openSUSE:Roadmap
It’s correct the next version/release is openSUSE Leap 42.1, so I suggest you (or I) leave it alone.
Personally speaking, I suggest you are being somewhat impatient. Making a version based on SUSE SLE opened-up sources hasn’t been done before. Perhaps some sympathy would not go amiss and so you could cut the developers some slack in this case.
The life cycle of Leap 42 is going to be longer than three years AFAICT. Isn’t that long enough for your purposes?
The English Page is correct, so you are asking about the Dutch page in an English forum…
I think you could point out the problem by editing the Dutch page to remove the wrong “Leap”. At least it should get reviewed before the actual change is made. IIRC that is how it works on the English Wiki.
Someone correct me if I’m wrong, but Leap’s mapping begins in Nov with 42.1 coinciding with SLE 12+Service Pack 1.
On Wed 16 Sep 2015 05:36:01 PM CDT, consused wrote:
consused;2728381 Wrote:
> What we know so far is those could map to three SLE service packs
> (“tied” is not a word I would use yet) i.e. Leap 42.1/2/3. However
> that’s just my interpretation based on comments read on the ML’s. So
> it could change between now and a formal announcement!
Someone correct me if I’m wrong, but Leap’s mapping begins in Nov with
42.1 coinciding with SLE 12+Service Pack 1.
Hi
Yes, this is correct and like I indicated I would expect the service
packs out around every 18 months with a 6 month overlap, now how that
works for the non-SLE packages… I know the ones (packages) I have
contributed will be kept up to date. Given that, I expect openSUSE Leap
42.4 to finally fade in around 2021…
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.44-52.10-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
That would indeed be LTS! Well I don’t recall a 42.4 being mentioned, and it would make sense for Leap 43 to coincide with SLE 13, but that could mean SLE moves to a 3 SP cycle. I guess anything is possible, and now we are speculating.
I’ve updated the Roadmap and Lifecycle pages to reflect the situation, as it currently stands today
Please notice the very heavy, repeated, and excessive use of words like ESTIMATED, and EXPECTED
There is lots of room for things to change with Leap, because Leap’s only promise is that is going to be ‘aligned with SUSE Linux Enterprise Releases’
and unlike previous openSUSE releases, where we used to often talk years in advance about how we’d try to do stuff (and then either change our mind or be faced with changing realities and end up delivering something else), SUSE only talk about SLE stuff when they know exactly what they’re doing, things are planned, prepared, and often partially underway
So, we know SUSE are currently planning SLE 12 service packs around about every year. We know SLE 12 SP1 is expected by the end of this year, which is how and why we’re releasing openSUSE Leap 42.1 based on those sources in November.
We’re therefore planning Leap Minor Releases around about every year also, but that might change, especially if SLE’s plans change.
Those Leap Minor Releases are going to have a lot in common with SLE Service Packs, not just in terms of the sources, but also probably in terms of ‘philosophy’ - I don’t want people to expect every Minor Release of Leap will contain every new version of every upstream thing every year. The purpose of Leap is to be able to provide a really stable, long term supported, version of openSUSE, so Leap Minor Releases like 42.2 a year from now will include a whole bunch of updates, but it’s stuff that we know people can move to safely, and easily, and expect to work without too much/any problem
And so, this is one reason why we’ll also be inheriting SLE’s maintenance lifecycle for Leap Minor Versions, which is 6 months after each Service Pack release.
Another reason is that about 6 months after a Minor Version is out, SUSE will stop General Support for the SLE Service Pack that Leap is based on, and so unless the openSUSE community wants to shoulder than burden and take on extra maintenance of all the SLE packages, the logical lifecycle is for a the lifecycle of the previous Leap Minor Release to end about 6 months after the newest Leap Minor release
The next Leap Major release (eg. 43.x) is expected 36-48 months from now, maybe sooner, maybe later, SUSE haven’t announced anything for SLE 13 yet, but when that starts coming together Leap 43.0 will come up with a release plan aligned with it. Until then Leap 42.x will keep on churning out minor releases as we go forward
Does this detail help?
The current plan, is that once Leap 43.0 is out, there will not be any more Leap 42.x minor releases
So, lets consider a THEORETICAL scenario where in November 2017 openSUSE releases Leap 42.3 with SLE 12 SP3 sources, then some time in 2018 we release Leap 43.0 with SLE 13 sources, but in November 2018 SUSE release SLE 12 SP4
In that scenario, openSUSE will almost certainly not make a release for openSUSE Leap 42.4
However, also in that case, we do realise that not everyone is going to want to jump from Leap 42.x to Leap 43.0 right away, and in an ideal situation they might like to wait until, lets say Leap 43.1 comes out, which may require a little bit of a longer support period of the last Leap 42.x version to make things more comfortable for the jump to 43.x
So, I’m chatting with management at SUSE about how we might deal with situations like that.
Nothing concrete yet, because frankly, this is all worrying about theoretical problems years away which might not actually become problems, but everyone seems pretty sure we’ll find a solution if problems arise, we’ll just need to be a few years down this road before we can be sure how we’ll deal with them.
On 2015-09-16 23:36, RBrownSUSE wrote:
> Does this detail help?
Yes, thank you!
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
thx for that
That will help us a lot, thanks for your efforts there.
Does this detail help?
Certainly it does, even with caveat. Grateful that you found the time to extend the discussion to the forum, also for the example of how transition to 43 could be handled with a return to a point-zero release and implications for life-cycle support.
It seems a long time ago now, when I partly selected openSUSE (actually then called SUSE Linux 10.1) for its backing by an Enterprise with similar but commercial product (SLE). So it seems that Leap 42 will begin to strengthen that position with a win-win on both sides, and could secure the future for regular openSUSE releases.
Any comments regarding openSUSE as merely a test bed for SUSE releases should remain in the past, hopefully, with Tumbleweed supporting that role.