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

Typo fixes

Browse source
This commit is contained in:
Ben Cotton 2021-07-08 09:50:17 -04:00
commit cbee901447
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
releases/modules/ROOT/pages/releases/branched.adoc
View file

@ -61,7 +61,7 @@ Therefore, it's usually not worth filing a bug for broken dependencies unless th
The Branched compose runs every day starting at 09:15UTC.
All branched package builds at that time that are marked as xref:quick-docs:repositories.adoc[_stable_] are included in the compose attempt.
If any release-blocking image fails to build as part of the compose, the compose is considered to have failed.
If the compose completes successfully, a set of automated tests intended to check its compliance with the https://fedoraproject.org/wiki/Basic_Release_Criteria[[Basic Release Criteria] are run.
If the compose completes successfully, a set of automated tests intended to check its compliance with the https://fedoraproject.org/wiki/Basic_Release_Criteria[Basic Release Criteria] are run.
If these tests pass, the compose will be synced out to the mirror system.
Note that during https://fedoraproject.org/wiki/Milestone_freezes[freezes] there will be many days where 0 packages are added to the compose.
The Branched tree is under the next release's number on the mirrors.
@ -116,7 +116,7 @@ This allows you to more easily narrow down when a problem or issue appeared. If
This allows you to test the boot up process and packages related to it, as well as newer kernels.
Read and understand the Dracut troubleshooting steps.
* Follow the https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org/[test] and https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org/[devel] lists for Branched issues.
Try to at least skim them before doing your daily Branched updates. Look for "[branched"' or "[F<N+1>]" subjects or reports of issues.
Try to at least skim them before doing your daily Branched updates. Look for "[branched]" or "[F<N+1>]" subjects or reports of issues.
Additionally if you find a problem and are not sure what to file bugs against you can open a discussion there.
* At some times, Branched kernels are made with a large amount of debugging enabled.
You can often gain a good deal of performance by passing `slub_debug=-` to your kernel boot line in `/etc/grub2.cfg`.