From Fedora Project Wiki

(...and this time, do it properly)
(make NoMoreAlphas changes (as proposed at https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/KIVWSHFKRS4RJEFTCAWZBKDCCETKPI4F/ ))
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
<noinclude>{{tempdoc}}</noinclude>
<noinclude>{{tempdoc}}</noinclude>
== Proposing {{{type|$TYPE}}} bugs ==
You can use the [https://qa.fedoraproject.org/blockerbugs/propose_bug Blocker Bugs web application] to propose a bug as a {{{type|$TYPE}}}. It will guide you through the process.
You can use the [https://qa.fedoraproject.org/blockerbugs/propose_bug Blocker Bugs web application] to propose a bug as a {{{type|$TYPE}}}. It will guide you through the process.


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


To propose a bug as a {{{type|$TYPE}}} for a release, mark it as blocking the ''tracker bug'' for {{{type|$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|$TYPE}}} ''tracker bugs'' follow a consistent naming scheme. For the next release, the Alpha tracker will always be called '''Alpha{{{typecamel|$TYPECAMEL}}}''', the Beta tracker will always be called '''Beta{{{typecamel|$TYPECAMEL}}}''', and the final release tracker will always be called '''Final{{{typecamel|$TYPECAMEL}}}'''. Rarely, you may need to propose a bug as a {{{type|$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. '''F{{FedoraVersionNumber|next2}}Alpha{{{typecamel|$TYPECAMEL}}}'''. So, to mark a bug as a {{{type|$TYPE}}} for the release of {{FedoraVersion|long|next}} Beta, you would set it to block the bug '''Beta{{{typecamel|$TYPECAMEL}}}'''. You can find a full list of tracker bugs at [[BugZappers/HouseKeeping/Trackers]].
To propose a bug as a {{{type|$TYPE}}} for a release, mark it as blocking the ''tracker bug'' for {{{type|$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|$TYPE}}} ''tracker bugs'' follow a consistent naming scheme. For the next release, the Beta tracker will always be called '''Beta{{{typecamel|$TYPECAMEL}}}''', and the final release tracker will always be called '''Final{{{typecamel|$TYPECAMEL}}}'''. Rarely, you may need to propose a bug as a {{{type|$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. '''F{{FedoraVersionNumber|next2}}Beta{{{typecamel|$TYPECAMEL}}}'''. So, to mark a bug as a {{{type|$TYPE}}} for the release of {{FedoraVersion|long|next}} Beta, you would set it to block the bug '''Beta{{{typecamel|$TYPECAMEL}}}'''. You can find a full list of tracker bugs at [[BugZappers/HouseKeeping/Trackers]].


{{admon/important|Must use [http://bugzilla.redhat.com Red Hat Bugzilla]|Only bugs reported against a Fedora component in [http://bugzilla.redhat.com Red Hat Bugzilla] can be marked as {{{type|$TYPE}}}s for a Fedora release. If the bug you wish to mark as a {{{type|$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.}}
{{admon/important|Must use [http://bugzilla.redhat.com Red Hat Bugzilla]|Only bugs reported against a Fedora component in [http://bugzilla.redhat.com Red Hat Bugzilla] can be marked as {{{type|$TYPE}}}s for a Fedora release. If the bug you wish to mark as a {{{type|$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.}}
<noinclude>[[Category:QA_Blocker_freeze_exception_templates]]</noinclude>
<noinclude>[[Category:QA_Blocker_freeze_exception_templates]]</noinclude>

Latest revision as of 00:23, 12 October 2017

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. F43Beta$TYPECAMEL. So, to mark a bug as a $TYPE for the release of Fedora 42 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.
Retrieved from "https://fedoraproject.org/w/index.php?title=Template:Blocker_freeze_exception_proposing&oldid=503314"