-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/06/2015 05:23 AM, Michal Kubecek wrote:
On Wednesday 06 of May 2015 00:41:09 Carlos E. R. wrote:
As a stable release user, I would be very excited by every new feature that I know is available in Tumbleweed that makes into Stable. And I would be very disappointed to find out that they will not be and that I have to wait another year for them.
One thing we should keep in mind is that openSUSE kernel maintenance doesn't work very well. You could read previous discussion on this topic for details. The short story is that unless we are lucky to pick a longterm kernel version (and we haven't been for quite long), upstream stable branch is closed even before openSUSE reaches its release and after that, only security bugs and small amount of functional fixes is backported into it.
We do not have resources to do openSUSE kernel maintenance comparable to at least upstream stable branches. Piggybacking on SLE kernel maintenance allows to achieve much better maintenance with much less effort than anything else. That's why Evergreen 11.4 uses 3.0 kernel (SLE11-SP2 based) and Evergreen 13.1 is planned to use 3.12 kernel (SLE12 based - I consider a move to SLE12-SP1 but that's for a different discussion in other lists). Even if openSUSE provides features and drivers not provided or not supported by SLE (including the whole i586 architecture now), the result is still much better that anything else we can realistically think of.
Well, I am not convinced about this. Especially that SLE no longer has an x86 implementation. Thus for x86 we would end up with a kernel that has a very large number of patches, is based on an older kernel version and will be difficult for others to work with due to the large number of patches if an issue arises that is specific to x86. Plus the chances of getting help from upstream on this kernel are even slimmer than with the approach we take today. I think that for all features that SLE supports we would end up with a better kernel binary than we have in openSUSE today. However for everything else, as stated above I think the argument doesn't apply. Last but not least a backport of a driver for the latest whiz-bang USB plug in gizmo is not going to happen if it is of no interest for SLE. Then we end up in a situation where the upstream kernel supports the feature but openSUSE users cannot access it because it will not be backported because it is of no interest to SLE. Thus, just considering the kernel there are many unanswered questions. Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJVSlgcAAoJEE4FgL32d2UkR1IH/3S3ytnnzUTguV9jIzdehOks +VgNb7H3lKhggTJx+f13/d13twvtQQ/kfv5Ii8XZfscGHFq4Tb2Ly0UMjWMOLG4n vPJmlZxMnD8jdvJBQnDsTXQ5PpfeaxRTufCm4dHRGm8heJ6A7t8J4FXto3vx8GMo qpNSCk4v4ut1dRkMenZOfu4Po/GH9QzO0RV7cIAPcznU04kZK4lobiFD/gvNrvmW 2mjY4MTrMp9ATf1xEzpEu5qDWfgN/J31WLMdeYEItlZVVXizQFNnhftVonv/Now2 QorvGZqStM3M2N+8tl1xDxhmGuelFgjHo0N8eN4LKWFceO+K/MO5F1IkyKHDApw= =O9jw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org