Some QA testers then enable the repository on testing systems to try out the updates and provide feedback. The testers perform the job of making sure the updates are OK before they reach the general user population.
When it comes to a Branched pre-release, the expectation is that anyone who installs it wants to help test it: we effectively consider anyone running a Branched release to be a tester. The function of updates-testing is different in this case. There is not a 'general user population' of Branched users who run with updates-testing disabled, and are protected from problematic updates by the group of update testers.
Instead, updates-testing in Branched serves other important functions. The main purpose is to insulate image builds from potentially problematic changes. Branched images - nightly images, and the Alpha, Beta and GA Final milestone builds and their test compose and release candidate builds - are built from the stable packages, that is, only those in the fedora repository, not those in updates-testing. In this sense, updates-testing protects not a set of users, but a set of builds , from potentially destabilizing changes.
Especially when we are building an Alpha, Beta or GA release, we need to be able to reduce the amount of change in the package set between composes in order to produce an image of high quality.
The updates-testing mechanism allows for that: during Milestone freezes , new builds can be sent to updates-testing , but cannot move from there to stable fedora without special circumstances. In this way, we can work on release images while not preventing packagers from sending out builds. For this and other less important functions, we need as much feedback as possible, so it makes sense to have all pre-release testers have updates-testing enabled by default, and encourage them to provide feedback through Bodhi.
See a typo, something missing or out of date, or anything else which can be improved? Want to help? Learn how to contribute to Fedora Docs.
Edit this Page. The fedora repository The fedora repository exists for all Fedora releases after they have Branched from Rawhide. The fedora repository in stable releases For stable releases, fedora represents the frozen release state. The updates repository The updates repository exists for Branched and stable releases, but is only populated and used for stable releases. The updates-testing repository The updates-testing repository exists for Branched releases after the Bodhi enabling point , and for stable releases.
Other repositories There are other repositories that fulfil various niche purposes, which are documented here for the sake of providing a comprehensive reference. A repository can be any of the following:. This might take some time, depending upon the speed of your processor s and HD. The contents should be: filelists. The mirrors share a common structure for updates. When a release reaches the point where it is no longer supported when no updates are created for it, then it is considered End of Life EOL.
Want to help? Learn how to contribute to Fedora Docs. Edit this Page. Release Dates Our release schedule intentionally includes some "buffer" weeks, with early and later release targets. Development Process Fedora uses a system involving two 'development' trees. 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.
Schedule Methodology Fedora Linux release schedules repeat ad infinitum with "early target" dates of the third Tuesday in April and October. Development Schedule Rationale Fedora generally develops new releases over a six month period to provide a regular and predictable release schedule.
Schedule Contingency Planning If ''Mass rebuild'' is not completed on time, all the subsequent milestones starting with ''Branch point'' are pushed back for one week until the ''Mass rebuild'' is completed. 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. For comments or queries, please contact us. The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community maintained site. Red Hat is not responsible for content. This page was last edited on 12 November , at
0コメント