[opensuse-project] long term support status
Hi, probably I'm missing something but anyone knows a current status on the "LTS" effort? I checked the wiki which was set up last year but there is nothing new apparently. Is this the right list to discuss that again or is a better/specific one somewhere else? Wolfgang -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Monday 22 November 2010 03:09:19 Wolfgang Rosenauer wrote:
Hi,
probably I'm missing something but anyone knows a current status on the "LTS" effort? I checked the wiki which was set up last year but there is nothing new apparently.
Is this the right list to discuss that again or is a better/specific one somewhere else?
Wolfgang
There's an LTS effort? That's surprising given the drafts that have been published regarding the openSUSE community's strategy...they basically toss the idea of the community focusing on 'enterprise' issues, leaving such services to external partners. I remember a number of months ago there was a proposal for an "openSLE", basically CentOS but for SLED/SLED rather than RedHat. That doesn't seem to have gone anywhere however. Perhaps others can provide more insight here. --- As an alternative solution... Our security commitment is "2 releases + 2 months". This commitment has an important knock-on effect - changing the release cycle means changing the length of security support. With our current 8-month cycle, the support period is 18 months...But if we extended our release cycle to 12 months, the support period would also be extended and become 26 months. This would return openSUSE back to its original security commitment of 2 years. I have tabled a proposal on openFATE that would move us to a 1 year cycle, but give us two releases a year in addition to extending the security period to 2 years + 2 months[1]. Basically, we release a major release once a year and then publish a minor 'bug-fix' or 'service pack' update 4-8 months later. The idea has been unpopular so far. It seems many people like the feel of "new", but are also unable (or unwilling) to use the Build Service to update their desired software...under such conditions, they understandably do not want a longer release cycle. Anyway, if you think it's a good idea, vote it up and tell your friends. If you think it's a bad idea, vote it down and tell your friends. Refilwe [1] https://features.opensuse.org/310122 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Le 22/11/2010 10:27, Refilwe Seete a écrit :
There's an LTS effort?
there could be :-) but I think we don't have the manpower right now to do so. However I asked a question recently, but with absolutely no answer :-(: what we could pretty easily is to *document* the task to make a server uptodate on the long time (having an outdated desktop is not really a problem; IMHO, very little major bug arise after two years and desktop users usually want recent products). I mean: on a server one need apache, postfix, dovecot, squirellmail (just examples), I mean a pretty small number of products. Of course kernel. what we would have to do for keeping the server safe is to list to begin with the application we focus on, then list the mailing-lists that give security updates and the HOWTO use them. Server admin are (should be) at ease with product updating, let alone because most wiki/CMS are not at all managed by openSUSE updates. Let me say also that my kernel updates are managed by my ISP, who provides said "network boot", that is a boot for the hosted servers on the ISP kernel. such a documentation could grow (adding more applications) and may be some time give a more complete support. jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Am 22.11.2010 10:27, schrieb Refilwe Seete:
On Monday 22 November 2010 03:09:19 Wolfgang Rosenauer wrote:
probably I'm missing something but anyone knows a current status on the "LTS" effort? I checked the wiki which was set up last year but there is nothing new apparently.
Is this the right list to discuss that again or is a better/specific one somewhere else?
There's an LTS effort?
That's surprising given the drafts that have been published regarding the openSUSE community's strategy...they basically toss the idea of the community focusing on 'enterprise' issues, leaving such services to external partners.
I remember a number of months ago there was a proposal for an "openSLE", basically CentOS but for SLED/SLED rather than RedHat. That doesn't seem to have gone anywhere however. Perhaps others can provide more insight here.
That is what I referred to. But AFAIK it was not decided if it would be a SLE clone or some kind of openSUSE LTS project. I'm not sure if I want to touch the release cycle (and I think that two years is still not enough anyway). If there are no news about the "openSLE" thing I'm wondering how we can do something to start with. While I would like to see something like CentOS for SLE I don't think that's easy if Novell doesn't like it (what they apparently do). So option 3 on http://www.zenez.com/mediawiki/openSLE-openSUSE_LTS-wiki/index.php/Pro%27s_a...: would be the most practical approach. What I could think of would be the following: The community could take over maintenance for a certain openSUSE release after it's phased out by Novell. Take 11.1 as example for that as it goes out of maintenance by end of this year and was the base for SLE11. How about continueing to maintain it as good as possible as a community effort? This would need some agreement what to maintain as we never can maintain everything from the original 11.1 release. I think that might be doable, if - service providers who roll out openSUSE as servers - community members who already do SLE11 updates (yes, I hope that Novell employees who are active in the openSUSE community would help us doing that as it's almost no additional work for them) - interested packagers and parties help in doing that. There are some details to work out but the most critical part is if we get enough manpower together so that it makes sense to start. Wolfgang -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-11-22 at 04:27 -0500, Refilwe Seete wrote:
As an alternative solution...
Our security commitment is "2 releases + 2 months". This commitment has an important knock-on effect - changing the release cycle means changing the length of security support.
I like this very much! I have said several times that I know several people (soho), some of them contributors, that have left the distro because 18 months is too little.
With our current 8-month cycle, the support period is 18 months...But if we extended our release cycle to 12 months, the support period would also be extended and become 26 months. This would return openSUSE back to its original security commitment of 2 years.
I have tabled a proposal on openFATE that would move us to a 1 year cycle, but give us two releases a year in addition to extending the security period to 2 years + 2 months[1]. Basically, we release a major release once a year and then publish a minor 'bug-fix' or 'service pack' update 4-8 months later.
That would be nice. It could be one "standard" release and one "rolling" release.
The idea has been unpopular so far.
It seems many people like the feel of "new", but are also unable (or unwilling) to use the Build Service to update their desired software...under such conditions, they understandably do not want a longer release cycle.
I do not know if I want a longer release cycle, but I do want indeed a longer maintenance period, even if the last leg of the period is strictly security bugs only, as in the old SuSE times.
Anyway, if you think it's a good idea, vote it up and tell your friends. If you think it's a bad idea, vote it down and tell your friends.
I'll do. Reposting to the Spanish list.
Refilwe [1] https://features.opensuse.org/310122
- -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkzqzQgACgkQtTMYHG2NR9WpmACeIYkIZ0Z4N0xghTxtZEnx+FmM 3l8AnRtNmGAKtU6vgpSdzYHYCIX4ntJj =XRDs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Wolfgang Rosenauer wrote:
Hi,
probably I'm missing something but anyone knows a current status on the "LTS" effort? I checked the wiki which was set up last year but there is nothing new apparently.
IIRC, Boyd Lynn Gerber started an LTS project - I'm on the mailing list, but I have not seen any activity for quite a while. -- Per Jessen, Zürich (4.2°C) -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Am 22.11.2010 11:02, schrieb Per Jessen:
Wolfgang Rosenauer wrote:
Hi,
probably I'm missing something but anyone knows a current status on the "LTS" effort? I checked the wiki which was set up last year but there is nothing new apparently.
IIRC, Boyd Lynn Gerber started an LTS project - I'm on the mailing list, but I have not seen any activity for quite a while.
Actually I _think_ I'm on this list as well ;-) Wolfgang -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
participants (5)
-
Carlos E. R. -
jdd -
Per Jessen -
Refilwe Seete -
Wolfgang Rosenauer