From 2776bf704550329dd05057634af6155ed3efd00b Mon Sep 17 00:00:00 2001 From: René Genz Date: Apr 21 2022 13:03:31 +0000 Subject: Various minor changes for releases - fix typos - add/fix links - delete surplus empty spaces --- diff --git a/releases/modules/ROOT/pages/branched.adoc b/releases/modules/ROOT/pages/branched.adoc index 1556dfa..d7333e6 100644 --- a/releases/modules/ROOT/pages/branched.adoc +++ b/releases/modules/ROOT/pages/branched.adoc @@ -7,40 +7,40 @@ Full nightly composes are also produced each night when a Branched release exist == Goals -Branched has the following goals: +Branched has the following goals: -* To allow package maintainers to integrate their packages into Fedora for a stable release. +* To allow package maintainers to integrate their packages into Fedora for a stable release. * To allow advanced users access to the newer packages than stable releases typically provide. * To identify and fix issues with packages before they reach a stable release of Fedora. == Audience -Branched is targeted at advanced users, testers and package maintainers. +Branched is targeted at advanced users, testers and package maintainers. -As a branched consumer, you should: +As a Branched consumer, you should: * Be willing to update often. -Branched doesn't get as many updates as rawhide (and at times they are frozen), but it still gets a larger amount than a Stable release. +Branched doesn't get as many updates as rawhide (and at times they are frozen), but it still gets a larger amount than a Stable release. * Be willing and able to troubleshoot problems. From time to time there are problems with Branched packages, and you will need strong troubleshooting skills and the ability to gather information for bug reports. You need a good understanding of dnf and how to downgrade packages, as well as boot-time troubleshooting. * Frequent reboots to test new kernel versions and confirm functionality of the boot process. If you can't reboot often, consider using a stable release instead. -* Be willing and able to report bugs as you find them and help maintainers gather information to fix them. +* Be willing and able to report bugs as you find them and help maintainers gather information to fix them. If the above doesn't match you, you may wish to use regular stable Fedora releases. == Using Branched -See the https://fedoraproject.org/wiki/Template:Rawhide_branched_install_methods[wiki template] for instructions on installing and using Rawhide. +See the https://fedoraproject.org/wiki/Template:Rawhide_branched_install_methods[wiki template] for instructions on installing and using Branched. == Communicating -There are a number of ways to communicate with other Branched users: +There are a number of ways to communicate with other Branched users: === IRC -Branched discussion is on topic and welcome in both the https://web.libera.chat/?channels=#fedora-devel[#fedora-devel] and https://web.libera.chat/?channels=#fedora-qa[#fedora-qa] IRC channels. +Branched discussion is on topic and welcome in both the https://web.libera.chat/?channels=#fedora-devel[#fedora-devel] and https://web.libera.chat/?channels=#fedora-qa[#fedora-qa] IRC channels. === Mailing Lists @@ -49,7 +49,7 @@ Branched discussion is on topic and welcome in both the https://lists.fedoraproj === Bugzilla Branched bugs should be reported against the _Fedora_ product, and version that this branched will become and the affected component. -Please do follow https://fedoraproject.org/wiki/Bugs_and_feature_requests[best practices] when filing. +Please do follow xref:quick-docs::howto-file-a-bug.adoc[best practices] when filing. Remember that IRC and mailing lists are useful to help narrow down if some behavior is a bug or where to report it, but are themselves not bug reporting channels. Always file bugs in https://bugzilla.redhat.com[Bugzilla]. @@ -58,7 +58,7 @@ Therefore, it's usually not worth filing a bug for broken dependencies unless th == Producing Branched -The Branched compose runs every day starting at 09:15UTC. +The Branched compose runs every day starting at 09:15 UTC. 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. @@ -66,19 +66,19 @@ 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. You can find a local mirror on the http://mirrors.fedoraproject.org/publiclist/Fedora/[public mirror list]. -Compose time varies depending on number of changes but is typically between 5 and 8 hours. +Compose time varies depending on number of changes, but is typically between 5 and 8 hours. Branched is subject to various policies during its life cycle. For most of its existence, it is subject to the xref:fesco::Updates_Policy.adoc[Updates Policy] and package updates for it are gated through the https://fedoraproject.org/wiki/Bodhi[Bodhi] package review process. -At various points of the xref:lifecycle.adoc[Fedora Release Life Cycle], other freezes, policies and requirements come into effect, including the https://fedoraproject.org/wiki/Software_String_Freeze_Policy[Software String Freeze Policy], the https://fedoraproject.org/wiki/Milestone_freezes[freezes], and the xref:program_management::chages_policy.adoc#change_process_milestones[Change freezes]. +At various points of the xref:lifecycle.adoc[Fedora Release Life Cycle], other freezes, policies and requirements come into effect, including the https://fedoraproject.org/wiki/Software_String_Freeze_Policy[Software String Freeze Policy], the https://fedoraproject.org/wiki/Milestone_freezes[freezes], and the xref:program_management::changes_policy.adoc#_change_process_milestones[Change freezes]. See all the above links for more details on exactly what changes may occur in the Branched tree under what conditions at what times. Composes are done using the 'mash' and https://pagure.io/pungi[Pungi] tools called from a script maintained by Fedora Release Engineering. -If the base set of packages needed to compose are broken, the daily compose may fail. +If the base set of packages needed to compose are broken, the daily compose may fail. A report for each Branched compose is sent to to 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. This report contains output from the https://pagure.io/compose-utils[compose-changelog] tool from the previous compose as well as a broken dependency report for packages with broken dependencies. -Additionally, private email is sent to maintainers with packages containing broken dependencies. +Additionally, private email is sent to maintainers with packages containing broken dependencies. Package maintainers should read and follow the xref:fesco::Updates_Policy.adoc[Branched release updates policy] for building any packages in Branched. @@ -91,15 +91,15 @@ To use Branched at these times, GPG signature checking in your package managemen Not quite, though it has improved substantially in recent years. Still, see audience above. -There are things that break from time to time, but if you are able to downgrade or troubleshoot such issues aren't too severe, however most users should stick to stable Fedora releases. +There are things that break from time to time, but if you are able to downgrade or troubleshoot, such issues aren't too severe, however most users should stick to stable Fedora releases. -*I'm using a stable Fedora release, but I want the newer package for foo thats only available in Branched. Can I just yum|dnf install it?* +*I'm using a stable Fedora release, but I want the newer package for foo that is only available in Branched. Can I just yum|dnf install it?* No. -Mixing releases like this is a very bad idea. Better options are: +Mixing releases like this is a very bad idea. Better options are: -* Obtain the src.rpm for the package you wish and try and mock rebuild it (which may or may not work depending on dependencies) -* Ask the Fedora maintainer in a bug report to update the stable version if permitted by policy. +* Obtain the src.rpm for the package you wish and try to `mock --rebuild` it (which may or may not work depending on dependencies). +* Ask the Fedora maintainer in a bug report to update the stable version if permitted by policy. *How can I tell when the branched compose for the day has finished?* @@ -111,23 +111,23 @@ You can also watch fedora-messaging for the messages that rawhide compose has fi * Your package management system can be of great help in diagnosing and working around issues you find. Do read up and understand: `dnf downgrade`, `dnf history`, `dnf upgrade`, and `koji download-build`. * You should update frequently (preferably every day). -This allows you to more easily narrow down when a problem or issue appeared. If you apply a week of Branched updates at once you have many more packages to examine to narrow down issues. +This allows you to more easily narrow down when a problem or issue appeared. If you apply a week of Branched updates at once, you have many more packages to examine to narrow down issues. * Reboot often (preferably whenever new kernels arrive). 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. +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]" 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. +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`. -Additionally, you can run kernels in the https://fedoraproject.org/wiki/RawhideKernelNodebug[Rawhide Kernel Nodebug] repo that have all debugging disabled. +Additionally, you can run kernels in the https://fedoraproject.org/wiki/RawhideKernelNodebug[Rawhide Kernel Nodebug] repo that have all debugging disabled. * If you are using a graphical desktop environment in your Branched install, you may wish to install several of them. This allows you to still login and troubleshoot when your primary desktop environment is not working for some reason. * Have rescue media handy of the current stable Fedora release for emergencies. == History -Branched was created as part of the "No frozen Rawhide" proposals: +Branched was created as part of the "No frozen Rawhide" proposals: * https://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal[No Frozen Rawhide Proposal] * https://fedoraproject.org/wiki/No_Frozen_Rawhide_Implementation[No Frozen Rawhide Implementation] diff --git a/releases/modules/ROOT/pages/eol.adoc b/releases/modules/ROOT/pages/eol.adoc index 45cd17d..c4171de 100644 --- a/releases/modules/ROOT/pages/eol.adoc +++ b/releases/modules/ROOT/pages/eol.adoc @@ -11,6 +11,7 @@ If you want to upgrade your old system, please check xref:quick-docs::upgrading. .EOL Releases |=== |Release|EOL since|Maintained for + |Fedora Linux 33|2021-11-30|399 days |Fedora Linux 32|2021-05-25|392 days |Fedora Linux 31|2020-11-24|392 days diff --git a/releases/modules/ROOT/pages/f19/index.adoc b/releases/modules/ROOT/pages/f19/index.adoc index 807ec1a..c93de26 100644 --- a/releases/modules/ROOT/pages/f19/index.adoc +++ b/releases/modules/ROOT/pages/f19/index.adoc @@ -17,4 +17,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f20/index.adoc b/releases/modules/ROOT/pages/f20/index.adoc index bdb6ebd..2899cd3 100644 --- a/releases/modules/ROOT/pages/f20/index.adoc +++ b/releases/modules/ROOT/pages/f20/index.adoc @@ -17,4 +17,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f21/index.adoc b/releases/modules/ROOT/pages/f21/index.adoc index 8dfb9ed..a35ef9f 100644 --- a/releases/modules/ROOT/pages/f21/index.adoc +++ b/releases/modules/ROOT/pages/f21/index.adoc @@ -17,4 +17,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f22/index.adoc b/releases/modules/ROOT/pages/f22/index.adoc index ca03091..18f70d6 100644 --- a/releases/modules/ROOT/pages/f22/index.adoc +++ b/releases/modules/ROOT/pages/f22/index.adoc @@ -17,4 +17,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f23/index.adoc b/releases/modules/ROOT/pages/f23/index.adoc index cb8b29f..dab4240 100644 --- a/releases/modules/ROOT/pages/f23/index.adoc +++ b/releases/modules/ROOT/pages/f23/index.adoc @@ -18,4 +18,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f24/index.adoc b/releases/modules/ROOT/pages/f24/index.adoc index d6a9e30..2ab6204 100644 --- a/releases/modules/ROOT/pages/f24/index.adoc +++ b/releases/modules/ROOT/pages/f24/index.adoc @@ -18,4 +18,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f25/index.adoc b/releases/modules/ROOT/pages/f25/index.adoc index 7577774..3eb84a8 100644 --- a/releases/modules/ROOT/pages/f25/index.adoc +++ b/releases/modules/ROOT/pages/f25/index.adoc @@ -18,4 +18,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f26/index.adoc b/releases/modules/ROOT/pages/f26/index.adoc index 7d2a1ea..96afbd3 100644 --- a/releases/modules/ROOT/pages/f26/index.adoc +++ b/releases/modules/ROOT/pages/f26/index.adoc @@ -18,4 +18,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f27/index.adoc b/releases/modules/ROOT/pages/f27/index.adoc index 16b24f3..e1749a3 100644 --- a/releases/modules/ROOT/pages/f27/index.adoc +++ b/releases/modules/ROOT/pages/f27/index.adoc @@ -18,4 +18,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f28/index.adoc b/releases/modules/ROOT/pages/f28/index.adoc index 377b757..8fb2a79 100644 --- a/releases/modules/ROOT/pages/f28/index.adoc +++ b/releases/modules/ROOT/pages/f28/index.adoc @@ -19,4 +19,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f29/index.adoc b/releases/modules/ROOT/pages/f29/index.adoc index 119d63f..55fa619 100644 --- a/releases/modules/ROOT/pages/f29/index.adoc +++ b/releases/modules/ROOT/pages/f29/index.adoc @@ -19,4 +19,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f30/index.adoc b/releases/modules/ROOT/pages/f30/index.adoc index b6a044d..634c66d 100644 --- a/releases/modules/ROOT/pages/f30/index.adoc +++ b/releases/modules/ROOT/pages/f30/index.adoc @@ -19,4 +19,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f31/index.adoc b/releases/modules/ROOT/pages/f31/index.adoc index 1a8847f..e6f7b02 100644 --- a/releases/modules/ROOT/pages/f31/index.adoc +++ b/releases/modules/ROOT/pages/f31/index.adoc @@ -19,4 +19,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f32/index.adoc b/releases/modules/ROOT/pages/f32/index.adoc index d168258..8c91b22 100644 --- a/releases/modules/ROOT/pages/f32/index.adoc +++ b/releases/modules/ROOT/pages/f32/index.adoc @@ -19,4 +19,4 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] diff --git a/releases/modules/ROOT/pages/f33/index.adoc b/releases/modules/ROOT/pages/f33/index.adoc index 6511ae1..e7841e8 100644 --- a/releases/modules/ROOT/pages/f33/index.adoc +++ b/releases/modules/ROOT/pages/f33/index.adoc @@ -19,5 +19,5 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}Changes[Changes] diff --git a/releases/modules/ROOT/pages/f34/blocking.adoc b/releases/modules/ROOT/pages/f34/blocking.adoc index 16ab181..06787e7 100644 --- a/releases/modules/ROOT/pages/f34/blocking.adoc +++ b/releases/modules/ROOT/pages/f34/blocking.adoc @@ -23,7 +23,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t |Image | optical boot is blocking | maximum size |Cloud/aarch64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.aarch64.qcow2 | no | -|Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.qcow2 | no | +|Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.qcow2 | no | |Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.raw.xz | no | |Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-_RELEASE_MILESTONE_.iso | yes | 700 MiB |IoT/aarch64/images/Fedora-IoT-_RELEASE_MILESTONE_.aarch64.raw.xz | no | diff --git a/releases/modules/ROOT/pages/f34/index.adoc b/releases/modules/ROOT/pages/f34/index.adoc index dbca955..1d4134d 100644 --- a/releases/modules/ROOT/pages/f34/index.adoc +++ b/releases/modules/ROOT/pages/f34/index.adoc @@ -19,5 +19,5 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}Changes[Changes] diff --git a/releases/modules/ROOT/pages/f34/spins.adoc b/releases/modules/ROOT/pages/f34/spins.adoc index 960a9af..c2b4f7e 100644 --- a/releases/modules/ROOT/pages/f34/spins.adoc +++ b/releases/modules/ROOT/pages/f34/spins.adoc @@ -17,16 +17,16 @@ file an issue against https://pagure.io/fedora-qa/relval/issues[relval]. |https://fedoraproject.org/wiki/Design_Suite[Design Suite] | The Fedora Design Suite includes well-selected applications, fitting a variety of use cases. Whether you decide to work on publishing documents, creating images and pictures or even 3D content, the Design Suite has a fitting tool. | 4 GB |https://fedoraproject.org/wiki/Fedora_jam[Fedora Jam] | Fedora Jam is a full-featured audio creation spin. It includes all the tools needed to help create the music you want, anything from classical to jazz to Heavy metal. Included in Fedora jam is full support for JACK and JACK to PulseAudio bridging. | 4 GiB |https://fedoraproject.org/wiki/Games_Spin[Games Spin] | The Fedora Games spin offers a perfect show-case of the best games available in Fedora. The included games span several genres, from first person shooters to real-time and turn based strategy games to puzzle games. Not all the games available in Fedora are included on this spin, but trying out this spin will give you a fair impression of Fedora's abilities to run great games. | 16 GiB -|https://docs.fedoraproject.org/en-US/i3/[i3 Spin] | An Fedora Spin shipping the popular i3 window manager. This Spin is the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment. | +|https://docs.fedoraproject.org/en-US/i3/[i3 Spin] | An Fedora Spin shipping the popular i3 window manager. This Spin is the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment. | |https://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking]) -|https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB +|https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight, but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB |https://fedoraproject.org/wiki/MATE-Compiz_Spin[MATE-Compiz Spin] | The Fedora MATE spin is meant to provide users with a classic, lightweight and traditional looking desktop. | 2 GB |https://fedoraproject.org/wiki/Changes/PythonClassroomLab[Python Classroom Lab] | The Fedora Python Classroom Lab makes it even easier for teachers and instructors to use Fedora in their classrooms or workshops. Ready to use operating system with important stuff pre-installed - either with GNOME or as a headless environment for Docker or Vagrant. | 2 GiB -|https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. | +|https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. | |https://fedoraproject.org/wiki/Robotics_Spin[Robotics Spin] | Create a spin that provides as many robotics related packages to the spin to maximize out-of-the-box usable hardware and software. Eventually provide out-of-the-box simulation environment for one or more scenarios. | 4 GiB |https://fedoraproject.org/wiki/Scientific_Spin[Fedora Scientific] | Fedora Scientific spin aims to create a Fedora desktop based spin which will have a generic toolset for Linux users whose profession/studies involve scientific research. To learn more, see the documentation. | 5 GiB |https://fedoraproject.org/wiki/Security_Spin[Security Spin] | The Fedora Security Spin provides a safe test environment to work on security auditing, forensics, system rescue and teaching security testing methodologies in universities and other organizations. The spin is maintained by a community of security testers and developers. It comes with the clean and fast LXDE Desktop Environment and a customized menu that provides all the instruments needed to follow a proper test path for security testing or to rescue a broken system. The Live image has been crafted to make it possible to install software while running, and if you are running it from a USB stick created with the Live Media Writer's overlay feature, you can install and update software and save your test results permanently. Additional information is available at the Security Spin home page and its wiki page. | 2 GB -|https://fedoraproject.org/wiki/Sugar_on_a_Stick[Sugar on a Stick Spin] | Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can starts any computer with the student's personalized Sugar environment. We would like to see Sugar's presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. | 700 MiB -|https://fedoraproject.org/wiki/Xfce_Spin[Xfce_Spin] | The Fedora Xfce spin showcases the Xfce desktop, which aims to be fast and lightweight, while still being visually appealing and user friendly. Xfce is a full fledged desktop using the freedesktop.org standard. | 2 GB -|https://fedoraproject.org/wiki/Changes/LXQt_Spin[LXQt Spin] | The Fedora LXQt spin is meant to be a lightweight but yet complete desktop based on LXQt. LXQt is a fast and stable desktop environment already usable on production desktops. It will not get in the user's way. It is focused on being a Classic Desktop with a modern Look & Feel. | 1.4 GiB +|https://fedoraproject.org/wiki/Sugar_on_a_Stick[Sugar on a Stick Spin] | Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can start any computer with the student's personalized Sugar environment. We would like to see Sugar's presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. | 700 MiB +|https://fedoraproject.org/wiki/Xfce_Spin[Xfce Spin] | The Fedora Xfce spin showcases the Xfce desktop, which aims to be fast and lightweight, while still being visually appealing and user friendly. Xfce is a full fledged desktop using the freedesktop.org standard. | 2 GB +|https://fedoraproject.org/wiki/Changes/LXQt_Spin[LXQt Spin] | The Fedora LXQt spin is meant to be a lightweight, but yet complete desktop based on LXQt. LXQt is a fast and stable desktop environment already usable on production desktops. It will not get in the user's way. It is focused on being a Classic Desktop with a modern Look & Feel. | 1.4 GiB |=== diff --git a/releases/modules/ROOT/pages/f35/blocking.adoc b/releases/modules/ROOT/pages/f35/blocking.adoc index 2d2b0a1..590b865 100644 --- a/releases/modules/ROOT/pages/f35/blocking.adoc +++ b/releases/modules/ROOT/pages/f35/blocking.adoc @@ -23,7 +23,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t |Image | optical boot is blocking | maximum size |Cloud/aarch64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.aarch64.qcow2 | no | -|Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.qcow2 | no | +|Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.qcow2 | no | |Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.raw.xz | no | |Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-_RELEASE_MILESTONE_.iso | yes | 700 MiB |IoT/aarch64/images/Fedora-IoT-_RELEASE_MILESTONE_.aarch64.raw.xz | no | diff --git a/releases/modules/ROOT/pages/f35/index.adoc b/releases/modules/ROOT/pages/f35/index.adoc index 2382091..10303bc 100644 --- a/releases/modules/ROOT/pages/f35/index.adoc +++ b/releases/modules/ROOT/pages/f35/index.adoc @@ -19,5 +19,5 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}Changes[Changes] diff --git a/releases/modules/ROOT/pages/f35/spins.adoc b/releases/modules/ROOT/pages/f35/spins.adoc index f7ac57b..944dd77 100644 --- a/releases/modules/ROOT/pages/f35/spins.adoc +++ b/releases/modules/ROOT/pages/f35/spins.adoc @@ -17,17 +17,17 @@ file an issue against https://pagure.io/fedora-qa/relval/issues[relval]. |https://fedoraproject.org/wiki/Design_Suite[Design Suite] | The Fedora Design Suite includes well-selected applications, fitting a variety of use cases. Whether you decide to work on publishing documents, creating images and pictures or even 3D content, the Design Suite has a fitting tool. | 4 GB |https://fedoraproject.org/wiki/Fedora_jam[Fedora Jam] | Fedora Jam is a full-featured audio creation spin. It includes all the tools needed to help create the music you want, anything from classical to jazz to Heavy metal. Included in Fedora jam is full support for JACK and JACK to PulseAudio bridging. | 4 GiB |https://fedoraproject.org/wiki/Games_Spin[Games Spin] | The Fedora Games spin offers a perfect show-case of the best games available in Fedora. The included games span several genres, from first person shooters to real-time and turn based strategy games to puzzle games. Not all the games available in Fedora are included on this spin, but trying out this spin will give you a fair impression of Fedora's abilities to run great games. | 16 GiB -|https://docs.fedoraproject.org/en-US/i3/[i3 Spin] | An Fedora Spin shipping the popular i3 window manager. This Spin is the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment. | +|https://docs.fedoraproject.org/en-US/i3/[i3 Spin] | An Fedora Spin shipping the popular i3 window manager. This Spin is the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment. | |https://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking]) -|https://kinoite.fedoraproject.org/[Kinoite] | An rpm-ostree-based KDE Plasma dekstop | -|https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB +|https://kinoite.fedoraproject.org/[Kinoite] | An rpm-ostree-based KDE Plasma desktop | +|https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight, but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB |https://fedoraproject.org/wiki/MATE-Compiz_Spin[MATE-Compiz Spin] | The Fedora MATE spin is meant to provide users with a classic, lightweight and traditional looking desktop. | 2 GB |https://fedoraproject.org/wiki/Changes/PythonClassroomLab[Python Classroom Lab] | The Fedora Python Classroom Lab makes it even easier for teachers and instructors to use Fedora in their classrooms or workshops. Ready to use operating system with important stuff pre-installed - either with GNOME or as a headless environment for Docker or Vagrant. | 2 GiB -|https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. | +|https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. | |https://fedoraproject.org/wiki/Robotics_Spin[Robotics Spin] | Create a spin that provides as many robotics related packages to the spin to maximize out-of-the-box usable hardware and software. Eventually provide out-of-the-box simulation environment for one or more scenarios. | 4 GiB |https://fedoraproject.org/wiki/Scientific_Spin[Fedora Scientific] | Fedora Scientific spin aims to create a Fedora desktop based spin which will have a generic toolset for Linux users whose profession/studies involve scientific research. To learn more, see the documentation. | 5 GiB |https://fedoraproject.org/wiki/Security_Spin[Security Spin] | The Fedora Security Spin provides a safe test environment to work on security auditing, forensics, system rescue and teaching security testing methodologies in universities and other organizations. The spin is maintained by a community of security testers and developers. It comes with the clean and fast LXDE Desktop Environment and a customized menu that provides all the instruments needed to follow a proper test path for security testing or to rescue a broken system. The Live image has been crafted to make it possible to install software while running, and if you are running it from a USB stick created with the Live Media Writer's overlay feature, you can install and update software and save your test results permanently. Additional information is available at the Security Spin home page and its wiki page. | 2 GB -|https://fedoraproject.org/wiki/Sugar_on_a_Stick[Sugar on a Stick Spin] | Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can starts any computer with the student's personalized Sugar environment. We would like to see Sugar's presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. | 700 MiB -|https://fedoraproject.org/wiki/Xfce_Spin[Xfce_Spin] | The Fedora Xfce spin showcases the Xfce desktop, which aims to be fast and lightweight, while still being visually appealing and user friendly. Xfce is a full fledged desktop using the freedesktop.org standard. | 2 GB -|https://fedoraproject.org/wiki/Changes/LXQt_Spin[LXQt Spin] | The Fedora LXQt spin is meant to be a lightweight but yet complete desktop based on LXQt. LXQt is a fast and stable desktop environment already usable on production desktops. It will not get in the user's way. It is focused on being a Classic Desktop with a modern Look & Feel. | 1.4 GiB +|https://fedoraproject.org/wiki/Sugar_on_a_Stick[Sugar on a Stick Spin] | Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can start any computer with the student's personalized Sugar environment. We would like to see Sugar's presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. | 700 MiB +|https://fedoraproject.org/wiki/Xfce_Spin[Xfce Spin] | The Fedora Xfce spin showcases the Xfce desktop, which aims to be fast and lightweight, while still being visually appealing and user friendly. Xfce is a full fledged desktop using the freedesktop.org standard. | 2 GB +|https://fedoraproject.org/wiki/Changes/LXQt_Spin[LXQt Spin] | The Fedora LXQt spin is meant to be a lightweight, but yet complete desktop based on LXQt. LXQt is a fast and stable desktop environment already usable on production desktops. It will not get in the user's way. It is focused on being a Classic Desktop with a modern Look & Feel. | 1.4 GiB |=== diff --git a/releases/modules/ROOT/pages/f36/blocking.adoc b/releases/modules/ROOT/pages/f36/blocking.adoc index 5dbefb3..69722b1 100644 --- a/releases/modules/ROOT/pages/f36/blocking.adoc +++ b/releases/modules/ROOT/pages/f36/blocking.adoc @@ -23,7 +23,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t |Image | optical boot is blocking | maximum size |Cloud/aarch64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.aarch64.qcow2 | no | -|Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.qcow2 | no | +|Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.qcow2 | no | |Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.raw.xz | no | |Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-_RELEASE_MILESTONE_.iso | yes | 700 MiB |IoT/aarch64/images/Fedora-IoT-_RELEASE_MILESTONE_.aarch64.raw.xz | no | diff --git a/releases/modules/ROOT/pages/f36/index.adoc b/releases/modules/ROOT/pages/f36/index.adoc index 270e4ca..f391b80 100644 --- a/releases/modules/ROOT/pages/f36/index.adoc +++ b/releases/modules/ROOT/pages/f36/index.adoc @@ -19,5 +19,5 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}Changes[Changes] diff --git a/releases/modules/ROOT/pages/f36/spins.adoc b/releases/modules/ROOT/pages/f36/spins.adoc index caf4262..f2bca28 100644 --- a/releases/modules/ROOT/pages/f36/spins.adoc +++ b/releases/modules/ROOT/pages/f36/spins.adoc @@ -17,17 +17,17 @@ file an issue against https://pagure.io/fedora-qa/relval/issues[relval]. |https://fedoraproject.org/wiki/Design_Suite[Design Suite] | The Fedora Design Suite includes well-selected applications, fitting a variety of use cases. Whether you decide to work on publishing documents, creating images and pictures or even 3D content, the Design Suite has a fitting tool. | 4 GB |https://fedoraproject.org/wiki/Fedora_jam[Fedora Jam] | Fedora Jam is a full-featured audio creation spin. It includes all the tools needed to help create the music you want, anything from classical to jazz to Heavy metal. Included in Fedora jam is full support for JACK and JACK to PulseAudio bridging. | 4 GiB |https://fedoraproject.org/wiki/Games_Spin[Games Spin] | The Fedora Games spin offers a perfect show-case of the best games available in Fedora. The included games span several genres, from first person shooters to real-time and turn based strategy games to puzzle games. Not all the games available in Fedora are included on this spin, but trying out this spin will give you a fair impression of Fedora's abilities to run great games. | 16 GiB -|https://docs.fedoraproject.org/en-US/i3/[i3 Spin] | An Fedora Spin shipping the popular i3 window manager. This Spin is the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment. | +|https://docs.fedoraproject.org/en-US/i3/[i3 Spin] | An Fedora Spin shipping the popular i3 window manager. This Spin is the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment. | |https://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking]) -|https://kinoite.fedoraproject.org/[Kinoite] | An rpm-ostree-based KDE Plasma dekstop | -|https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB +|https://kinoite.fedoraproject.org/[Kinoite] | An rpm-ostree-based KDE Plasma desktop | +|https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight, but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB |https://fedoraproject.org/wiki/MATE-Compiz_Spin[MATE-Compiz Spin] | The Fedora MATE spin is meant to provide users with a classic, lightweight and traditional looking desktop. | 2 GB |https://fedoraproject.org/wiki/Changes/PythonClassroomLab[Python Classroom Lab] | The Fedora Python Classroom Lab makes it even easier for teachers and instructors to use Fedora in their classrooms or workshops. Ready to use operating system with important stuff pre-installed - either with GNOME or as a headless environment for Docker or Vagrant. | 2 GiB -|https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. | +|https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. | |https://fedoraproject.org/wiki/Robotics_Spin[Robotics Spin] | Create a spin that provides as many robotics related packages to the spin to maximize out-of-the-box usable hardware and software. Eventually provide out-of-the-box simulation environment for one or more scenarios. | 4 GiB |https://fedoraproject.org/wiki/Scientific_Spin[Fedora Scientific] | Fedora Scientific spin aims to create a Fedora desktop based spin which will have a generic toolset for Linux users whose profession/studies involve scientific research. To learn more, see the documentation. | 5 GiB |https://fedoraproject.org/wiki/Security_Spin[Security Spin] | The Fedora Security Spin provides a safe test environment to work on security auditing, forensics, system rescue and teaching security testing methodologies in universities and other organizations. The spin is maintained by a community of security testers and developers. It comes with the clean and fast LXDE Desktop Environment and a customized menu that provides all the instruments needed to follow a proper test path for security testing or to rescue a broken system. The Live image has been crafted to make it possible to install software while running, and if you are running it from a USB stick created with the Live Media Writer's overlay feature, you can install and update software and save your test results permanently. Additional information is available at the Security Spin home page and its wiki page. | 2 GB -|https://fedoraproject.org/wiki/Sugar_on_a_Stick[Sugar on a Stick Spin] | Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can starts any computer with the student's personalized Sugar environment. We would like to see Sugar's presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. | 700 MiB -|https://fedoraproject.org/wiki/Xfce_Spin[Xfce_Spin] | The Fedora Xfce spin showcases the Xfce desktop, which aims to be fast and lightweight, while still being visually appealing and user friendly. Xfce is a full fledged desktop using the freedesktop.org standard. | 2 GB -|https://fedoraproject.org/wiki/Changes/LXQt_Spin[LXQt Spin] | The Fedora LXQt spin is meant to be a lightweight but yet complete desktop based on LXQt. LXQt is a fast and stable desktop environment already usable on production desktops. It will not get in the user's way. It is focused on being a Classic Desktop with a modern Look & Feel. | 1.4 GiB +|https://fedoraproject.org/wiki/Sugar_on_a_Stick[Sugar on a Stick Spin] | Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can start any computer with the student's personalized Sugar environment. We would like to see Sugar's presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. | 700 MiB +|https://fedoraproject.org/wiki/Xfce_Spin[Xfce Spin] | The Fedora Xfce spin showcases the Xfce desktop, which aims to be fast and lightweight, while still being visually appealing and user friendly. Xfce is a full fledged desktop using the freedesktop.org standard. | 2 GB +|https://fedoraproject.org/wiki/Changes/LXQt_Spin[LXQt Spin] | The Fedora LXQt spin is meant to be a lightweight, but yet complete desktop based on LXQt. LXQt is a fast and stable desktop environment already usable on production desktops. It will not get in the user's way. It is focused on being a Classic Desktop with a modern Look & Feel. | 1.4 GiB |=== diff --git a/releases/modules/ROOT/pages/f37/blocking.adoc b/releases/modules/ROOT/pages/f37/blocking.adoc index d1dcb23..defbb89 100644 --- a/releases/modules/ROOT/pages/f37/blocking.adoc +++ b/releases/modules/ROOT/pages/f37/blocking.adoc @@ -23,7 +23,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t |Image | optical boot is blocking | maximum size |Cloud/aarch64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.aarch64.qcow2 | no | -|Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.qcow2 | no | +|Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.qcow2 | no | |Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.raw.xz | no | |Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-_RELEASE_MILESTONE_.iso | yes | 700 MiB |IoT/aarch64/images/Fedora-IoT-_RELEASE_MILESTONE_.aarch64.raw.xz | no | diff --git a/releases/modules/ROOT/pages/f37/index.adoc b/releases/modules/ROOT/pages/f37/index.adoc index 17e98a6..049d19c 100644 --- a/releases/modules/ROOT/pages/f37/index.adoc +++ b/releases/modules/ROOT/pages/f37/index.adoc @@ -19,5 +19,5 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}Changes[Changes] diff --git a/releases/modules/ROOT/pages/f37/spins.adoc b/releases/modules/ROOT/pages/f37/spins.adoc index 92987ea..857fad9 100644 --- a/releases/modules/ROOT/pages/f37/spins.adoc +++ b/releases/modules/ROOT/pages/f37/spins.adoc @@ -17,17 +17,17 @@ file an issue against https://pagure.io/fedora-qa/relval/issues[relval]. |https://fedoraproject.org/wiki/Design_Suite[Design Suite] | The Fedora Design Suite includes well-selected applications, fitting a variety of use cases. Whether you decide to work on publishing documents, creating images and pictures or even 3D content, the Design Suite has a fitting tool. | 4 GB |https://fedoraproject.org/wiki/Fedora_jam[Fedora Jam] | Fedora Jam is a full-featured audio creation spin. It includes all the tools needed to help create the music you want, anything from classical to jazz to Heavy metal. Included in Fedora jam is full support for JACK and JACK to PulseAudio bridging. | 4 GiB |https://fedoraproject.org/wiki/Games_Spin[Games Spin] | The Fedora Games spin offers a perfect show-case of the best games available in Fedora. The included games span several genres, from first person shooters to real-time and turn based strategy games to puzzle games. Not all the games available in Fedora are included on this spin, but trying out this spin will give you a fair impression of Fedora's abilities to run great games. | 16 GiB -|https://docs.fedoraproject.org/en-US/i3/[i3 Spin] | An Fedora Spin shipping the popular i3 window manager. This Spin is the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment. | +|https://docs.fedoraproject.org/en-US/i3/[i3 Spin] | An Fedora Spin shipping the popular i3 window manager. This Spin is the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment. | |https://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking]) -|https://kinoite.fedoraproject.org/[Kinoite] | An rpm-ostree-based KDE Plasma dekstop | -|https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB +|https://kinoite.fedoraproject.org/[Kinoite] | An rpm-ostree-based KDE Plasma desktop | +|https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight, but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB |https://fedoraproject.org/wiki/MATE-Compiz_Spin[MATE-Compiz Spin] | The Fedora MATE spin is meant to provide users with a classic, lightweight and traditional looking desktop. | 2 GB |https://fedoraproject.org/wiki/Changes/PythonClassroomLab[Python Classroom Lab] | The Fedora Python Classroom Lab makes it even easier for teachers and instructors to use Fedora in their classrooms or workshops. Ready to use operating system with important stuff pre-installed - either with GNOME or as a headless environment for Docker or Vagrant. | 2 GiB -|https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. | +|https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. | |https://fedoraproject.org/wiki/Robotics_Spin[Robotics Spin] | Create a spin that provides as many robotics related packages to the spin to maximize out-of-the-box usable hardware and software. Eventually provide out-of-the-box simulation environment for one or more scenarios. | 4 GiB |https://fedoraproject.org/wiki/Scientific_Spin[Fedora Scientific] | Fedora Scientific spin aims to create a Fedora desktop based spin which will have a generic toolset for Linux users whose profession/studies involve scientific research. To learn more, see the documentation. | 5 GiB |https://fedoraproject.org/wiki/Security_Spin[Security Spin] | The Fedora Security Spin provides a safe test environment to work on security auditing, forensics, system rescue and teaching security testing methodologies in universities and other organizations. The spin is maintained by a community of security testers and developers. It comes with the clean and fast LXDE Desktop Environment and a customized menu that provides all the instruments needed to follow a proper test path for security testing or to rescue a broken system. The Live image has been crafted to make it possible to install software while running, and if you are running it from a USB stick created with the Live Media Writer's overlay feature, you can install and update software and save your test results permanently. Additional information is available at the Security Spin home page and its wiki page. | 2 GB -|https://fedoraproject.org/wiki/Sugar_on_a_Stick[Sugar on a Stick Spin] | Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can starts any computer with the student's personalized Sugar environment. We would like to see Sugar's presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. | 700 MiB -|https://fedoraproject.org/wiki/Xfce_Spin[Xfce_Spin] | The Fedora Xfce spin showcases the Xfce desktop, which aims to be fast and lightweight, while still being visually appealing and user friendly. Xfce is a full fledged desktop using the freedesktop.org standard. | 2 GB -|https://fedoraproject.org/wiki/Changes/LXQt_Spin[LXQt Spin] | The Fedora LXQt spin is meant to be a lightweight but yet complete desktop based on LXQt. LXQt is a fast and stable desktop environment already usable on production desktops. It will not get in the user's way. It is focused on being a Classic Desktop with a modern Look & Feel. | 1.4 GiB +|https://fedoraproject.org/wiki/Sugar_on_a_Stick[Sugar on a Stick Spin] | Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can start any computer with the student's personalized Sugar environment. We would like to see Sugar's presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. | 700 MiB +|https://fedoraproject.org/wiki/Xfce_Spin[Xfce Spin] | The Fedora Xfce spin showcases the Xfce desktop, which aims to be fast and lightweight, while still being visually appealing and user friendly. Xfce is a full fledged desktop using the freedesktop.org standard. | 2 GB +|https://fedoraproject.org/wiki/Changes/LXQt_Spin[LXQt Spin] | The Fedora LXQt spin is meant to be a lightweight, but yet complete desktop based on LXQt. LXQt is a fast and stable desktop environment already usable on production desktops. It will not get in the user's way. It is focused on being a Classic Desktop with a modern Look & Feel. | 1.4 GiB |=== diff --git a/releases/modules/ROOT/pages/f38/blocking.adoc b/releases/modules/ROOT/pages/f38/blocking.adoc index 9a4c41b..6528413 100644 --- a/releases/modules/ROOT/pages/f38/blocking.adoc +++ b/releases/modules/ROOT/pages/f38/blocking.adoc @@ -23,7 +23,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t |Image | optical boot is blocking | maximum size |Cloud/aarch64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.aarch64.qcow2 | no | -|Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.qcow2 | no | +|Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.qcow2 | no | |Cloud/x86_64/images/Fedora-Cloud-Base-_RELEASE_MILESTONE_.x86_64.raw.xz | no | |Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-_RELEASE_MILESTONE_.iso | yes | 700 MiB |IoT/aarch64/images/Fedora-IoT-_RELEASE_MILESTONE_.aarch64.raw.xz | no | diff --git a/releases/modules/ROOT/pages/f38/index.adoc b/releases/modules/ROOT/pages/f38/index.adoc index 6a79b4a..af2534e 100644 --- a/releases/modules/ROOT/pages/f38/index.adoc +++ b/releases/modules/ROOT/pages/f38/index.adoc @@ -19,5 +19,5 @@ User documentation, when available, will be at https://docs.fedoraproject.org/en * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaBlocker[Beta Blockers] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}BetaFreezeException[Beta Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalBlocker[Final Blockers] -* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exeptions] +* https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}FinalFreezeException[Final Freeze Exceptions] * https://bugzilla.redhat.com/show_bug.cgi?id=F{release-version}Changes[Changes] diff --git a/releases/modules/ROOT/pages/f38/spins.adoc b/releases/modules/ROOT/pages/f38/spins.adoc index e42928e..98ffdd5 100644 --- a/releases/modules/ROOT/pages/f38/spins.adoc +++ b/releases/modules/ROOT/pages/f38/spins.adoc @@ -17,17 +17,17 @@ file an issue against https://pagure.io/fedora-qa/relval/issues[relval]. |https://fedoraproject.org/wiki/Design_Suite[Design Suite] | The Fedora Design Suite includes well-selected applications, fitting a variety of use cases. Whether you decide to work on publishing documents, creating images and pictures or even 3D content, the Design Suite has a fitting tool. | 4 GB |https://fedoraproject.org/wiki/Fedora_jam[Fedora Jam] | Fedora Jam is a full-featured audio creation spin. It includes all the tools needed to help create the music you want, anything from classical to jazz to Heavy metal. Included in Fedora jam is full support for JACK and JACK to PulseAudio bridging. | 4 GiB |https://fedoraproject.org/wiki/Games_Spin[Games Spin] | The Fedora Games spin offers a perfect show-case of the best games available in Fedora. The included games span several genres, from first person shooters to real-time and turn based strategy games to puzzle games. Not all the games available in Fedora are included on this spin, but trying out this spin will give you a fair impression of Fedora's abilities to run great games. | 16 GiB -|https://docs.fedoraproject.org/en-US/i3/[i3 Spin] | An Fedora Spin shipping the popular i3 window manager. This Spin is the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment. | +|https://docs.fedoraproject.org/en-US/i3/[i3 Spin] | An Fedora Spin shipping the popular i3 window manager. This Spin is the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment. | |https://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking]) -|https://kinoite.fedoraproject.org/[Kinoite] | An rpm-ostree-based KDE Plasma dekstop | -|https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB +|https://kinoite.fedoraproject.org/[Kinoite] | An rpm-ostree-based KDE Plasma desktop | +|https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight, but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB |https://fedoraproject.org/wiki/MATE-Compiz_Spin[MATE-Compiz Spin] | The Fedora MATE spin is meant to provide users with a classic, lightweight and traditional looking desktop. | 2 GB |https://fedoraproject.org/wiki/Changes/PythonClassroomLab[Python Classroom Lab] | The Fedora Python Classroom Lab makes it even easier for teachers and instructors to use Fedora in their classrooms or workshops. Ready to use operating system with important stuff pre-installed - either with GNOME or as a headless environment for Docker or Vagrant. | 2 GiB -|https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. | +|https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. | |https://fedoraproject.org/wiki/Robotics_Spin[Robotics Spin] | Create a spin that provides as many robotics related packages to the spin to maximize out-of-the-box usable hardware and software. Eventually provide out-of-the-box simulation environment for one or more scenarios. | 4 GiB |https://fedoraproject.org/wiki/Scientific_Spin[Fedora Scientific] | Fedora Scientific spin aims to create a Fedora desktop based spin which will have a generic toolset for Linux users whose profession/studies involve scientific research. To learn more, see the documentation. | 5 GiB |https://fedoraproject.org/wiki/Security_Spin[Security Spin] | The Fedora Security Spin provides a safe test environment to work on security auditing, forensics, system rescue and teaching security testing methodologies in universities and other organizations. The spin is maintained by a community of security testers and developers. It comes with the clean and fast LXDE Desktop Environment and a customized menu that provides all the instruments needed to follow a proper test path for security testing or to rescue a broken system. The Live image has been crafted to make it possible to install software while running, and if you are running it from a USB stick created with the Live Media Writer's overlay feature, you can install and update software and save your test results permanently. Additional information is available at the Security Spin home page and its wiki page. | 2 GB -|https://fedoraproject.org/wiki/Sugar_on_a_Stick[Sugar on a Stick Spin] | Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can starts any computer with the student's personalized Sugar environment. We would like to see Sugar's presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. | 700 MiB -|https://fedoraproject.org/wiki/Xfce_Spin[Xfce_Spin] | The Fedora Xfce spin showcases the Xfce desktop, which aims to be fast and lightweight, while still being visually appealing and user friendly. Xfce is a full fledged desktop using the freedesktop.org standard. | 2 GB -|https://fedoraproject.org/wiki/Changes/LXQt_Spin[LXQt Spin] | The Fedora LXQt spin is meant to be a lightweight but yet complete desktop based on LXQt. LXQt is a fast and stable desktop environment already usable on production desktops. It will not get in the user's way. It is focused on being a Classic Desktop with a modern Look & Feel. | 1.4 GiB +|https://fedoraproject.org/wiki/Sugar_on_a_Stick[Sugar on a Stick Spin] | Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can start any computer with the student's personalized Sugar environment. We would like to see Sugar's presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. | 700 MiB +|https://fedoraproject.org/wiki/Xfce_Spin[Xfce Spin] | The Fedora Xfce spin showcases the Xfce desktop, which aims to be fast and lightweight, while still being visually appealing and user friendly. Xfce is a full fledged desktop using the freedesktop.org standard. | 2 GB +|https://fedoraproject.org/wiki/Changes/LXQt_Spin[LXQt Spin] | The Fedora LXQt spin is meant to be a lightweight, but yet complete desktop based on LXQt. LXQt is a fast and stable desktop environment already usable on production desktops. It will not get in the user's way. It is focused on being a Classic Desktop with a modern Look & Feel. | 1.4 GiB |=== diff --git a/releases/modules/ROOT/pages/index.adoc b/releases/modules/ROOT/pages/index.adoc index 92a5c9a..b357392 100644 --- a/releases/modules/ROOT/pages/index.adoc +++ b/releases/modules/ROOT/pages/index.adoc @@ -28,7 +28,7 @@ There is no guarantee of stability. Rawhide is intended for initial testing of the very latest code under active development. * On mirrors: https://download.fedoraproject.org/pub/fedora/linux/development/rawhide[development/rawhide] -* Repository: xref:quick-docs::repositories.adoc#rawhide[rawhide (unstable)] +* Repository: xref:quick-docs::repositories.adoc#the-rawhide-repository[rawhide (unstable)] === Branched diff --git a/releases/modules/ROOT/pages/lifecycle.adoc b/releases/modules/ROOT/pages/lifecycle.adoc index 8309e5f..c9ecaf9 100644 --- a/releases/modules/ROOT/pages/lifecycle.adoc +++ b/releases/modules/ROOT/pages/lifecycle.adoc @@ -1,7 +1,7 @@ = Fedora Linux Release Life Cycle The Fedora Project releases a new version of Fedora Linux approximately every six months and provides updated packages (maintenance) to these releases for approximately 13 months. -This allows users to "skip a release" while still being able to always have a system that is still receiving updates. +This allows users to "skip a release" while still being able to always have a system that is still receiving updates. == Release Dates Our https://fedorapeople.org/groups/schedule/[release schedule] intentionally includes some "buffer" weeks, with early and later release targets. @@ -26,7 +26,7 @@ Beta and General Availability (final) releases happen at approximately 14:00 UTC === Development Planning Fedora development planning is handled by the xref:program_management::changes_policy.adoc[Release Planning Process]. -So-called ''Changes'' are proposed, initially reviewed, and monitored through the development process by the xref:fesco::index.adoc[Fedora Engineering Steering Committee] (FESCo) and xref:program_management::index.adoc#fedora_program_manager[Fedora Program Manager]. +So-called ''Changes'' are proposed, initially reviewed, and monitored through the development process by the xref:fesco::index.adoc[Fedora Engineering Steering Committee] (FESCo) and xref:program_management::index.adoc#_fedora_program_manager[Fedora Program Manager]. === Development Process @@ -38,8 +38,8 @@ At that point the Rawhide tree is moving towards the release ''after'' the new B TIP: This means that development of a Fedora release is considered to begin at the time its ''predecessor'' branches from Rawhide. For instance, development on Fedora Linux 31 began the day after Fedora Linux 30 branched from Rawhide and entered the stabilization process. -After the https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling[Bodhi activation point], the https://fedoraproject.org/wiki/Bodhi[Bodhi] system is permanently active on the Branched release (all the way until it goes end of life), and requirements for updates to be marked as ''stable'' are set out in the xref:fesco::Updates_Policy.adoc[Updates Policy]. -Packages must go through the xref:quick-docs::repositories.adoc#updates-testing[''updates-testing''] repository for the release before entering its xref:quick-docs:repositories.adoc[''stable''] repository, according to rules defined in the updates policy. +After the xref:fesco::Updates_Policy.adoc#updates-testing-activation[Bodhi activation point] , the https://fedoraproject.org/wiki/Bodhi[Bodhi] system is permanently active on the Branched release (all the way until it goes end of life), and requirements for updates to be marked as ''stable'' are set out in the xref:fesco::Updates_Policy.adoc[Updates Policy]. +Packages must go through the xref:quick-docs::repositories.adoc#the-updates-testing-repository[''updates-testing''] repository for the release before entering its xref:quick-docs::repositories.adoc#stable-is-not-a-repository[''stable''] repository, according to rules defined in the updates policy. These rules tighten gradually from Beta through to post-GA (Final), but the basic process does not change. For some time prior to a milestone (Beta, Final) release a https://fedoraproject.org/wiki/Milestone_freezes[freeze] is in effect which prevents packages moving from ''updates-testing'' to ''stable'' except in accordance with the https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process[blocker] and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process[freeze exception] bug policies. @@ -58,7 +58,7 @@ Fedora generally develops new releases over a six month period to provide a regu Changes to this standard must be approved by FESCo. A six month release schedule also follows the precedence of Red Hat Linux (precursor to Fedora). -Former Red Hat software engineer Havoc Pennington offers a http://article.gmane.org/gmane.linux.redhat.fedora.advisory-board/1475/[historical perspective]. +Former Red Hat software engineer Havoc Pennington offers a https://listman.redhat.com/archives/fedora-advisory-board/2006-December/002039.html[historical perspective]. GNOME started following a time based release based on the ideas and success of Red Hat Linux and other distributions following Fedora having adopted a similar release cycle. Several other major components have started following a time-based release schedule. While the exact release schedules vary between these components and other upstream projects, the interactions between these components and Fedora Linux makes a six month, time-based release schedule a good balance. @@ -73,13 +73,13 @@ If the Beta https://fedoraproject.org/wiki/Go_No_Go_Meeting[Go/No-Go_Meeting] re * Slip of the Beta to Target #1 adds a new ''Beta Target #2'' * Slip of the Beta past Target #N (where N >= 2) adds a new ''Beta Target #(N+1)'' and also adds a new ''Final Target #N'' -If the Final https://fedoraproject.org/wiki/Go_No_Go_Meeting[Go/No-Go_Meeting] results in a "No Go" determination, that milestone and subsequent milestones will be pushed back by one week. +If the Final https://fedoraproject.org/wiki/Go_No_Go_Meeting[Go/No-Go_Meeting] results in a "No Go" determination, that milestone and subsequent milestones will be pushed back by one week. One week is added to the schedule to maintain the practice of releasing on Tuesdays. Tuesdays are the designated release day because they are good days for news coverage and correspond to the established day we synchronize our content with the mirrors that carry our releases. Be aware of holidays and of possible PR conflicts with the new proposed final date. -Go/No Go meetings receive input from representatives of xref:fesco::index.adoc[FESCo], https://docs.pagure.org/releng/[Release Engineering], and https://fedoraproject.org/wiki/QA[Quality Assurance]. +Go/No-Go Meetings receive input from representatives of xref:fesco::index.adoc[FESCo], https://docs.pagure.org/releng/[Release Engineering], and https://fedoraproject.org/wiki/QA[Quality Assurance]. == Maintenance Schedule We say maintained for ''approximately 13 months'' because the supported period for releases is dependent on the date the release under development goes final. @@ -89,7 +89,7 @@ As a result, ''Release N'' is supported until four weeks after the release of '' === Maintenance Schedule Rationale Fedora Linux is focused on free and open source software innovations and moves quickly. -If you want a distribution that moves slower but has a longer lifecycle, CentOS Stream or Red Hat Enterprise Linux, which are downstream of Fedora might be more suitable for you. +If you want a distribution that moves slower, but has a longer lifecycle, CentOS Stream or Red Hat Enterprise Linux, which are downstream of Fedora might be more suitable for you. Historically, the Fedora Project has found that supporting two releases plus Rawhide and the pre-release Branched code to be a manageable work load. @@ -100,7 +100,4 @@ Branches for new packages in the SCM are not allowed for distribution N after th The tasks performed at EOL are documented in the https://docs.pagure.org/releng/sop_end_of_life.html[End of life SOP]. -// = Additional Release Schedule Information -// * Overview of xref:index.adoc[rReleases], including currently supported releases -// * [[End of life | Unsupported Releases]] -// * [[Releases/HistoricalSchedules | Historical Release Information]] +xref:eol.adoc[Information about EOL releases] is available. diff --git a/releases/modules/ROOT/pages/name_history.adoc b/releases/modules/ROOT/pages/name_history.adoc index a5df57d..78a70a7 100644 --- a/releases/modules/ROOT/pages/name_history.adoc +++ b/releases/modules/ROOT/pages/name_history.adoc @@ -59,23 +59,25 @@ It is part of the fun! === Fedora Linux 12 (Constantine) -* Constantine is the name of Township in St. Joseph County, Michigan in the United States, as well as a name of a bay in the United Kingdom. +* Constantine is the name of Township in St. Joseph County, Michigan in the United States, as well as a name of a bay in the United Kingdom. * http://en.wikipedia.org/wiki/Constantine,_Michigan * There are several other connections listed at http://en.wikipedia.org/wiki/Constantine === Fedora Linux 11 (Leonidas) * Leonidas was a ship in the United States Navy. -* http://www.history.navy.mil/photos/sh-usn/usnsh-l/ad7.htm +* https://web.archive.org/web/20040310113223/http://www.history.navy.mil/photos/sh-usn/usnsh-l/ad7.htm +* https://www.history.navy.mil/content/history/nhhc/research/histories/ship-histories/danfs/l/leonidas-ii.html * Leonidas is also the name of a king. * http://en.wikipedia.org/wiki/Leonidas_I === Fedora Linux 10 (Cambridge) * Cambridge is a city in the United States, as well as being original code name of Red Hat Linux 10 (before it became Fedora Core 1), and was the name of a ship in the United States Navy. -* http://www.history.navy.mil/photos/sh-usn/usnsh-c/cambridg.htm +* https://web.archive.org/web/20031006204348/http://www.history.navy.mil/photos/sh-usn/usnsh-c/cambridg.htm +* https://www.history.navy.mil/content/history/nhhc/research/histories/ship-histories/danfs/c/cambridge-i.html * http://en.wikipedia.org/wiki/Cambridge%2C_Massachusetts -* Voting results: http://jwboyer.fedorapeople.org/fedora10relname.txt.asc +* Voting results: https://web.archive.org/web/20080809205521/http://jwboyer.fedorapeople.org/fedora10relname.txt.asc === Fedora Linux 9 (Sulphur) diff --git a/releases/modules/ROOT/pages/rawhide.adoc b/releases/modules/ROOT/pages/rawhide.adoc index 660f98f..3a54a78 100644 --- a/releases/modules/ROOT/pages/rawhide.adoc +++ b/releases/modules/ROOT/pages/rawhide.adoc @@ -4,13 +4,13 @@ It consists of a xref:quick-docs::repositories.adoc[package repository] called "rawhide" and contains the latest build of all Fedora Linux packages updated on a daily basis. Each day, the build system attempts to create a full set of deliverables (installation images and so on), and all that compose successfully are included in the Rawhide tree for that day. -Rawhide is sometimes called "development" or "main" (as it's the "main" branch in package git repositories). +Rawhide is sometimes called "development" or "main" (as it's the "main" branch in package git repositories). == Goals -Rawhide has the following Goals: +Rawhide has the following Goals: -* To allow package maintainers to integrate the newest _usable_ versions of their packages into Fedora. +* To allow package maintainers to integrate the newest _usable_ versions of their packages into Fedora. * To allow advanced users access to the newest _usable_ packages in a rolling manner. * To allow incremental changes to packages that are either too minor or major to go to stable Fedora releases. * To identify and fix issues with packages before they reach a stable release of Fedora. @@ -18,9 +18,9 @@ Rawhide has the following Goals: == Audience -Rawhide is targeted at advanced users, testers, and package maintainers. +Rawhide is targeted at advanced users, testers, and package maintainers. -As a Rawhide consumer, you should: +As a Rawhide consumer, you should: * Be willing to update on an almost daily basis. Rawhide gets hundreds of updates a day, and applying those updates on a regular basis allows you to more easily isolate when a bug appeared and what package(s) are responsible. @@ -31,7 +31,7 @@ You need a good understanding of dnf and how to downgrade packages, as well as b Rawhide packages stick closely to upstream projects, so interfaces and command-line options are subject to frequent changes. * Be willing to reboot frequently to test new kernel versions and confirm functionality of the boot process. If you can't reboot often, consider using a stable release instead. -* Be willing and able to report bugs to bugzilla as you find them and help maintainers gather information to fix them. +* Be willing and able to report bugs to Bugzilla as you find them and help maintainers gather information to fix them. If the above doesn't match you, you may wish to instead follow the xref:branched.adoc[Branched] release (depending on the point in the https://fedorapeople.org/groups/schedule/[release cycle]) or use regular stable Fedora releases. @@ -41,7 +41,7 @@ See the https://fedoraproject.org/wiki/Template:Rawhide_branched_install_methods == Discussing Rawhide -There are a number of ways to communicate with other Rawhide users: +There are a number of ways to communicate with other Rawhide users: === IRC @@ -54,7 +54,7 @@ Rawhide discussion is on topic and welcome in both the https://lists.fedoraproje === Bugzilla Rawhide bugs should be reported against the _Fedora_ product, _rawhide_ version and the affected component. -Please do follow https://fedoraproject.org/wiki/Bugs_and_feature_requests[best practices] when filing. +Please do follow xref:quick-docs::howto-file-a-bug.adoc[best practices] when filing. Remember that IRC and mailing lists are useful to help narrow down if some behavior is a bug or where to report it, but are themselves not bug reporting channels. Always file bugs in http://bugzilla.redhat.com[Bugzilla]. @@ -63,9 +63,9 @@ Therefore, it's usually not worth filing a bug for broken dependencies unless th == Producing Rawhide -Package owners must build for Rawhide using koji just like you would any other build; you do not go through the Bodhi process and the build becomes available almost immediately. +Package owners must build for Rawhide using Koji just like you would any other build; you do not go through the Bodhi process and the build becomes available almost immediately. -The Rawhide repository is composed every day starting at 05:15UTC. +The Rawhide repository is composed every day starting at 05:15 UTC. All rawhide builds in the buildsystem at that time are included in the compose attempt. The compose process also attempts to build all the standard Fedora 'deliverables' (live and install images, ARM and Cloud disk images, container images and so on). If any release-blocking image fails to build as part of the compose, the compose is considered to have failed. @@ -73,42 +73,42 @@ If the compose completes successfully, the compose will be 'synced out' to the m (A system where the sync only happens if a set of automated tests run on it passes is planned, but not yet fully implemented). Rawhide is under `development/rawhide` on the mirrors. -You can find a local "development" mirror on the http://mirrors.fedoraproject.org/publiclist/Fedora/development/[public mirror list]. Compose time varies depending on number of changes but is typically between 5 and 8 hours. +You can find a local "development" mirror on the http://mirrors.fedoraproject.org/publiclist/Fedora/development/[public mirror list]. Compose time varies depending on number of changes, but is typically between 5 and 8 hours. -Composes are done in a rawhide chroot using the 'pungi' tool called from https://pagure.io/pungi-fedora/blob/master/f/nightly.sh[a script maintained by Fedora Release engineering]. -If the base set of packages in Rawhide needed to compose Rawhide are broken, the daily compose may fail. +Composes are done in a rawhide chroot using the 'pungi' tool called from https://pagure.io/pungi-fedora/blob/main/f/nightly.sh[a script maintained by Fedora Release engineering]. +If the base set of packages in Rawhide needed to compose Rawhide are broken, the daily compose may fail. A report for each Rawhide compose is sent to to 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. This report contains output from the repodiff tool from the previous compose as well as a broken dependency report for packages with broken dependencies. -Additionally, private email is sent to maintainers with packages containing broken dependencies. +Additionally, private email is sent to maintainers with packages containing broken dependencies. -Package maintainers should read and follow the xref:fesco::Updates_Policy.adoc#rawhide[Rawhide updates policy] for building any packages in Rawhide. +Package maintainers should read and follow the xref:fesco::Updates_Policy.adoc#_rawhide[Rawhide updates policy] for building any packages in Rawhide. If needed and approved by xref:fesco::index.adoc[FESCo], mass rebuilds are done by Release Engineering in Rawhide a month or so before the next release branches from it. -Typically these are done for a global change over all packages such as a new gcc release, or rpm package format. +Typically these are done for a global change over all packages such as a new gcc release, or rpm package format. == Questions and Answers *Doesn't rawhide eat babies / kill pets / burn down houses / break constantly?* No. -Please stop telling everyone that. +Please stop telling everyone that. *So Rawhide is very stable and we can all use it?* No. See audience above. -There are things that break from time to time, but if you are able to downgrade or troubleshoot such issues aren't too severe. +There are things that break from time to time, but if you are able to downgrade or troubleshoot, such issues aren't too severe. Most users should still stick to stable Fedora releases, but Rawhide is a viable option for enthusiasts to experiment with. *I'm using a Stable Fedora release, but I want a newer package version that's only available in Rawhide. Can I just `dnf install` it?* No -Mixing releases like this is a bad idea. Better options are: +Mixing releases like this is a bad idea. Better options are: * Ask the Fedora maintainer in a bug report to update the stable version if permitted by policy. If not, there may be a http://copr.fedoraproject.org/[Copr repository] that provides the updated version. See the COPR page for more details. -* Obtain the src.rpm for the package you wish and try and to `rpmbuild --rebuild` it (which may or may not work depending on dependencies). +* Obtain the src.rpm for the package you wish and try to `rpmbuild --rebuild` it (which may or may not work depending on dependencies). *I want to run the Rawhide kernel on my stable Fedora machine. Can I do that?* @@ -123,7 +123,7 @@ It depends on how you define that, but yes. *How can I tell when the Rawhide compose for the day has finished?* -Check the for the reports sent to 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, or watch fedora-messaging for the `org.fedoraproject.prod.pungi.compose.status.change` topic. +Check the reports sent to 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, or watch fedora-messaging for the `org.fedoraproject.prod.pungi.compose.status.change` topic. *What happens during branching, does it affect my Rawhide release somehow?* @@ -152,7 +152,7 @@ In that case, you can try `--skip-broken` or removing the offending packages (if *As a package maintainer do I have to build rawhide packages or does the nightly compose take care of that?* You must build for Rawhide yourself (using Koji). -The nightly compose only collects packages already built and marked with the appropriate target (rawhide) in koji. +The nightly compose only collects packages already built and marked with the appropriate target (rawhide) in Koji. *Are rawhide packages signed?* @@ -166,22 +166,22 @@ Make sure you have gpgcheck=1 set in your repo file to take advantage of this. ** `dnf history` ** `dnf update --skip-broken` ** `koji download-build` -* If you are using a immutable variant like Silverblue, you should make good use of the features of OSTree like: +* If you are using an immutable variant like Silverblue, you should make good use of the features of OSTree like: ** `rpm-ostree rollback` ** `ostree admin config-diff` ** `ostree admin pin 0` * You should update frequently (preferably every day). This allows you to more easily narrow down when a problem or issue appeared. -If you apply a week of Rawhide updates at once you have many more packages to examine to narrow down issues. +If you apply a week of Rawhide updates at once, you have many more packages to examine to narrow down issues. * Reboot often (preferably whenever new kernels arrive). 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. +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 Rawhide issues. Try to at least skim them before doing your daily Rawhide updates. Look for '[rawhide]' 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. +Additionally, if you find a problem and are not sure what to file bugs against, you can open a discussion there. * Rawhide kernels are often built with varying degrees of debugging code enabled, which will result in worse performance and increased resource usage. See https://fedoraproject.org/wiki/KernelDebugStrategy[Kernel Debugging Strategy] for details on exactly what debugging code is enabled for which kernel builds. -You can disable SLUB debugging for those builds for which it is enabled by passing `slub_debug=-` to your kernel command line in `/etc/default/grub` (and re-generating your grub config, or just adding it directly). +You can disable SLUB debugging for those builds for which it is enabled by passing `slub_debug=-` to your kernel command line in `/etc/default/grub` (and re-generating your GRUB config, or just adding it directly). Additionally, you can run kernels in the https://fedoraproject.org/wiki/RawhideKernelNodebug[Rawhide Kernel Nodebug] repo that have all debugging disabled. * If you are using a graphical desktop environment in your Rawhide install, you may wish to install several of them. This allows you to still login and troubleshoot when your primary desktop environment is not working for some reason. @@ -189,9 +189,9 @@ This allows you to still login and troubleshoot when your primary desktop enviro == History -Red Hat Linux "Raw Hide" http://lwn.net/1998/0820/rawhide.html[announcement] +Red Hat Linux "Raw Hide" http://lwn.net/1998/0820/rawhide.html[announcement]. -The name might come from the http://en.wikipedia.org/wiki/Rawhide_%28song%29[song with the same name] that starts with "Rolling, rolling, rolling, ..." +The name might come from the http://en.wikipedia.org/wiki/Rawhide_%28song%29[song with the same name] that starts with "Rolling, rolling, rolling, ...". At one time, Rawhide would freeze before release milestones. This was changed with the https://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal[No Frozen Rawhide Proposal] and Branched process which we now follow. diff --git a/releases/modules/ROOT/pages/spins/creating.adoc b/releases/modules/ROOT/pages/spins/creating.adoc index 1a83782..6e1d977 100644 --- a/releases/modules/ROOT/pages/spins/creating.adoc +++ b/releases/modules/ROOT/pages/spins/creating.adoc @@ -54,7 +54,7 @@ The https://pagure.io/design[Design team repo] is your starting point for those == Adopting a Spin -If a Spin is abandoned and you want to take it over., it doesn't take much beyond raising your hand. +If a Spin is abandoned and you want to take it over, it doesn't take much beyond raising your hand. If the Program Manager has announced that the Spin is abandoned, just reply to their email. For a Spin that has been retired, first make sure there's a good use case for bringing it back. If there is, submit a Self-Contained xref:program_management::changes_policy.adoc[Change proposal] as if it were a new Spin. diff --git a/releases/modules/ROOT/pages/spins/index.adoc b/releases/modules/ROOT/pages/spins/index.adoc index 96cff77..4848be6 100644 --- a/releases/modules/ROOT/pages/spins/index.adoc +++ b/releases/modules/ROOT/pages/spins/index.adoc @@ -38,4 +38,4 @@ A customized spin can save you time and effort. Custom spins let you experience a select set of Fedora software, possibly in a particular way. For example, a desktop live CD could boot directly to a GNOME desktop, with 3D desktop effects enabled and selected backgrounds, colors and featured applications. -With further customization, a custom spin could boot directly to a movie player or launch a Web server is that ready to publish custom data. +With further customization, a custom spin could boot directly to a movie player or launch a Web server that is ready to publish custom data. diff --git a/releases/modules/ROOT/pages/spins/maintaining.adoc b/releases/modules/ROOT/pages/spins/maintaining.adoc index eab4d69..fce126a 100644 --- a/releases/modules/ROOT/pages/spins/maintaining.adoc +++ b/releases/modules/ROOT/pages/spins/maintaining.adoc @@ -3,7 +3,7 @@ == Making changes The contents and configuration of Spins come from kickstart files in the https://pagure.io/fedora-kickstarts/[fedora-kickstarts] repo. -To make changes, you can submit pull requests against the appropriate file. +To make changes, you can submit pull requests against the appropriate file. If you have a particularly meaningful change to make, you may want to file a xref:program_management::changes_policy.adoc[Change proposal] in order to communicate it to the wider community (and get it into the release notes). == Monitoring status