kparal added a new comment to an issue you are following:
``
It's standard to include them if they are well tested, well in advance, believed to be
safe, and do not threaten our schedule to be slipped (which is this case, if we want to
release this week, which might or might not work, we can't risk that the compose will
fail in any way). Some details are here:
https://fedoraproject.org/wiki/QA:SOP_compose_request
https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
You may also request that pending fixes for freeze exception bugs are
included in release candidate composes. Freeze exception bugs are those that do not block
the release, but which have been accepted as being of sufficient importance that fixes may
be allowed through the freeze: see the QA:SOP_freeze_exception_bug_process for further
details. During release freezes, release engineering may push freeze exception fixes to
the stable repository, but if a fix for a freeze exception issue is still pending stable
status, and you judge the issue to be of sufficient importance and the fix to be
sufficiently safe, you may list it for inclusion in the release candidate compose. Release
engineering may question this decision if they consider it risky. Err on the side of
caution when requesting inclusion of pending freeze exception fixes in release candidate
composes.
But I and @pschindl are just apprentices here, @adamwill usually handles this. We might be
doing it wrong, and Adam's on PTO right now. If you believe some FE should definitely
be included today, let's have a discussion about it. If we slip, I of course intend to
pull the safe FEs to stable.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7018