On 4/21/05, Marius Andreiana <malists(a)epon.ro> wrote:
How about unresolved bugs already filled?
lets see out 7 fc4t1 bugs listed at that url
2 are in assigned state and the red hat maintainers have commented
inside the bug and have expressed that this issue is being worked on.
1 is in needinfo state and the red hat maintainer has commented saying
this should be fixed in rawhide and is waiting for the reporter to
retest and confirm the fix
1 is in a reopen state where the maintainer has commented asking for
3 are in a new state, 1 has been commented on by the developer that
its fixed in cvs.
2 in the new state are kernel issues. The reporters of these test1
kernel problems should attempt to duplicate the issues with test2 and
report back. Lets face it.. the kernel gets a lot of bugreports thats
intimately hardware specific, affect hardware the fedora developer
might not have access to.. but upstream developers might be aware of
and working on.
I did a query on fc3 test 1-3 bugs, there are still 425 bugs:
Out of those 425.. how many are now in the modified state indicating
that a developer has worked on it and thinks the issue is fixed? how
many are in the need info state meaning the developer needs someone to
provide more information to make headway on the report?
how many are in the assigned state where the developer is working on
out of the remaining new or reopened.. how many of those are actually
requests for enhancements instead of a serious crasher or inoperable
Ignoring the bug reports doesn't motivate testers very much...
No one sane is going to suggest that there is enough skilled manpower
right now to follow up on each individual bugreport AND get things
actually fixed. But I don't think its fair to say that people are
actively ignoring bug reports. Let's talk numbers.
I get a total of 1602 bug against fc3t1-3
i get a total of 320 assigned/new/reopened against fc3t1-3
Those numbers don't tell me that developers are trying to ignore
anyone, those numbers tell me the system is overwhelmed.