Mozilla 1.0.1 is Basically Done

Friday June 28th, 2002

Judson Valeski has posted a newsgroup message saying that Mozilla 1.0.1 is almost complete. "Approvals have been tighter since Monday (the 24th), and the idea is that they will become nonexistent starting this Monday (July 1st, 2002)." Mozilla 1.0.1 should be complete by the middle of next week, bar any unforeseen problems (if you know of any, tell drivers@mozilla.org now).

#1 Full Message

by AlexBishop

Friday June 28th, 2002 7:11 PM

Subject: mozilla 1.0.1 is ... From: Judson Valeski <valeski@netscape.com> Date: Fri, 28 Jun 2002 13:28:13 -0600 Newsgroups: netscape.public.mozilla.seamonkey,netscape.public.mozilla.general,netscape.public.mozilla.builds

... basically done. Approvals have been tighter since Monday (the 24th), and the idea is that they will become nonexistent starting this Monday (July 1st, 2002). If drivers is missing something, please make us aware of it (jump up and down, yell, scream, kick, call, email, msg, etc.; but, make sure you would be willing to stop the release of the milestone for it). Otherwise, we're planning on being complete by mid next week. If folks see a need for a release candidate ("1.0" style), please vocalize.

Jud

#2 Re: Full Message

by pepejeria

Saturday June 29th, 2002 6:36 AM

Cool, hopefully Netscape 7 will be based on Mozilla 1.0.1 What I dont understand is all the bugs targeted to Mozilla 1.0.1 and for example Mozilla 1.1a. Will they be moved to Mozilla 1.0.2/Mozilla 1.2?

#3 yep

by johnlar

Saturday June 29th, 2002 8:17 PM

Thats what has been going on for a long time now. Releases get released and targets that don't make it get pushed back.

#4 An Idea

by Tanyel

Saturday June 29th, 2002 10:28 PM

Maybe they should reschedule all of the bugs for version 7.5 so Mozilla 7 can be released long before IE 7 is ready. That will also solve the problem of version differences between Netscape and Mozilla.

#5 Re: Re: Full Message

by joschi

Sunday June 30th, 2002 10:24 AM

as i understand it, targets are not promises, its more like each developer is scheduling which bugs they would _like_ to do by then, but they often take on a different set of bugs than they initially planned for various internal and external reasons, and the targets get shuffled. the bugs which actually block a release are determined by the release team.