Going through Firebird's bugs

Posted July 26th, 2003, 1:40 am

Hi all,

We're starting to prepare for a drive to 1.0. Over the next week I'll be posting some development plans on my website, blakeross.com. To get to 1.0, we need to start getting our bug lists in order. I went through and triaged about 100 or our ~500 bugs tonight. Many of the bugs were worksforme. It would be really helpful if you guys could go through the ~350 remaining untriaged (Milestone: ----) Firebird bugs testing them and resolving them WORKSFORME if they are, indeed, fixed. Perhaps you could split it up amongst yourselves?

Thanks!

Blake

Posted July 26th, 2003, 1:51 am

Can you edit your post and include the bugzilla url that will produce the list or is it an obvious query?

Posted July 26th, 2003, 1:55 am

Sailfish wrote:Can you edit your post and include the bugzilla url that will produce the list or is it an obvious query?

Tried to edit it but the bugzilla link is way too long and doesn't wrap. Makes the page unreadable.

It's an easy query, just select Firebired as the product and ---- as the milestone.

Posted July 26th, 2003, 1:58 am

Blake, if they aren't WFM do you want us to set anything else? Milestone for example?

Also, if it's reported that a bug has been fixed via patches to other bugs, are we allowed to close it or do we have to wait for someone higher up the food chain to notice it?

Posted July 26th, 2003, 1:59 am

Colin Ramsay wrote:Blake, if they aren't WFM do you want us to set anything else? Milestone for example?

Nope, thanks. You could just mark "Still seeing this bug in..." so others know not to bother testing.

Posted July 26th, 2003, 2:03 am

Righty-o. I edited my above post, probably about the time you were answering it so I'll just ask again - if patches to another bug are reported to have fixed another are we allowed to close the other?

Posted July 26th, 2003, 2:14 am

Colin Ramsay wrote:Righty-o. I edited my above post, probably about the time you were answering it so I'll just ask again - if patches to another bug are reported to have fixed another are we allowed to close the other?

Don't ever go on hearsay. Test the other bug to confirm that it's fixed, and if it is, then you can mark FIXED.

Posted July 26th, 2003, 2:18 am

Cool. I'll get started.

Posted July 26th, 2003, 2:29 am

Blake wrote:
Sailfish wrote:Can you edit your post and include the bugzilla url that will produce the list or is it an obvious query?

Tried to edit it but the bugzilla link is way too long and doesn't wrap. Makes the page unreadable.

It's an easy query, just select Firebired as the product and ---- as the milestone.

Using the above, I got 349 hits as of this post. If that seems correct then I look at some tomorrow, er, later today.

btw, enclosing a long url using the BBCode [ url=Some Monster URL]Some text[ /url], should work in the future.

fwiw...

Posted July 26th, 2003, 2:48 am

I'm confused again. That link gives a list of unresolved bugs which are assigned, which means they can only be marked WFM by the owner doesn't it?

Posted July 26th, 2003, 4:08 am

Colin Ramsay wrote:I'm confused again. That link gives a list of unresolved bugs which are assigned, which means they can only be marked WFM by the owner doesn't it?

No, if enough people say, that a bug is WFM, then it will be marked as such.

But generally it's better for unexperienced bug-testers and -triagers to just comment in the bug, that they can't reproduce the issue anymore and the let experienced people like Asa, noririty, Mike Connors, David P James, Erik Fornoff, Bill Mason and me mark the bug as resolved.

General rule:
If in doubt, write a comment.

Posted July 26th, 2003, 4:46 am

Ok, I have started going through and writing relevant comments - updating the situation if bugs haven't been active for a while, etc. One thing I have seen is a few bugs with patches waiting but not reviewed and checked in. In fact most of these seem to be from one person. How can I try and hurry those bugs to closure?

Posted July 26th, 2003, 5:51 am

Regarding my previous comment, I will make a list of bugs with patches waiting to be reviewed and either post it here or send it to Blake.

Posted July 26th, 2003, 6:06 am

Blake wrote:
Sailfish wrote:Can you edit your post and include the bugzilla url that will produce the list or is it an obvious query?

Tried to edit it but the bugzilla link is way too long and doesn't wrap. Makes the page unreadable.

It's an easy query, just select Firebired as the product and ---- as the milestone.

I just had an idea how to get round this problem. Use one of the short url sites to make a shorter link so that you can post the link up on the forums. One of the best ones is http://www.makeashorterlink.com/ . I haven't tested this out yet, but if someone could confirm it works with bugzilla then that would be cool.

[edit]Here's a simple one, of bugs reported today: http://makeashorterlink.com/?B2ED32565 [/edit]

Posted July 26th, 2003, 7:14 am

Riiiight, I have gone through 75 bugs from <a href="http://bugzilla.mozilla.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&product=Firebird&target_milestone=---&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">this query</a> and updated them as I saw fit. It probably makes sense for <b><i>following triagers to start at bug 75 (Support Midas in Mozilla Firebird) on the list</i></b> so we don't duplicate our efforts and then when we have finished going through them all, go back and add test cases, detail etc. if need be.

Within the first 75 bugs I found these with patches wait for review:

http://bugzilla.mozilla.org/show_bug.cgi?id=172517 - Per-toolbar button size/type settings
http://bugzilla.mozilla.org/show_bug.cgi?id=176675 - Dragging links to the URL bar doesn't work as expected
http://bugzilla.mozilla.org/show_bug.cgi?id=177719 - No defaults for #ifdefs in DTD files cause platforms not to come up
http://bugzilla.mozilla.org/show_bug.cgi?id=180156 - bookmark overflow chevron can overlap bookmark name text
http://bugzilla.mozilla.org/show_bug.cgi?id=180164 - Make menu position customizable.
http://bugzilla.mozilla.org/show_bug.cgi?id=182928 - Add confirmation for Set As Wallpaper
http://bugzilla.mozilla.org/show_bug.cgi?id=184802 - Sidebar close button has no tooltip
http://bugzilla.mozilla.org/show_bug.cgi?id=184805 - Close button in the tab bar has no tooltip
http://bugzilla.mozilla.org/show_bug.cgi?id=185382 - alt+enter for opening URL in new tab doesn't work on WinME
http://bugzilla.mozilla.org/show_bug.cgi?id=186413 - History sort order incorrect when left on last visited

And this one which might be three bugs in one:

http://bugzilla.mozilla.org/show_bug.cgi?id=181872 - see my last comment - mark dupes?

I've also marked some WFM's, added some testcases and screenshots as well as updating some bugs by commenting.

Continue my good work my minions!

Going through Firebird's bugs

Who is online