On Fri, 22 Jun 2012 11:14:56 -0700
Adam Williamson wrote:
> One area that may be more interesting, I guess, would be to look at
> various timing issues. One key one would be 'how long it takes for
> bugs to be a) nominated and b) accepted as blockers, after they are
> reported'. I've come across
On Fri, Jun 22, 2012 at 11:14:56 -0700,
Adam Williamson wrote:
The most obvious area, perhaps, would be to look at the components
against which the most blockers are filed. That's so easy to do it may
be worth doing anyway, but I suspect the result will be quite
predictable and something we'r
Look at the time difference between blocker status (first bugzilla'd,
nominated for blocker, and/or confirmed) and the package revision
(culprit created, then fixed.) There might be some relationship
between problem packages and frequency of releases.
--
--
test mailing list
test@lists.fedorapr
One of the items on the Fedora 17 QA retrospective -
https://fedoraproject.org/wiki/Fedora_17_QA_Retrospective - is a
suggestion from Bruno that we could perhaps gain some useful insights by
analyzing the (by now considerable) corpus of blocker bugs from previous
releases, as a way perhaps to ident
