Tree Closes Tonight for Mozilla 0.9.9

Tuesday February 19th, 2002 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. 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.

#105 Attention- help get a vital bug acted on ASAP

by jensend <>

Saturday February 23rd, 2002 8:07 PM

You are replying to this message

Excuse my intrusion on the arguments- please read the bug before you make a lot of remarks concerning the bug. Moz developers have, as a whole, agreed that using resource urls in preference files is feasible to implement with little effort, is necessary for more than just dual-booting (see the bugs which depend upon it), and is the way of the future. The bug had an odd argument in its comments because a couple of people didn't understand the nature of the bug (comments about 52 to 62), but the rest of the commentary is informative. This is not just a dual-booting bug. It was first posted by a moz developer who wasn't dual-booting but was concerned about the tendency of his prefs to be stored in an absolute instead of relative way, which is contrary to design ideals. Only considerably later was it made a point that this would enable dual-booting profiles. The bug is not, as far as I understand, "potentially destabilizing"- please see bug comments 11-14. Comment 28 was the first to address dual-booting- over two years after the bug was opened. This bug is, when its dependent (and really dupe, in my opinion) bug 58647 is included, is definitely a mostfreq- which suggests that a much larger portion of Moz users than .125% are concerned about this bug. Thank you in any case for pointing out to me, albeit in an indirect way, that I need to include more information about this bug in any later attempts to help draw attention to this bug.