Hi folks! So, we have this Alpha release criterion:
https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria#FESCo_blocke...
it was added back in 2013 - https://lists.fedoraproject.org/pipermail/test/2013-June/116531.html - to provide a documented process by which FESCo could designate bugs as blocking the release. Practically, FESCo has always been able to do this, but we didn't used to have a way of keeping track of it.
It occurs to me that there's really no reason for FESCo-designated blockers to go through the review process: there's really nothing to be discussed, if FESCo says "we designate this bug as a blocker", then it's a blocker. We don't need to propose and review it. So I suggest we should amend the Automatic Blockers policy:
https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Automatic_blockers
with this additional bullet:
* Bugs designated as release blockers by FESCo (see [[{{FedoraVersion| long|next}}_Alpha_Release_Criteria#FESCo_blocker_bugs]])
does this make sense to you all? Thanks!
On Thu, 10 Jul 2014 13:54:02 -0700 Adam Williamson adamwill@fedoraproject.org wrote:
Hi folks! So, we have this Alpha release criterion:
https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria#FESCo_blocke...
it was added back in 2013 - https://lists.fedoraproject.org/pipermail/test/2013-June/116531.html - to provide a documented process by which FESCo could designate bugs as blocking the release. Practically, FESCo has always been able to do this, but we didn't used to have a way of keeping track of it.
It occurs to me that there's really no reason for FESCo-designated blockers to go through the review process: there's really nothing to be discussed, if FESCo says "we designate this bug as a blocker", then it's a blocker. We don't need to propose and review it. So I suggest we should amend the Automatic Blockers policy:
https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Automatic_blockers
with this additional bullet:
- Bugs designated as release blockers by FESCo (see [[{{FedoraVersion|
long|next}}_Alpha_Release_Criteria#FESCo_blocker_bugs]])
does this make sense to you all? Thanks!
That makes sense to me. Plus, it saves us a few minutes during blocker meetings, which some days, we need :)
// Mike
On 07/10/2014 03:54 PM, Adam Williamson wrote:
Hi folks! So, we have this Alpha release criterion:
https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria#FESCo_blocke...
it was added back in 2013 - https://lists.fedoraproject.org/pipermail/test/2013-June/116531.html - to provide a documented process by which FESCo could designate bugs as blocking the release. Practically, FESCo has always been able to do this, but we didn't used to have a way of keeping track of it.
It occurs to me that there's really no reason for FESCo-designated blockers to go through the review process: there's really nothing to be discussed, if FESCo says "we designate this bug as a blocker", then it's a blocker. We don't need to propose and review it. So I suggest we should amend the Automatic Blockers policy:
https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Automatic_blockers
with this additional bullet:
- Bugs designated as release blockers by FESCo (see [[{{FedoraVersion|
long|next}}_Alpha_Release_Criteria#FESCo_blocker_bugs]])
does this make sense to you all? Thanks!
Makes sense. Make it so.
On Thu, 2014-07-10 at 23:53 -0500, Dan Mossor wrote:
On 07/10/2014 03:54 PM, Adam Williamson wrote:
Hi folks! So, we have this Alpha release criterion:
https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria#FESCo_blocke...
it was added back in 2013 - https://lists.fedoraproject.org/pipermail/test/2013-June/116531.html - to provide a documented process by which FESCo could designate bugs as blocking the release. Practically, FESCo has always been able to do this, but we didn't used to have a way of keeping track of it.
It occurs to me that there's really no reason for FESCo-designated blockers to go through the review process: there's really nothing to be discussed, if FESCo says "we designate this bug as a blocker", then it's a blocker. We don't need to propose and review it. So I suggest we should amend the Automatic Blockers policy:
https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Automatic_blockers
with this additional bullet:
- Bugs designated as release blockers by FESCo (see [[{{FedoraVersion|
long|next}}_Alpha_Release_Criteria#FESCo_blocker_bugs]])
does this make sense to you all? Thanks!
Makes sense. Make it so.
Done, thanks Dan etc. for the feedback. Kevin, can you pass on to FESCo that this change has been made, and if they decide to designate a bug as a release blocker, they can give it the 'AcceptedBlocker' whiteboard field immediately? Thanks.
On Fri, 11 Jul 2014 13:50:25 -0700 Adam Williamson adamwill@fedoraproject.org wrote:
On Thu, 2014-07-10 at 23:53 -0500, Dan Mossor wrote:
On 07/10/2014 03:54 PM, Adam Williamson wrote:
Hi folks! So, we have this Alpha release criterion:
https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria#FESCo_blocke...
it was added back in 2013 - https://lists.fedoraproject.org/pipermail/test/2013-June/116531.html
- to provide a documented process by which FESCo could designate
bugs as blocking the release. Practically, FESCo has always been able to do this, but we didn't used to have a way of keeping track of it.
It occurs to me that there's really no reason for FESCo-designated blockers to go through the review process: there's really nothing to be discussed, if FESCo says "we designate this bug as a blocker", then it's a blocker. We don't need to propose and review it. So I suggest we should amend the Automatic Blockers policy:
https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Automatic_blockers
with this additional bullet:
- Bugs designated as release blockers by FESCo (see
[[{{FedoraVersion| long|next}}_Alpha_Release_Criteria#FESCo_blocker_bugs]])
does this make sense to you all? Thanks!
Makes sense. Make it so.
Done, thanks Dan etc. for the feedback. Kevin, can you pass on to FESCo that this change has been made, and if they decide to designate a bug as a release blocker, they can give it the 'AcceptedBlocker' whiteboard field immediately? Thanks.
Done. Thanks.
kevin
-
Adam Williamson -
Dan Mossor -
Kevin Fenzi -
Mike Ruckman