From Fedora Project Wiki

(create template for another shared section of the blocker/FE processes)
 
(rename "target size" to "maximum size" per https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/ABIGYREPXUPSAMJH3YREQ2PJGXZB4GRF/)
(3 intermediate revisions by one other user not shown)
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]].}}


Line 10: Line 10:
* File conflicts between two packages on a {{{blocking|$BLOCKING}}} DVD-style (offline installer) image without an explicit Conflicts: tag (failures of [[QA:Testcase_Mediakit_FileConflicts]])
* File conflicts between two packages on a {{{blocking|$BLOCKING}}} DVD-style (offline installer) image without an explicit Conflicts: tag (failures of [[QA:Testcase_Mediakit_FileConflicts]])
* Complete failure of any {{{blocking|$BLOCKING}}} TC/RC image to boot at all under any circumstance - "DOA" image (conditional failure is not an automatic {{{type|$TYPE}}})
* Complete failure of any {{{blocking|$BLOCKING}}} TC/RC image to boot at all under any circumstance - "DOA" image (conditional failure is not an automatic {{{type|$TYPE}}})
* Any {{{blocking|$BLOCKING}}} Beta or Final TC/RC image exceeding its target size (failures of [[QA:Testcase_Mediakit_ISO_Size]])
* Any {{{blocking|$BLOCKING}}} Beta or Final TC/RC image exceeding its maximum size (failures of [[QA:Testcase_Mediakit_ISO_Size]])
{{#ifeq:{{PAGENAME}}|SOP freeze exception bug process||* Bugs designated as blockers by FESCo (see [[{{FedoraVersion|long|next}}_Alpha_Release_Criteria#FESCo_blocker_bugs]])}}
{{#ifeq:{{PAGENAME}}|SOP freeze exception bug process||* Bugs designated as blockers by FESCo (see [[{{FedoraVersion|long|next}}_Beta_Release_Criteria#FESCo_blocker_bugs]])}}


No other type of bug can be considered an ''automatic {{{type|$TYPE}}}'' under any circumstance. In particular, "I think it is obviously a {{{type|$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
No other type of bug can be considered an ''automatic {{{type|$TYPE}}}'' under any circumstance. In particular, "I think it is obviously a {{{type|$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
[https://lists.fedoraproject.org/mailman/listinfo/test test@ mailing list].
[https://lists.fedoraproject.org/mailman/listinfo/test test@ mailing list].
<noinclude>[[Category:QA_Blocker_freeze_exception_templates]]</noinclude>
<noinclude>[[Category:QA_Blocker_freeze_exception_templates]]</noinclude>

Revision as of 13:06, 16 September 2019

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.

  • Bugs which entirely prevent the composition of one or more of the $BLOCKING images required to be built for a currently-pending (pre-)release
  • Incorrect checksums present on any of the $BLOCKING TC/RC images (failures of QA:Testcase_Mediakit_ISO_Checksums)
  • Unresolved dependencies on a $BLOCKING DVD-style (offline installer) image (failures of QA:Testcase_Mediakit_Repoclosure)
  • File conflicts between two packages on a $BLOCKING DVD-style (offline installer) image without an explicit Conflicts: tag (failures of QA:Testcase_Mediakit_FileConflicts)
  • Complete failure of any $BLOCKING TC/RC image to boot at all under any circumstance - "DOA" image (conditional failure is not an automatic $TYPE)
  • Any $BLOCKING Beta or Final TC/RC image exceeding its maximum size (failures of QA:Testcase_Mediakit_ISO_Size)
  • Bugs designated as blockers by FESCo (see Fedora 41_Beta_Release_Criteria#FESCo_blocker_bugs)

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.

Retrieved from "https://fedoraproject.org/w/index.php?title=Template:Blocker_freeze_exception_automatic&oldid=552781"