Tree Closes Tonight for Mozilla 0.9.9
Tuesday February 19th, 2002
mozilla.org will begin the process to release Mozilla 0.9.9 tonight at 11:59 pm pacific by closing the tree to free checkins. Mozilla 0.9.9 is the last major milestone prior to 1.0, and includes numerous bugfixes in composer, history, and other areas. Along with this, likely new features that will be in the milestone include a new full screen window mode, set image as wallpaper, and composer publishing.
Following the tree close tonight, expect up to a week of tree closure for stability and regression fixes, then a branch to be cut some time next week. As soon as the branch is cut, the trunk will reopen for Mozilla 1.0 checkins. mozilla.org is shooting for a March 1st release date, but due to this being the last milestone before 1.0, and because there is a large amount of code that will be landed tonight prior to tree close, delays may occur.
#136 Re: Re: Re: Bugzilla defect curves (was Re: Re: Re
Monday February 25th, 2002 9:56 PM
You are replying to this message
With respect to the issue that only bad news gets reported, you've pretty much convinced me. I would note that there are also factors working in the other direction: lack of Talkback on Mac, crashes that are so severe they disable Talkback, and people opting out of Talkback reports. It's hard to say which is a stronger force, but as I said, the last time I tried using a milestone for a day, it crashed almost exactly on schedule, after about four hours.
It's also surely worth nothing that the so-called MTBF rating has been going down rather than up over the last few months. Mozilla fans were happy to take credit when it was creeping up last fall, but now that it's creeping back down, it seems that's not of any real significance. You can't have it both ways. Good dials good, bad dials irrelevant?
I don't agree on the higher duplicates issue with Reopened bugs. Seems to me you're not basing that on any analysis. It would also seem very strange if key players weren't taking a close look at Reopened bugs, since those are the ones that (from a root-cause analysis perspective) are most likely to point out basic stability problems. Anyway, the argument that's been made that the New and Unassigned defect curves don't count has been that no one was looking at them -- if that's true, then the Reopened bugs do at least have someone looking at them, and so ought to be more accurate.
I agree that there are different kinds of Reopened. As I said, it would be good if there were better charting facilities in Bugzilla. More powerful query inputs to the charts would produce better data. You haven't done anything to establish that the majority of Reopened bugs aren't regressions, though, only that some aren't. Looking at the chart, I see a correlation with milestones that received relatively better or worse public reception on quality grounds.
Does it seem to you like it's just a coincidence that all the metrics established to mark progress on the project are negative? Can systemic errors account for the situation actually being rosy but there being not a single quantitative indicator that points in that direction? That's seems pretty dang weird to me. The large software projects that I've shipped were all highly dependent on QA metrics to find their way out of the forest of problems that is product release. All the indicators seem to show the plane is flying into a mountain, but don't worry, it's just all the dials that are wrong? I have a hard time buying that. I do agree that the dials are wrong, though.