On Fri, 2003-03-07 at 08:15, Frederic Crozat wrote: > On Fri, 07 Mar 2003 10:03:48 -0600, Bret Baptist wrote: > > > On Friday 07 March 2003 9:51 am, Warly wrote: > >> Bret Baptist <[EMAIL PROTECTED]> writes: > >> > It is a bit hard to confirm bugs if you only have 1 vote per component. > >> > I have tried to vote for a ton of bugs but can not because of the one > >> > vote limit. > >> > >> I first though that having only one person to confirm a bug will not be > >> enough, so I set the minimum number of vote to confirm a bug to 2, but it > >> may be more intelligent to lower it to 1. > > > > Well it is not a problem requiring 2 votes per bug to confirm it. It is the > > fact that if I want to vote for 2 bugs that are in the Installation component > > I can't. So if I am doing my bug hunting, find 2 bugs in the installation, > > search in bugzilla and find that other people have already discovered these > > bugs, I can only confirm one of them. The other bug I can't vote for. This > > seems counterintuitive to me. > > I think the BIG problem with UNCONFIRMED bug is their test case scenario : > > If you check all the bugs I replied to this week, more than 500f reply > are : give me reproducible facts, give me testcase, etc... And when I > think bug are fixed, I ask people to test and I get no answer in 250f > case.. > > This is really an area where YOU (cooker community) can help.. If I can't > reproduce crash/bugs, I can't fix them..
Frederic You're right... and I'd like to propose an idea on how this could be made better for you and the community. If Warly and others at MDK (or from the community) would look at the bug reporting page at mozilla you'll see a number of required fields there, such as ones related to reproducibility, installed OS (9.1rc1 cooker current 9.1rc2 etc) What you did to get the bug, what did you expect. suggested solution etc. Nobody in the world had a worse situation than Mozilla did around 0.6, Now although it's not perfect their system seems to work really well (most of the time if I do a bug report there I get an e-mail back within 24 hours.... compared to 2 weeks pre 0.6) it will make a submit a more lengthy process (by a minute or two) but I think you'll get more of what you need. Second... I guess I need to submit a patch to the "howto" Greg is assembling on this very point ... (and make better use of this myself *grin*) James
