Mailinglist Archive: opensuse-project (207 mails)

< Previous Next >
Re: [opensuse-project] Code names
  • From: Mark V <mvyver@xxxxxxxxx>
  • Date: Wed, 6 May 2009 15:28:38 +1000
  • Message-id: <389c43e40905052228k371a0699q19789d587770c7c5@xxxxxxxxxxxxxx>
On Wed, May 6, 2009 at 12:49 PM, Rajko M. <rmatov101@xxxxxxxxxxx> wrote:
On Tuesday 05 May 2009 07:51:30 pm Mark V wrote:

Unless openSUSE starts adopting end-of-life schedules that leapfrog
each other, which I think Ubuntu does, then the most distant expiry
date is the most recent release, so the release date information is

You see, that is why I proposed to have release schedule linked from Project
Overview. So many people, including you, think that support ends with new
release, which is plain wrong.

No I don't.
See the link to this page:

Which I provided before giving some examples. I did so precisely to
indicate that was the understanding I was working from, and so that
people would not not assume a different end-of-life policy (like
Ubuntu's) and leap off on tangents..... I think it is hilarious that
anyone would:
- look at that page,
- see the graphic I saw,
- read the examples I gave and the description,
- reach the conclusion you just did.

I suspect step one was skipped ;)

I think there is some confusion about terminology.
Release lifespans can overlap, which openSUSE's do. That's fine and
does not cause confusion in the name scheme I suggested - as I stated
clearly perhaps too often ;)

By 'leapfrog' I meant:
An older release has a 'expiry' date that is after a newer release,
i.e it starts from behind, passes over and ends-up ahead of the newer
release expiry date - like you do in leapfrog :)
Maybe leapfrog is played somewhere where to start from behind and jump
on top of the obstacle and stops there.... hmm analogy this is getting
weird so I'll stop now :)

My understanding is that in openSUSE if release B is made after
release A, then the expiry date of B will be after the expiry date of
See the graphic on the lifetime page. It really was clear to me ;)

Again as I've stated clearly several times, this is different to
Ubuntu, where a LTS release expiry date _can_ leapfrog a release that
occurs after the LTS release - anyway it is irrlevant _except_ that I
did want to flag that if openSUSE feel they might ever consider such a
end-of-life policy like Ubuntu's then the naming scheme suggested
would _not_ 'work', for the reasons I (badly) explained.

My fault for poor choice of terms and explanation.

The (open)SUSE is older then *buntu, and it has leapfrog end-of-life policy
since ever. It is merely that *buntu copied SUSE end-of-life policy down to
the length of term - 2 years for each release, since release date.
See for release dates of currently supported

Currently you have 10.3, 11.0 and 11.1 alive and well, ie. all supported.
Support for 10.3 will end in October 2009, shortly before 11.2 release.
The 11.0 will run supported until June 2010, and 11.1 till December 2010.

I'm not sure what made you think I suggested otherwise, anyway....


Regards, Rajko

To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx

To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx

< Previous Next >