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

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

+