From Fedora Project Wiki

(create template for another shared section of the blocker/FE processes)
 
m (small tweak for new non-media blocker process (just say 'accepted' instead of 'Accepted$TYPE' as it's an easy change))
Line 2: Line 2:
== Automatic {{{type|$TYPE}}}s ==
== Automatic {{{type|$TYPE}}}s ==


Certain types of bugs are considered ''automatic {{{type|$TYPE}}}s''. These bugs can be marked as Accepted{{{typecamel|$TYPECAMEL}}} by any member of one of the stakeholder groups without formal review. A comment should accompany this change, explaining that it has been made under the ''automatic {{{type|$TYPE}}}'' policy and linking to this section of this page. If anyone believes that a bug has been incorrectly marked as Accepted{{{typecamel|$TYPECAMEL}}} in this way, they may propose that it be formally reviewed by appending a comment to the bug or by raising it during a {{{type|$TYPE}}} review meeting. '''Only''' the following types of bug are considered ''automatic {{{type|$TYPE}}}s''. {{#ifeq:{{PAGENAME}}|SOP freeze exception bug process||Note that
Certain types of bugs are considered ''automatic {{{type|$TYPE}}}s''. These bugs can be marked as accepted by any member of one of the stakeholder groups without formal review. A comment should accompany this change, explaining that it has been made under the ''automatic {{{type|$TYPE}}}'' policy and linking to this section of this page. If anyone believes that a bug has been incorrectly marked as Accepted{{{typecamel|$TYPECAMEL}}} in this way, they may propose that it be formally reviewed by appending a comment to the bug or by raising it during a {{{type|$TYPE}}} review meeting. '''Only''' the following types of bug are considered ''automatic {{{type|$TYPE}}}s''. {{#ifeq:{{PAGENAME}}|SOP freeze exception bug process||Note that
where an item on this list applies to {{{blocking|$BLOCKING}}} images, a corresponding issue in a non-{{{blocking|$BLOCKING}}} image would likely be an ''automatic freeze exception'', under the corresponding [[QA:SOP_freeze_exception_bug_process#Automatic_freeze_exceptions|policy]].}}
where an item on this list applies to {{{blocking|$BLOCKING}}} images, a corresponding issue in a non-{{{blocking|$BLOCKING}}} image would likely be an ''automatic freeze exception'', under the corresponding [[QA:SOP_freeze_exception_bug_process#Automatic_freeze_exceptions|policy]].}}



Revision as of 20:17, 11 December 2015

Template documentation [edit]

This documentation is transcluded from Template:Blocker freeze exception automatic/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.

Automatic $TYPEs

Certain types of bugs are considered automatic $TYPEs. These bugs can be marked as accepted by any member of one of the stakeholder groups without formal review. A comment should accompany this change, explaining that it has been made under the automatic $TYPE policy and linking to this section of this page. If anyone believes that a bug has been incorrectly marked as Accepted$TYPECAMEL in this way, they may propose that it be formally reviewed by appending a comment to the bug or by raising it during a $TYPE review meeting. Only the following types of bug are considered automatic $TYPEs. Note that where an item on this list applies to $BLOCKING images, a corresponding issue in a non-$BLOCKING image would likely be an automatic freeze exception, under the corresponding policy.

No other type of bug can be considered an automatic $TYPE under any circumstance. In particular, "I think it is obviously a $TYPE" is not a valid reason to use this procedure. If you believe another type of bug should be added to the list, please propose the change on the test@ mailing list.