The kernel-4.13.3-300.fc27 kernel still has debugging enabled and it's the one currently in stable and used in the RC2 and RC3 composes. kernel-4.13.3-301.fc27 has debugging disabled again (and a few more minor fixes). If we do a RC4 or decide that debugging is not acceptable for Beta, we will need to pull this newer kernel in.
Proposed as a Freeze Exception for 27-beta by Fedora user kevin using the blocker tracking app because: Debugging builds make everything slower and will leave a poor impression for Beta. Additionally beta kernel builds break some 3rd party modules that depend on non debugging.
-1 FE as it does not violate any criteria and is consistent with https://fedoraproject.org/wiki/KernelDebugStrategy
Freeze Exceptions (by the process definitions) do not voliate critera, otherwise they would be blocker bugs. :) "In general, freeze exception bugs are usually bugs for which an update is not an optimal solution, and for which the fix is reasonably small and testable (this consideration becomes progressively more important as a release nears, so bugs may be downgraded from freeze exception status late in the release process if it transpires that the fix is complex and hard to test). " An update is not a solution here for all the media with the debug kernel. The fix is pretty small (there's 2 other small changes in with it, but otherwise it's pretty small). I fear we will get some bad press/user reaction to this... "Fedora 27 Beta is so slow"
+1 FE
(In reply to Kevin Fenzi from comment #3) > I fear we will get some bad press/user reaction to this... "Fedora 27 Beta > is so slow" Things got quite heated on devel-list, I expect user reaction will be greater. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/QENPO34KBEHPWE5FWONRG6GXVQYQNBFN/
(In reply to Dennis Gilmore from comment #2) > -1 FE as it does not violate any criteria and is consistent with > https://fedoraproject.org/wiki/KernelDebugStrategy So you care more about policy than user experience?, first impressions count.
At this point in the schedule (having already slipped twice), I don't like the inherent risk involved in switching out a tested kernel. If this were a blocking issue, I'd be less hesitant, but it's not. User first impressions do count, but the set of users that installs a Beta of an OS is very different (and generally more forgiving) than the set of users that installs a final release. I think we're fine with fast-tracking the non-debug kernel for 0-day updates. -1 FE.
I'm making this a rejected FE. But please note that if we slip yet another week, this will be definitely considered again.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.15.3-300.f27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.