Three Monkeys, Three Typewriters, Two Days

November 23, 2003

Info barrage, continued

I stopped keeping track because it got depressing. Here's the tally for the last two days (granted, it was a weekend... but I was trying not to spend too much time on Mozilla stuff):

  • Newsgroup reading: 5 minutes
  • Mozillazine, etc: 20 minutes
  • Bugmail (commenting on bugs and debugging stuff prompted by bugmail included): 5 hours, 23 minutes
  • Other (coding, reviews): 3 hours, 4 minutes

Summary: I need to uncc myself off some of those thousands of bugs.

Posted by bzbarsky at 9:24 PM

November 22, 2003

Info barrage

What's a reasonable amount of time (say per week) to expect someone to spend on reading bugmail, bugs (possibly as a result of bugmail), patches, Mozilla newsgroups, Mozillazine forums, Mozillazine article talkbacks, etc? How much do people spend? I include time spent posting to the above lists and forums in "time spent reading."

I'll attempt to keep track of this for a few days (with the caveat that I'm trying to minimize the amount of time I spend on such pursuits; for example I no longer read any of the Mozillazine forums)... I'll be posting the results sometime.

Posted by bzbarsky at 6:56 PM

November 18, 2003

Mozilla 1.7 plans?

I wonder when we plan to freeze 1.7a.....

Posted by bzbarsky at 8:10 AM

November 10, 2003

Birthdays

To somewhat rip off Tom Lehrer, "By the time Galois was my age he had been dead for over three years."

Posted by bzbarsky at 12:16 PM

Tokens

Touching nsHTMLTokens and nsHTMLTokenizer is not good for sanity. The worst part is, it's about as clean as it can be given what it has to deal with.

Posted by bzbarsky at 12:44 AM

November 5, 2003

More on Bugzilla

Just to expand on my previous post... Bugzilla offers a number of features and a number of annoyances. In fact, anything that's not a feature but generates bugmail is an annoyance, in my opinion.

From a developer's point of view, the features (and I only list features which generate bugmail below; searching and such are not on the "possible annoyance" list) are:

  • Ability to have bugs filed and steps to reproduce the bug reported.
  • Ability to have testcases attached.
  • Ability to prioritize bugs.
  • Ability to classify bugs based on what code is involved or what sort of code-level issue it is.
  • Ability to track progress on fixing a bug and discuss possible fixes.
  • Ability to request, give, and receive reviews
  • Ability to attach patches.
  • Ability to resolve bugs.
  • Ability to cc people who need to look at a bug on it and request that they do so.

From a project manager's (drivers') point of view, I think the features would be:

  • Ability to receive approval requests
  • Ability to receive requests for blocking status
  • Ability to set approval or blocking flags
  • Ability to cc people who need to look at a bug on it and request that they do so.
  • Ability to track progress toward major project goals via tracking bugs.

From a QA perspective, the features are:

  • Ability to have bugs filed and steps to reproduce the bug reported.
  • Ability to create testcases and attach them to bugs.
  • Ability to categorize bugs based on the code that's buggy.
  • Ability to cc people who need to look at a bug on it and request that they do so.
  • Ability to mark bugs as verified.

From a user perspective, the features are:

  • Ability to file bugs.
  • Ability to find out when a bug is resolved.

Note that for many operations only some of those groups are interested in the bugmail. Also note that many people wear multiple hats (the developer+QA+user combination being rather common, as well as the QA+user combination).

The bugzilla comments that tend to piss people off are the ones that fall into the "annoyance" category for all of the classes of users involved—mass-changes, pointless tracking bugs, cc-munging, etc, etc.

Posted by bzbarsky at 12:51 AM