Am Samstag, 28. Dezember 2019, 01:25:59 CET schrieb Michal Kubecek:
On Fri, Dec 27, 2019 at 02:40:01PM +0100, Hans-Peter Jansen wrote:
Hi Ludwig,
kernel-source (5.3.15 -> 5.3.16)
Fun fact, we're 4 revisions in front of TW now
Looking only at version numbers is rather deceiving when talking about Leap kernels. For example, only about one third of the patches in current openSUSE-15.2 kernel come from upstream stable. Also, upstream stable-5.3.y branch has been already announced as finished (with 5.3.18) so that future Leap 15.2 kernels are all going to have "version 5.3.18" even if they are going to get many more new patches.
To be honest, it really escapes me to not base a long term distribution kernel on a long term kernel. According to Takashi, the kernel team needs to backport the changes manually anyway, hence it doesn't make a *big* difference, but merging can fail in funny ways...
(yeah, Dominique explained the reasons: upgrade to 5.4.* was blocked by openqa due to kexec issues..).
That's one part of the reason. The other is that our workflow does not allow submitting another kernel (in this case some later 5.3.y) without superseding the previous one (in this case, first 5.4.y). However, this unfortunate situation is quite rare, usually it doesn't take more than 2-3 weeks to get a new kernel release through; so I don't think it would be worth the effort to try to make it possible in some way.
Eventually, delaying new kernel releases for w few weeks is a good idea from a users perspective (since some evil extensions people including me rely on may need to catch up..). IMHO, this limitation really hurts in transitions with a huge impact, eg. Python 3.7 to 3.8 or some such. Thanks for your valuable contributions, Michal. They are a real pleasure to read. Wishing you and the illustrious audience all the best for 2020, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org