operations/docs
operations/docs
3
1
Fork 9
Code Issues 4 Pull requests Activity Actions

Add reasoning to why we exclude kernel bugs (via jforbes)

Browse source
This commit is contained in:
Ben Cotton 2021-08-16 11:51:35 -04:00
commit 872720655a
1 changed files with 5 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
modules/ROOT/pages/pgm_guide/release_process.adoc
View file

@ -172,6 +172,11 @@ Execute it from a machine with stable power and networking.
You should then change the F<N+1>Changes 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].