== Goals

  * 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

  * Be willing to update often.

  * 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.

  If the above doesn't match you, you may wish to use regular stable Fedora releases.

  == Using Branched

  == Communicating

  === IRC

  === Mailing Lists

  === Bugzilla

  Branched bugs should be reported against the _Fedora_ product, and version that this branched will become and the affected component.

  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].

  == Producing Branched

  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.

  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].

  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.

  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.

  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.

  Package maintainers should read and follow the xref:fesco::Updates_Policy.adoc[Branched release updates policy] for building any packages in Branched.

  Not quite, though it has improved substantially in recent years.

  Still, see audience above.

  No.

  *How can I tell when the branched compose for the day has finished?*

  * 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).

  * 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.

  * Follow the https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org/[test] and https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org/[devel] lists for Branched issues.

  Try to at least skim them before doing your daily Branched updates. Look for "[branched]" or "[F<N+1>]" subjects or reports of issues.

  * 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`.

  * 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

  * https://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal[No Frozen Rawhide Proposal]

  * https://fedoraproject.org/wiki/No_Frozen_Rawhide_Implementation[No Frozen Rawhide Implementation]

  .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

  * 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}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}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}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}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}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}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}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}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}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}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}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}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}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}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}Changes[Changes]

  |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.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 |

  * 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}Changes[Changes]

  |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://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking])

  |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/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

  |===

  |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.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 |

  * 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}Changes[Changes]

  |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://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking])

  |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/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

  |===

  |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.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 |

  * 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}Changes[Changes]

  |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://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking])

  |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/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

  |===

  |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.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 |

  * 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}Changes[Changes]

  |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://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking])

  |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/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

  |===

  |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.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 |

  * 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}Changes[Changes]

  |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://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking])

  |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/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

  |===

  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]

  === Branched

  = 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.

  == Release Dates

  Our https://fedorapeople.org/groups/schedule/[release schedule] intentionally includes some "buffer" weeks, with early and later release targets.

  === Development Planning

  Fedora development planning is handled by the xref:program_management::changes_policy.adoc[Release Planning Process].

  === Development Process

  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.

  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.

  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).

  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.

  * 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''

  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.

  == 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.

  === Maintenance Schedule Rationale

  Fedora Linux is focused on free and open source software innovations and moves quickly.

  Historically, the Fedora Project has found that supporting two releases plus Rawhide and the pre-release Branched code to be a manageable work load.

  The tasks performed at EOL are documented in the https://docs.pagure.org/releng/sop_end_of_life.html[End of life SOP].

  === Fedora Linux 12 (Constantine)

  * 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.

  * 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://en.wikipedia.org/wiki/Cambridge%2C_Massachusetts

  === Fedora Linux 9 (Sulphur)

  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.

  == Goals

  * 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.

  == Audience

  * 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.

  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.

  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.

  == Discussing Rawhide

  === IRC

  === Bugzilla

  Rawhide bugs should be reported against the _Fedora_ product, _rawhide_ version and the affected component.

  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].

  == Producing Rawhide

  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.

  (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.

  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.

  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.

  == Questions and Answers

  *Doesn't rawhide eat babies / kill pets / burn down houses / break constantly?*

  No.

  *So Rawhide is very stable and we can all use it?*

  No. See audience above.

  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

  * 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.

  *I want to run the Rawhide kernel on my stable Fedora machine. Can I do that?*

  *How can I tell when the Rawhide compose for the day has finished?*

  *What happens during branching, does it affect my Rawhide release somehow?*

  *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).

  *Are rawhide packages signed?*

  ** `dnf history`

  ** `dnf update --skip-broken`

  ** `koji download-build`

  ** `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.

  * 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.

  * 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.

  * 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.

  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.

  == History

  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.

  == Adopting a Spin

  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.

  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.

  == Making changes

  The contents and configuration of Spins come from kickstart files in the https://pagure.io/fedora-kickstarts/[fedora-kickstarts] repo.

  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