From 872720655acedfc45feecc3d4e1e6b0c35634134 Mon Sep 17 00:00:00 2001 From: Ben Cotton Date: Mon, 16 Aug 2021 11:51:35 -0400 Subject: [PATCH] Add reasoning to why we exclude kernel bugs (via jforbes) --- modules/ROOT/pages/pgm_guide/release_process.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/modules/ROOT/pages/pgm_guide/release_process.adoc b/modules/ROOT/pages/pgm_guide/release_process.adoc index f6b4fdb..6c92f73 100644 --- a/modules/ROOT/pages/pgm_guide/release_process.adoc +++ b/modules/ROOT/pages/pgm_guide/release_process.adoc @@ -172,6 +172,11 @@ Execute it from a machine with stable power and networking. You should then change the FChanges bug and bugs that block it to the branched version. The reason to do this separately is to keep from branching Changes targeted to N+2, which seem to always exist by Branch Day. +NOTE: The reason we exclude kernel bugs is two-fold: +1. A number of reported kernel bugs are longer-term bits that need to be solved over time, or bugs which upstream has to eventually get to. +It has become the place to file these bugs, even if not against the rawhide kernel in specific so that they do not get auto closed in a year. +2. Rawhide kernels are most typically built as debug kernels only, and many bugs filed against them are not reproducible on branched non-debug kernels. + == Go/No-Go meeting Before each public release, FESCo, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the https://fedoraproject.org/wiki/Go_No_Go_Meeting[Go/No-Go Meeting].