{% macro form_error(element) %} {% if element.errors %}
{% for error in element.errors %}

{{ error }}

{% endfor %}
{% endif %} {%- endmacro %} {% extends "base_nav.html" %} {% block jsheader %} {% endblock %} {% block info %}
{# Figure out a way to show this if partner-bugzilla is being used #}
{% endblock %} {% block body %}

Propose a Blocker or Freeze Exception

{{ bugform.csrf_token }}
Blocker Information
{{ bugform.bugid(class_="form-control") }} {{ form_error(bugform.bugid) }}
{{ bugform.bz_user(readonly=True, class_="form-control") }} {{ form_error(bugform.bz_user) }}

{{ bugform.milestone(class_="form-control") }} {{ form_error(bugform.milestone) }}

{{ bugform.blocker(class_="big-checkbox form-control") }} {{ form_error(bugform.blocker) }}

{{ bugform.freeze_exception(class_="big-checkbox form-control") }} {{ form_error(bugform.freeze_exception) }}
Details

A release blocking bug is a bug which is judged severe enough to justify blocking release until it is fixed. Blocker bugs generally violate a release criterion ( basic, beta, final) and follow the blocker SOP.

Freeze exception bugs are generally not possible to fix with an update after release but do not qualify as release blocking. Freeze exception bugs follow the freeze exception SOP.

Justification (Required)
{{ bugform.justification(rows=5, class_="form-control") }} {{ form_error(bugform.justification) }}

Proposing a bug as either blocker or freeze exception requires review by Fedora contributors. This process is much more straight forward when there is a clear reason why a bug has been proposed. If you are proposing a blocker, please cite a violated release criterion ( basic, beta, final) if possible.


{% endblock %}