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.
#150 Re: Re: Re: Re: MTBF (was Re: Re: Re: Re: doh)
Tuesday February 26th, 2002 10:23 AM
You are replying to this message
The Talkback agent does keep counting the browser runtime between starts and stops. It takes a failure, however, before _any_ data is sent to the talkback server.
" The only thing that would be missing in that case is the times when people installed a NEW browser, used it for a short time until they AGAIN got a new browser and did not crash in between. I doubt those people are so many that it would be a big factor in the statistics.. Maybe I'm wrong.."
You are. You're very wrong. "The _only think that would be missing_?" That would read better if it said, "The more common case that is missing". You can doubt all you want about Mozilla nightly downloads but that fact is that the overwhelming majority of people downloading the nightly builds are doing just that _downloading_ _nightly_ builds_. They don'y use those builds for months on end, they don't all use them exclusively. They do use those builds for a day's worth of browsing (or less) and then they get the next nightly build. Talkback does not measure uptime across different builds and a significant percentage of users do not crash in between the two builds. I, for example, am about to get my Tuesday morning build and I haven't crashed Monday's build (at least 14 hours of use). I'm not alone in this. This is born out by looking at the percentage of people who send in thier first talkback report with many days usage before a crash in Milestone builds. You can feel free to doubt all you want and you can talk, like strauss, as if you knew something on the subject but there are much more knowledgeable people (dozens of them) that know what this data means, and how to get the most value out of it. All the speculation in the world here at mozillazine doesn't make the browser any better. If you actually want to do something to help improve Mozilla's uptime then let me know and I'll be glad to help get you started. If you're not actually going to do something useful then I've already wasted too much time explaining things you.