#89: Improve tracking blocker review status
--------------------------+-------------------------------------------------
Reporter: jlaska | Owner: poelstra
Type: enhancement | Status: assigned
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Resolution: | Keywords: retrospective
--------------------------+-------------------------------------------------
Comment (by poelstra):
Replying to [comment:2 jlaska]:
> Replying to [comment:1 poelstra]:
> > 3) I have an inquiry into the bugzilla team to see if there is a way
to get an exception report of blocker bugs that have not transitioned
through the VERIFIED state.
>
> Any revelations here? I think we're still exposed in this area since
bodhi CLOSES bugs
> when the update ships (regardless of the bug state).
>
Thanks for the reminder. I didn't get a response to my first query so I'm
asking again.
> > 4) We added a one week blocker bug nagging period before the Alpha,
Beta, and Final change deadlines to the schedule. It seemed to work okay
for the Fedora 14 Alpha, but getting rapid maintainer response was
difficult.
>
> We've had a bit more distance from the release, any new ideas/thoughts
on the blocker process that we'll want to track for F-15?
I think we can consider this item along with #1 and #2 closed. Getting
timely maintainer response was still an impediment in Beta and Final
though we were able to mitigate it successfully enough (to release on
time) by reviewing the blocker list and nagging maintainers daily the
seven days before the RC compose. So, no, don't really have any other
ideas.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/89#comment:5>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
