On jeudi, 12 janvier 2017 16.25:43 h CET Takashi Iwai wrote:
On Thu, 12 Jan 2017 14:33:11 +0100,
Ludwig Nussel wrote:
Richard Brown wrote:
On 12 January 2017 at 12:05, Stefan Seyfried
<stefan.seyfried@googlemail.com> wrote:
On 11.01.2017 10:19, Bruno Friedmann wrote:
Also Jason, with Leap it's still not too risky to use the kernel-stable repository, I know it is not a messy devel project ;-)
Richard will not approve that option :-P
You might be surprised, see below :-P
On 12 January 2017 at 12:23, Stefan Seyfried
<stefan.seyfried@googlemail.com> wrote:
On 12.01.2017 10:06, Jiri Slaby wrote:
Despite of all that, I still prefer the SLE kernel. If people are able to make linux working on new machines, they are enough experienced to zypper ar Kernel:stable. Leap + K:stable usually cures most of the issues of new notebooks for me.
[...] So the default would be SLE kernel, but there's an option somewehere in the system (it might be a pre-added but not activated Kernel:stable repository or some script that add the repo and installs a newer kernel in addition to the old one) that allows relatively unexperienced users make their system work.
[...] I quite like the idea. In order to do it in a way that I think I could approve (or more importantly, that would be a robust, sensible way for the openSUSE Project to stake it's reputation on) we would require something like the following criteria:
- Some kind of formal submission review separate from the current [...]
- Some kind of formal testing process. This would be to catch actual [...]
- Some kind of formal release process. Which upstream kernel versions [...]
What about just using maintenance updates? All points solved there already.
Right, it can be done in a similar manner as TW, but do MR instead of SR. We may even delay the submission until 4.x.1 or later is released, where usually it catches up the pending stable fixes, and often regressions are already covered there.
(BTW, we do care security fixes on Kernel:stable, too; usually it ends up with just a +1 version bump in the case of stable branch, thus it doesn't look obvious like others.)
That "latest upstream kernel" just needs a name != kernel-default so it can coexist in the official repo.
It's a dilemma. We certainly want to avoid the growth of kernel flavors, while it looks inevitable in this case...
One another question is how to keep 3rd party drivers (Nvidia, VMware, VirtualBox, etc) working with this.
If the 3rd party support is assured, it's a really good option, IMO.
Takashi
+1 for this new way of life ... -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org