From Fedora Project Wiki

Template documentation [edit]
This documentation is transcluded from Template:Blocker freeze exception proposing/doc. It will not be transcluded on pages that use this template.

This template is used to share very similar content between the QA:SOP_blocker_bug_process and the QA:SOP_freeze_exception_bug_process, for efficiency and consistency.

Proposing $TYPE bugs

You can use the Blocker Bugs web application to propose a bug as a $TYPE. It will guide you through the process.

Manual process

If you have an issue with the guided process or want to propose a $TYPE directly from Bugzilla for efficiency, you can use the manual process.

To propose a bug as a $TYPE for a release, mark it as blocking the tracker bug for $TYPE bugs in that release. To do this, enter the alias or bug ID of the tracker bug into the Blocks: field in Bugzilla. The aliases for the $TYPE tracker bugs follow a consistent naming scheme. For the next release, the Beta tracker will always be called Beta$TYPECAMEL, and the final release tracker will always be called Final$TYPECAMEL. Rarely, you may need to propose a bug as a $TYPE for the next release but one - in this case, prepend FXX (where XX is the release number) to the name of the alias, e.g. F31Beta$TYPECAMEL. So, to mark a bug as a $TYPE for the release of Fedora 30 Beta, you would set it to block the bug Beta$TYPECAMEL. You can find a full list of tracker bugs at BugZappers/HouseKeeping/Trackers.

Must use Red Hat Bugzilla
Only bugs reported against a Fedora component in Red Hat Bugzilla can be marked as $TYPEs for a Fedora release. If the bug you wish to mark as a $TYPE is being tracked in an upstream bug tracking system, you must file a corresponding bug in the Fedora bug tracking system before proposing it.