SeaMonkey/Bug events/20111027

The SeaMonkey Community will hold a Bug event in the few days and night preceding Hallowe'en 2011. Witches and wizards, hold your wands and get ready to fight the evil Bugs and their offspring Maggots!

Where?

Channel #bugday on the Mozilla IRC server. How to go there will depend on your IRC server.

• First, connecting to the server
  • In ChatZilla, click "moznet" in the list of server names in the *client* tab (which can be opened by /client if you don't see it). In other IRC clients, establish a connection to irc.mozilla.org, either on port 6667 (default) without SSL, or on port 6697 with SSL.
• Second, join the channel
  • /join #bugday

When?

The Event will run continouously at the times shown below for various places all over the world (sorted by timezone: from the International Date Line, the Americas, West to East across Eurasia, then Oceania back to the International Date Line. Notice the "strange" ordering in Australia due to the fact that some provinces use DST and others don't. All these times include DST / summer time where applicable):

If your country or region is not shown in the above table, we hope that you will be able to deduce what time it will be on your clock, by comparison with neighbouring areas and/or by addition to or subtraction from UTC (Universal Time) which is shown in bold type near the first third of the table and/or to/from "Mozilla time" (USA Pacific DST, second line from top).

Before you start

• Make sure you have a Bugzilla account (and if you don't yet have one, get one here).
• Install the latest SeaMonkey nightly but not in the same directory as your usual "release" version of SeaMonkey. How to install it varies depending on your OS.
• Notes:
  • "Mac" builds are "Universal builds" supporting both 32- and 64-bit Mac computers with Intel processors running Mac OS X 10.5 or later. OS X 10.4 is not supported anymore, and neither are PowerPC computers.
  • There are separate "Linux" builds for 32-bit (i686) and 64-bit (x86_64) systems. 32-bit builds can run on 64-bit systems but not vice-versa. The 64-bit builds are still regarded as "experimental" because there are still few testers using them: a chicken-and-egg problem. If you have a 64-bit Linux system, maybe you can help us bytesting the x86_64 Linux build.
  • For Windows, only 32-bit builds are available at this time. They ought to run correctly on both 32- and 64-bit Windows computers.
  • A full list of hardware and software requirements for Windows, Linux and Mac can be found here.
• Start your new SeaMonkey as follows (at a command-line [shell] prompt, after cd to the directory containing the executable):

seamonkey -no-remote -ProfileManager

• • The first time, create a new profile then use it. Later on, you can just reuse that same profile.

What?

Finding, triageing and/or resolving bugs.

Helpful links

• In order to use the following searches, you need to be logged in to Bugzilla but you don't need any particular privileges.
  • All SeaMonkey UNCONFIRMED bugs
  • All open bugs for SeaMonkey::General
  • All bugs with [Halloween2011Bug] in the Whiteboard (see below)
  • Very old EXPIRED or UNCONFIRMED bugs (numbered < 100000) for MailNews & Sidebar
  • Ditto, but also some a little newer (numbered < 200000)

Moving bugs to other Products

Some bugs report under SeaMonkey actually don't belong there. The links below go to the "lists of components" for the Products most used for bugs coming from SeaMonkey:

• Calendar — The Mozilla Calendar project (more info) (For SeaMonkey, the Lightning and Provider for Google Calendar extensions)
• Core — Shared components used by Firefox and other Mozilla software, including handling of Web content (HTML, CSS, scripts, images, networking, etc.).
• MailNews Core — Mail and news components common to Thunderbird and SeaMonkey
• Mozilla Localizations — Translation, spelling and other errors in language packs and localized builds (more info)
• Other Applications — For bugs in CCK, Chatzilla, DOM Inspector, Venkman, and other applications which aren't large enough to warrant an entire Bugzilla product.
• SeaMonkey — This product covers SeaMonkey, the further developed code of the former Mozilla 1.x application suite, including web browser, e-mail and newsgroup client, and HTML composer. (more info)
• Tech Evangelism — For reporting web pages that need to be upgraded to support web standards and Gecko-based browsers (more info)
• Toolkit — The platform toolkit underlying Mozilla's "Aviary"-style applications (sic). This Product includes the add-on manager, the Firefox-style (not Jökulsárlón) download manager, the password manager, etc.

What do Resolutions mean?

Here are those you will probably use. (There are others.)

• DUPLICATE — This bug is a duplicate of some other bug, whose bug number must be mentioned.
• INCOMPLETE — The steps to reproduce are either nonexistent or too vague to allow reproducing the bug, and the reporter hasn't replied to requests for furter information.
• INVALID — This is either intended behaviour ("not a bug") or else it is a bug but not in Mozilla code ("not our bug")
• WORKSFORME — All attempts to reproduce the bug have failed; or the bug used tobe found in earlier versions but it has disappeared from other versions, and we don't know what fixed it.
• FIXED — The bug has been fixed in trunk code, and we know exactly which patch fixed it.
• WONTFIX — Only an Owner or Peer for the relevant Module may set this Resolution, see below.

• Also, the VERIFIED status means that someone other than whoever set RESOLVED has checked that the Resolution is correct. For FIXED bugs, this means in principle that someone (not necessarily the same person) has verified that in recent builds, the bug has disappeared from all three of Windows, Linux and Mac, or at least from those of the three where the bug had been seen before.

Using the Whiteboard

• Please mark all bugs handled during this Event by adding [Halloween2011Bug] to the Whiteboard. One of the entries below may be added in addition if it is not clear that the bug should be RESOLVED immediately.
  • DUPEME — you remember seeing a bug somewhere, of which this bug is a duplicate, but you can't find the other bug back.
  • [CLOSEME 2012-01-01 INCO] — bugs to be RESOLVED INCOMPLETE if the reporter doesn't answer.
  • [CLOSEME 2012-01-01 WFM] — bugs to be RESOLVED WORKSFORME unless someone can reproduce them (and say how, or at least say that is appears sporadically in such-and-such circumstances)
  • [CLOSEME INVA/WONT?] — bugs which might possibly be one of the following, but you aren't certain:
    • Intended behaviour (INVALID)
    • Not a Mozilla bug (INVALID)
    • Not worth fixing (WONTFIX)
      • Notes: 1. Only an owner or peer of the concerned product may set WONTFIX so you may want to bring such a bug to their attention. To find who they are, follow the following links for SeaMonkey in particular or for Mozilla code in general.
      • 2. Some developers have a "Bugzilla address of record" different from their listed email address. Make sure that you have JavaScript enabled (at least on bugzilla.mozilla.org), and use the Bugzilla autocomplete feature in the Cc field of the bug.

Results

Late start

The event didn't really gather speed until Saturday. What are the possible causes?

• SeaMonkey testers are volunteers, they don't do it on the job.
• The above Helpful links were completed quite late: the first link had a wrong URL (finding Zarro Boogs) until the middle of the night from Wednesday to Thursday, the last two were added on Saturday evening, about the time the event actually started (thanks Mnyromyr for sharing the searches).
• Insufficient publicity? Apparently some SeaMonkey testers don't read the SeaMonkey newsgroups (not by NNTP, not by mailing list, and not by Google Groups). Maybe next time we'll have to ask:
  • someone (ashughes? whimboo?) to publish the announcement on QMO
  • someone else (Aleksej?) on mozilla.status.net
  • some Council member to publish it on the SeaMonkey blog at Mozillazine, which is syndicated by Planet Mozilla
• Not enough emphasis on the fact that any user can be a tester, no special talents (beyond the motivation to do it) or privileges required? (A Bugzilla account is needed but anyone can get one for free; but that was mentioned in Before you start above.)
• SeaMonkey leaders don't have IRC chanop status on #bugday, and cannot change its topic (thanks Aleksej for taking the necessary steps on Saturday)
• Intended Hallowen-related humor in the prologue to this page ununderstandable to people with only an elementary command of English? ("what are Maggots?")
• Apathy? Thanks Px for giving the good example and figuratively kicking everyone else in the bottoms.

The full results as a Bugzilla search

By Severity and Status/Resolution — This display is not ideal but I couldn't find how to make Bugzilla report Status/Resolution on a single axis. Feel free to edit.

Two bugs stand out in the RESOLUTION totals:

• bug 18575 resolved FIXED: this is a meta bug, all whose dependencies were RESOLVED (and not as EXPIRED) as part of the Bug Event. Most of these had been either FIXED or made obsolete by the Toolkit Transition (Sm 2.0).
• bug 99661 left as EXPIRED but marked [Halloween2011Bug]: info was asked to the Thunderbird QA. If it happens on both, it's probably two (frontent) bugs but with similar (forked) fixes.

Details

In all bug links below, Bugzilla conventions are adhered to throughout: UNCONFIRMED, NEW or REOPENED, RESOLVED bugs.

At Mnyromyr's suggestion, this time a significant part of the effort was dedicated to trying to find a "proper" Status/Resolution for very old Suite bugs which had previously been marked UNCONFIRMED in June 2009 and/or RESOLVED EXPIRED in April 2010 for lack of any serious activity on them since the inception of the SeaMonkey project. Bugs whose Product::Component indicated that they might be relevant for the MailNews component and/or for the Sidebar were handled by priority; their dependencies were however not neglected.

A consequence of this choice (appropriate, maybe, for Halloween) is that some bugs which used to be RESOLVED EXPIRED have been "reawoken" and confirmed, bringing them back from the living dead, so to speak, and among the NEW bugs.

Other bugs which received particular attention were Composer bugs OT1H, and UNCONFIRMED bugs of all kinds OTOH.

Notes:

1. On some bugs, several triagers cooperated. We tried to attribute the bug to the one whose action was most decisive, but in some cases, there was an element of arbitrariness in the decision.
2. At least two bugs were found to have had their [Halloween2011Bug] whiteboard entry removed after the fact. We cannot guarantee that there were no others, which will thus have fallen off the bug list above and off all statistics below.
3. For the bugs which were RESOLVED, little attempt was made to move them to the appropriate Product::Component, many of them were left in SeaMonkey::General.

By Triagers

1. Px: 108
   104590, 105689, 113994, 115107, 133718, 154317, 162407, 242942, 243989, 244452, 268108, 302815, 327578, 327579, 334200, 382266, 384820, 385924, 400012, 405941, 439769, 443798, 452447, 456498, 457808, 469352, 486838, 490613, 491618, 491843, 498087, 498111, 502752, 509013, 512478, 515123, 516301, 523825, 525447, 525508, 525726, 526643, 527344, 528677, 529038, 531744, 532111, 535799, 536099, 536228, 538838, 538854, 539419, 541107, 546083, 551370, 555458, 559276, 560021, 570032, 571456, 573959, 577548, 577955, 581787, 562568, 591018, 591201, 599622, 600480, 602401, 602402, 608558, 608933, 609665, 609688, 609808, 610174, 611932, 614722, 615687, 616391, 618901, 621447, 621543, 621911, 622084, 622086, 622182, 622677, 623830, 624355, 624812, 625089, 625359, 626757, 628028, 628609, 628780, 630824, 634502, 634732, 639202, 639203, 639290, 639859
   Congratulations to Px who triaged more bugs than everyone else combined!
2. Mnyromyr: 49
   54258, 54613, 56037, 56058, 56441, 56669, 57216, 57397, 57696, 57813, 57855, 57859, 58587, 59049, 59263, 59509, 59820, 61848, 70304, 71402, 71538, 72006, 72349, 72596, 72600, 72607, 72609, 72824, 73089, 73105, 73247, 73424, 73714, 74357, 76066, 76212, 76219, 76398, 77348, 78025, 78241, 78264, 78457, 79186, 79238, 79472, 79786, 79871, 157217
3. IanN: 40
   63673, 64294, 63985, 73222, 88960, 89381, 90448, 94845, 95141, 96500, 99634, 100114, 104190, 105356, 108115, 114075, 192225, 233028, 243990, 360330, 367294, 406310, 412922, 476369, 485224, 524929, 525787, 538887, 539464, 555522, 573577, 573900, 592287, 592292, 597668, 608471, 612585, 619028, 621842, 622166
4. tonymec: 10
   18575, 51206, 54625, 55131, 64161, 68243, 99661, 99767, 99834, 578362
5. Ratty: 6
   504291, 521700, 525461, 574791, 632364, 63503

Moves by Product::Component

Product is SeaMonkey unless specified otherwise.

• Not moved: 200
  • Core::File Handling: 1
  • Core::XUL: 1
  • MailNews Core::Account Manager: 1
  • Autocomplete: 2
  • Composer: 23
  • Download & File Handling: 3
  • General: 38
  • Location Bar: 1
  • MailNews: Account Configuration: 12
  • MailNews: Address Book & Contacts: 1
  • MailNews: Backend: 8
  • MailNews: Composition: 7
  • MailNews: General: 7
  • MailNews: Message Display: 52
  • OS Integration: 4
  • Passwords & Permissions: 3
  • Preferences: 11
  • Search: 4
  • Session Restore: 2
  • Sidebar: 6
  • Themes: 5
  • UI Design: 8
• Moved: 13
  • Core::Networking:Cookies → UI Design: 1
  • General → Bookmarks & History: 1
  • General → UI Design: 1
  • MailNews: Account Configuration → MailNews Core::Account Manager: 1
  • MailNews: General → MailNews Core::Networking: POP: 1
  • MailNews: Message Display → MailNews Core::Backend: 2
  • MailNews: Message Display → MailNews Core::Networking: IMAP: 1
  • MailNews: Message Display → MailNews Core::Networking: NNTP: 1
  • MailNews: Message Display → OS Integration: 1
  • Preferences → Location Bar: 1
  • UI Design → Find in Page: 1
  • UI Design → Core:: Networking: FTP: 1
• Total: 213

Changes in Status/Resolution

Also:

• DUPEME: 5
• [CLOSEME 2012-01-01 INCO]: 5
• [CLOSEME 2012-01-01 WFM]: 39

By Keywords

Most bugs have no keywords at all, many have one, a few have several:

• 4xp : 3
• access : 7
• classic : 4
• crash : 1
• dataloss : 1
• hang : 2
• helpwanted : 4
• intl : 3
• meta : 2
• modern : 1
• perf : 5
• polish : 6
• qawanted : 1
• regression : 3
• smoketest : 1
• stackwanted : 3
• testcase : 3