0.9.2 Branch and Beyond
Sunday June 24th, 2001
Chris Blizzard has posted an update on current tree management plans for the 0.9.2 branch and the 0.9.3 trunk. The plan calls for mozilla.org to drop the requirement of firstname.lastname@example.org approval for check ins to the trunk, while continuing it till 0.9.2 is finished on the branch. Chris felt that using 0.9.2 as a stability milestone was a success, partly thanks to the drivers requirement, but mostly due to better self policing by those who were checking in.
#37 Re: The point is the goals changed!!
Tuesday June 26th, 2001 3:58 PM
You are replying to this message
One more note: It appears to me what is being implemented is not a stability milestone, but a release milestone. At a release milestone, code is frozen. All bug fixes are locked out except for those required to ship the product, because even apparently low-risk fixes might turn out to cause problems.
The reason for 0.9.2 being redefined as a release milestone is because Netscape plans to push out yet another premature browser version based on this still-not-quite-ready-for-prime-time code base. (No criticism implied -- it may be ready for prime time in a little while, it's just not there now.)
Given that we all know Netscape has seriously damaged the Mozilla effort through these premature releases, to the point where for a while all Netscape 6 articles were banned on this site, I'm surprised to see people defending this practice here. Mozilla needs to be going ahead full tilt to fix as many of the remaining bugs as possible. This artificial code freeze to support another bad Netscape 6.x release is not in Mozilla's best interests.