Hi,
Kernel 5.3 was released upstream yesterday Sept 16. Fedora will be following the same rebase schedule as with past kernels. This means F30 will be rebased to 5.3 first followed by F29 shortly thereafter. We typically wait until the 2nd or 3rd stable release to push a rebase. Based on past timings, I'd expect this to happen around mid-October. You can find test builds in the kernel-stabilization COPR. Note that F31 will be shipping with 5.3 so you can always test those kernels too.
Please also keep an eye out for the 5.3 test day which will happen before the rebase as well.
Thanks, Laura
Hi,
Shouldn't we have kernel updates for F31 in updates-testing ?
On Mon, 2019-09-16 at 10:24 -0400, Laura Abbott wrote:
Hi,
Kernel 5.3 was released upstream yesterday Sept 16. Fedora will be following the same rebase schedule as with past kernels. This means F30 will be rebased to 5.3 first followed by F29 shortly thereafter. We typically wait until the 2nd or 3rd stable release to push a rebase. Based on past timings, I'd expect this to happen around mid-October. You can find test builds in the kernel- stabilization COPR. Note that F31 will be shipping with 5.3 so you can always test those kernels too.
Please also keep an eye out for the 5.3 test day which will happen before the rebase as well.
Thanks, Laura _______________________________________________ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
On 9/17/19 6:40 AM, Sérgio Basto wrote:
Hi,
Shouldn't we have kernel updates for F31 in updates-testing ?
Yes, I completely forgot to file them for the -rc updates. I did file for the final 5.3.0 and I'll be requesting that for stable (although I expect it won't go through until freeze is over)
On Mon, 2019-09-16 at 10:24 -0400, Laura Abbott wrote:
Hi,
Kernel 5.3 was released upstream yesterday Sept 16. Fedora will be following the same rebase schedule as with past kernels. This means F30 will be rebased to 5.3 first followed by F29 shortly thereafter. We typically wait until the 2nd or 3rd stable release to push a rebase. Based on past timings, I'd expect this to happen around mid-October. You can find test builds in the kernel- stabilization COPR. Note that F31 will be shipping with 5.3 so you can always test those kernels too.
Please also keep an eye out for the 5.3 test day which will happen before the rebase as well.
Thanks, Laura _______________________________________________ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Thanks
On Wed, 2019-09-18 at 09:58 -0400, Laura Abbott wrote:
On 9/17/19 6:40 AM, Sérgio Basto wrote:
Hi,
Shouldn't we have kernel updates for F31 in updates-testing ?
Yes, I completely forgot to file them for the -rc updates. I did file for the final 5.3.0 and I'll be requesting that for stable (although I expect it won't go through until freeze is over)
On Mon, 2019-09-16 at 10:24 -0400, Laura Abbott wrote:
Hi,
Kernel 5.3 was released upstream yesterday Sept 16. Fedora will be following the same rebase schedule as with past kernels. This means F30 will be rebased to 5.3 first followed by F29 shortly thereafter. We typically wait until the 2nd or 3rd stable release to push a rebase. Based on past timings, I'd expect this to happen around mid-October. You can find test builds in the kernel- stabilization COPR. Note that F31 will be shipping with 5.3 so you can always test those kernels too.
Please also keep an eye out for the 5.3 test day which will happen before the rebase as well.
Thanks, Laura _______________________________________________ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Laura Abbott schrieb am 16.09.19 um 16:24:
Kernel 5.3 was released upstream yesterday Sept 16. Fedora will be following the same rebase schedule as with past kernels. This means F30 will be rebased to 5.3 first followed by F29 shortly thereafter. We typically wait until the 2nd or 3rd stable release to push a rebase. Based on past timings, I'd expect this to happen around mid-October.
Would it be wise to tighten the "same rebase schedule as with past kernels" a little bit in the future (maybe by one week)?
Just wondering, as it seems the fast few transitions from one version line to the next iirc all finished some time after a line went EOL. This time it looks worse: 5.2 is EOL as of today and 5.3 hasn't even hit updates-testing for the current Fedora release yet afics. And the stabilization copr wasn't much in action this time either.
But whatever, I assume there are reasons why things are a little bit more bumpy this time, that not why I'm writing this mail. I was just wondering if a slightly faster schedule for the rebases might be a good idea in general.
CU, knurd
On 10/8/19 6:51 AM, Thorsten Leemhuis wrote:
Laura Abbott schrieb am 16.09.19 um 16:24:
Kernel 5.3 was released upstream yesterday Sept 16. Fedora will be following the same rebase schedule as with past kernels. This means F30 will be rebased to 5.3 first followed by F29 shortly thereafter. We typically wait until the 2nd or 3rd stable release to push a rebase. Based on past timings, I'd expect this to happen around mid-October.
Would it be wise to tighten the "same rebase schedule as with past kernels" a little bit in the future (maybe by one week)?
Just wondering, as it seems the fast few transitions from one version line to the next iirc all finished some time after a line went EOL. This time it looks worse: 5.2 is EOL as of today and 5.3 hasn't even hit updates-testing for the current Fedora release yet afics. And the stabilization copr wasn't much in action this time either.
But whatever, I assume there are reasons why things are a little bit more bumpy this time, that not why I'm writing this mail. I was just wondering if a slightly faster schedule for the rebases might be a good idea in general.
CU, knurd
The timing is kind of tricky because once we push a rebase we are stuck with it. That means if key CVEs come in we have to work to get them on the next kernel. It's also usually good to wait for the next merge window to close so any really obvious fixes have a chance to make it to a .1 or .2 stable kernels. We also wanted to wait for the kernel test week to complete, which happened last week. Based on all that's, that's how we got to the date today. We might be able to push a few of these things next time but it's also very hard to tell since sometimes the early releases are mostly unusable.
As for the stabilization copr, part of that was my fault for not being diligent there since I was traveling the last two weeks. I did the initial test build to make sure my f30 rebase was okay (didn't miss any pieces) and then mostly left it alone since I figured it would be just as easy to run the f31 kernel which was already on 5.3.
I do appreciate the feedback.
Thanks, Laura
On Tue, Oct 8, 2019 at 5:51 AM Thorsten Leemhuis fedora@leemhuis.info wrote:
Laura Abbott schrieb am 16.09.19 um 16:24:
Kernel 5.3 was released upstream yesterday Sept 16. Fedora will be following the same rebase schedule as with past kernels. This means F30 will be rebased to 5.3 first followed by F29 shortly thereafter. We typically wait until the 2nd or 3rd stable release to push a rebase. Based on past timings, I'd expect this to happen around mid-October.
Would it be wise to tighten the "same rebase schedule as with past kernels" a little bit in the future (maybe by one week)?
Just wondering, as it seems the fast few transitions from one version line to the next iirc all finished some time after a line went EOL. This time it looks worse: 5.2 is EOL as of today and 5.3 hasn't even hit updates-testing for the current Fedora release yet afics. And the stabilization copr wasn't much in action this time either.
While the EOL thing isn't ideal, it isn't that unusual either. We can, and
often do backport security fixes and the like before they appear in stable, so just because upstream stable has marked something as EOL, this does not mean that we will not update for such things. Stabilization is typically not used when the rebase version is the release kernel for the next Fedora. The real focus of stabilization is to have somewhere to accumulate patches before the rebase, while rawhide moves on. As F31 is releasing on 5.3, that branch was that place.
But whatever, I assume there are reasons why things are a little bit more bumpy this time, that not why I'm writing this mail. I was just wondering if a slightly faster schedule for the rebases might be a good idea in general
We are actually moving at about the same speed as in the past, 5.4-rc2 came out Sunday, and 5.3.5 will be built for F30 on Tuesday. The upstream stable tree is moving quite a bit faster though, we have gone from 1 stable update a week, to much closer to 2. We are also much more likely to get a .1 before rc1 comes out. This means, while we used to rebase on a .2 or .3 stable, we are rebasing on .4 - .6. From a kernel quality standpoint for the rebase, I am comfortable with this schedule.
Justin
CU, knurd
kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
On Tue, Oct 8, 2019 at 4:51 AM Thorsten Leemhuis fedora@leemhuis.info wrote:
Laura Abbott schrieb am 16.09.19 um 16:24:
Kernel 5.3 was released upstream yesterday Sept 16. Fedora will be following the same rebase schedule as with past kernels. This means F30 will be rebased to 5.3 first followed by F29 shortly thereafter. We typically wait until the 2nd or 3rd stable release to push a rebase. Based on past timings, I'd expect this to happen around mid-October.
Would it be wise to tighten the "same rebase schedule as with past kernels" a little bit in the future (maybe by one week)?
Just wondering, as it seems the fast few transitions from one version line to the next iirc all finished some time after a line went EOL. This time it looks worse: 5.2 is EOL as of today and 5.3 hasn't even hit updates-testing for the current Fedora release yet afics. And the stabilization copr wasn't much in action this time either.
But whatever, I assume there are reasons why things are a little bit more bumpy this time, that not why I'm writing this mail. I was just wondering if a slightly faster schedule for the rebases might be a good idea in general.
I'll take the contrary position :-) I haven't dug into what happened over the weekend with upstream kernel development, but they went from 5.3.2 to 5.3.5 in just a few days. And then a ton of backport bug fix stuff landed over the weekend in all stable kernels, I saw things from July in the changelog, even for 5.3.
I play kernel roulette, currently running 5.4.0-0.rc2.git0.1.fc32.x86_64 on F31, so I've signed up for kernel churn. But most everyday Fedora users silently appreciate not having to bother with it. Anyone else can 'dnf install *rpm' any kernel they want, if they want to opt into their own rebase. It's not a problem to run F31 kernels on F30. I've been doing that for years, to the point I now wonder if it'd be possible to have my usual dnf update only ever install Rawhide kernels, while keeping everything else on the current release. Automatically. *shrug*
5.2.20 is building only a day after release, and I think it's completely reasonable for Fedora 29 users to use that for a couple weeks, baring some major discovery. Anyone still on F29 is more likely to get perturbed with either churn or regressions - quite a lot of Fedora users are using laptops, in contrast to upstream testing so it's decently likely laptop related regressions get discovered later than automated tests will reveal. Most people aren't that interested in discovering and reporting kernel bugs, they have other work to get done.
I don't know if it's useful to figure out a way to get x86 kernels into u-t faster? If it were split out somehow, maybe it'd show up 4-6 hours earlier? e.g. right now if you check the kernels building, the 5.3.5 fc31 meta package, or whatever it's called, isn't done because armv7 is still building. The rest are done and can be downloaded already from koji, but not through u-t. But yeah, not sure if this would be an effective use of resources.
kernel@lists.fedoraproject.org