Mailinglist Archive: opensuse-project (422 mails)
|< Previous||Next >|
Re: [opensuse-project] openSUSE LTS
- From: Kim Leyendecker <kimleyendecker@xxxxxxxxxx>
- Date: Mon, 13 Dec 2010 16:41:15 +0100
- Message-id: <BLU0-SMTP495964AC97A153CF9C60D2A5120@xxxxxxx>
Anyways, a code name is just optional. What's needed is someone to
take over the work. Otherwise 11.1 is going to be declared
discontinued, repos well be removed etc in two weeks according to
the schedule (well, probably next year due to vacations).
Well, if I read this, I think he's right. I see this idea as the best:
- Organisation and official statement for the public (e.g. Pro-Linux.de, Linux-Journal, some other computer magazines and some openSUSE Newssites.
- Thinking of a name and realize the ideas we've made in the organisation-step.
- releasing of that, what's the result of the work.
So, the community and the users know what's planned and maybe they don't grade up their 11.1 installations. In fact, I've got an iso-image of 11.1 With virtualBox I'll create a virtual machine to test it, when it's out or in testing time.
THIS IS JUST OPTIONAL, AND DON'T IMPORTANT FOR MY POST
On 13.12.2010 09:43, jdd wrote:
Le 13/12/2010 04:16, Rajko M. a écrit :
On Sunday, December 12, 2010 12:36:09 pm Kim Leyendecker wrote:yes, I sent a mail on the subject with no answer :-)
Let me ask a technical question:That was another comment on this discussion; a lot of words about names and
Which kernel version will be supported?
none tried to start discuss for instance how to revive 11.1 as a test case
(kernel is 2.6.27). It is just out of support, so it can be easy to continue
adding security patches.
I would like to see some action plan what one has to do to keep 11.1 alive forexactly. I have a 11.1 server that can serve as test
another 6 months as a test is whole idea feasible.
In my humble opinion, better idea would be to think how to make upgrade pathpretty difficult
bullet proof, so that one has no fear what will happen on next change.
That will help desktop and server use cases with single effort.
IMHO we have to define what applications we have to focus on (kernel,
glibc, postfix, apache), notice the number of security fixes done for
the previous year (not except for the kernel...) and see how we can
make these fixes available.
A repo with only the patches? AFAIK I never updated my server for
month (my ISP takes care of the kernel)
Kim Leyendecker (kimleyendecker@xxxxxxxxxx)
Powered by openSUSE 11.3
This mail was composed under Linux
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
|< Previous||Next >|