From 10de9f9ae370d7bac189532bf987509fd9951443 Mon Sep 17 00:00:00 2001 From: Aleksandra Fedorova Date: Mar 23 2020 12:59:45 +0000 Subject: Add links to Rawhide Gating --- diff --git a/fesco/modules/ROOT/pages/Updates_Policy.adoc b/fesco/modules/ROOT/pages/Updates_Policy.adoc index 9a2ce2c..dc8b5f7 100644 --- a/fesco/modules/ROOT/pages/Updates_Policy.adoc +++ b/fesco/modules/ROOT/pages/Updates_Policy.adoc @@ -16,14 +16,23 @@ Life Cycle] provides a more detailed overview of the development process. == Rawhide / devel / master -link:https://fedoraproject.org/wiki/Releases/Rawhide[Rawhide] is the always-rolling development tree. -Package updates built for rawhide are composed every day and pushed out to all rawhide consumers. -There are no "`updates`" or "`updates-testing`" Repositories for rawhide. The Bodhi updates system is -not used. New builds against this tree also are added to the build root (ie, other packages build -from them) daily (usually). +link:https://fedoraproject.org/wiki/Releases/Rawhide[Rawhide] is the always-rolling development tree. Package +updates built for rawhide are composed every day and pushed out to all rawhide consumers. New builds against +this tree also are added to the build root (ie, other packages build from them). repos available: link:https://fedoraproject.org/wiki/Repositories#rawhide[_rawhide_] +Since link:https://fedoraproject.org/wiki/Changes/GatingRawhidePackages[Rawhide Gating change] was introduced, +package updates in Fedora Rawhide need to pass verification before they land in the rawhide repositories. This +is implemented as a check for a Bodhi update, which verifies that the update satisfies the Gating policy. See +link:https://docs.fedoraproject.org/en-US/rawhide-gating/single-builds/[Rawhide Gating/single-builds] and +link:https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/[Rawhide Gating/multi-builds] for +details. + +Currently the default gating policy is empty, thus Fedora Rawhide update can pass the gate, no matter the test +results. Package maintainer can opt-in for the gating of a package, by setting up individual gating policies, +see link:https://docs.fedoraproject.org/en-US/rawhide-gating/optin/[Rawhide Gating/optin]. + For updates to rawhide packages, Maintainers SHOULD: * Try not to push a clearly broken build (breaks the default buildroot package set, etc)