MozillaZine

Mozilla 1.0.1 Update

Thursday June 20th, 2002

Judson Valeski has posted an update on Mozilla 1.0.1 to the newsgroups. As the 1.0.1 release is close, the bar has been raised and only fixes for high visibility problems are currently being accepted on the 1.0 branch. Read Jud's full message for more details.


#1 Can someone post the message here? (-)

by ezh <ezh@menelon.ee>

Thursday June 20th, 2002 2:39 PM

Reply to this message

Tnx

#2 Re: Can someone post the message here? (-)

by zipo13

Thursday June 20th, 2002 2:47 PM

Reply to this message

mozilla1.0.1 is winding down. starting yesterday we started tapering down approvals by minusing requests that don't meet the further restricted criteria. A few weeks ago the following criteria was posted for 1.0.1 checkins.

"To provide more clarification regarding what we're targeting 1.0.1 for... we are generally looking for fixes to _high_ visibility problems, stability improvements (topcrash bugs), & near zero risk polish issues. The scope of 1.0.1 is more narrow than 1.0. Not everything that was declined for 1.0 should be requesting 1.0.1 checkins. Yes, the 1.0 branch is going to be alive for awhile, but, architecture work, feature work, risky changes, edge case work, and the like should be happening in our life blood, the trunk; not the 1.0.1 branch."

Now we're looking for even _higher_ visibility problems. topcrash is topcrash is topcrash. Low risk fixes to topcrash bugs are always strong candidates. We're shooting for nearly full lock down by Monday (the 24th of June), so, if you have bugs you want to include in 1.0.1 (that meet the above, further, narrowed criteria), send them to <drivers@mozilla.org>. We are only fielding bugs that have landed on the trunk and have baked there for at least two days, and that have been verified as resolved on the trunk.

Will there be a 1.0.2? If there's a need, there will be a 1.0.2.

Jud

#3 Re: Can someone post the message here? (-)

by AlexBishop <alex@mozillazine.org>

Thursday June 20th, 2002 2:56 PM

Reply to this message

Sorry about that. Still waiting for the message to turn up on Google Groups.

Alex

#4 Whatever

by Tanyel <tanyel@straightblack.com>

Friday June 21st, 2002 3:52 PM

Reply to this message

The page at <http://www.mozillazine.org/archive.html> seems to be broken. The dates are replaced with letters.

#11 Re: Whatever

by MXN

Saturday June 22nd, 2002 7:12 PM

Reply to this message

A lot of the pages here at MozillaZine are like that, including the poll talkbacks. That problem was fixed in these talkbacks a long time ago. No one's really been paying attention to the less visited pages, though.

- MXN

#5 Does this include any 1.1 changes?

by ph1nn <ph1nn@earthlink.net>

Friday June 21st, 2002 4:06 PM

Reply to this message

Does this include any of the l33t 1.1 changes like performance tweaks, fast loading XML, download manager, etc?

Or is it just a bug fixed 1.0

IF so... ill stick with the "cutting edge" 1.1 builds cause they are plenty stable anyway

#7 bug 150829

by thegoldenear

Friday June 21st, 2002 10:55 PM

Reply to this message

it is just polishing of 1.0.0

you miss the point of what the 1.0.x branch is all about - try reading around some of the comments here and documentation at mozilla.org

fast loading XUL, not XML

stick with the trunk

#10 Re: Does this include any 1.1 changes?

by marmoset

Saturday June 22nd, 2002 8:24 AM

Reply to this message

It almost goes without saying that anyone interested enough in the Mozilla development process to be following this forum is better off tracking the trunk than the 1.0x branch.

#6 I don't get it.

by jonasj

Friday June 21st, 2002 8:19 PM

Reply to this message

> A few weeks ago the following criteria was posted > for 1.0.1 checkins. > > "[...]we are generally looking for fixes to _high_ visibility > problems, stability improvements (topcrash bugs), & near zero > risk polish issues.

So how come they approved the New Tab button (new feature) but not the patch to remove the very buggy "Open a link in a new window" checkbox from Scripts & Windows (zero risk polish)?

<JTK>Oh, of course -- it's because Netscape wanted it.</JTK>

I'm starting to lose my faith in mozilla.org :-(

#8 Re: I don't get it.

by WillyWonka

Saturday June 22nd, 2002 8:19 AM

Reply to this message

"So how come they approved the New Tab button (new feature) but not the patch to remove the very buggy "Open a link in a new window" checkbox from Scripts & Windows (zero risk polish)?"

What is buggy about it? It doesn't support JavaScript window.open but the targeting types of popups it seems to fix. Is that the bug?

#15 Re: Re: I don't get it.

by jonasj

Monday June 24th, 2002 7:09 AM

Reply to this message

Exactly, that's the bug. You can't expect end users to understand the difference between window.open and target="_blank"; they will think that the feature is buggy and file bugs like <<http://bugzilla.mozilla.org/show_bug.cgi?id=145418>>. See bug 78037.

#9 Re: I don't get it.

by AlexBishop <alex@mozillazine.org>

Saturday June 22nd, 2002 8:20 AM

Reply to this message

"So how come they approved the New Tab button (new feature) but not the patch to remove the very buggy 'Open a link in a new window' checkbox from Scripts & Windows (zero risk polish)?"

The New Tab button isn't really a new feature. It's just a new button that activates an existing command. As the only change it's introducing is a graphic and a little bit of simple XUL, it's not really got any risk at all.

Alex

#12 Testing = Using

by TheK <kl@3dots.de>

Sunday June 23rd, 2002 4:02 PM

Reply to this message

the only risk on this button is, that many themes doesn't support it.

#13 Re: Testing = Using

by Dobbins

Sunday June 23rd, 2002 7:26 PM

Reply to this message

"the only risk on this button is, that many themes doesn't support it."

Another "risk" was checking the modern icon into the classic theme where it joins the new mail popup in sticking out like a sore thumb.

#14 Heh

by seymour <chris@blackplasma.net>

Sunday June 23rd, 2002 10:59 PM

Reply to this message

Heh, that was the first thing I noticed. Orbit doesn't have it yet, I'm looking forward to seeing a nice button for it.

#16 1.0.2

by Salsaman

Monday June 24th, 2002 8:41 AM

Reply to this message

The message implies that there may not be a 1.0.2 release after this. If a decsion is made for there not to be a 1.0.2, what will happen to the 1.0 / 1.0.1 branch ?

Would the expectation then be that everyone should move to 1.1 when it's released ?

#19 Re: I don't get it.

by AlexBishop <alex@mozillazine.org>

Monday June 24th, 2002 12:21 PM

Reply to this message

The 1.0 branch is supposed to be a mature and stable baseline that vendors and other developers can work from. It will probably be around for at least a year. Upgrades to the branch (1.0.1, 1.0.2, 1.0.x etc.) will only be made if it's neccessary: critical fixes (security bugs etc.) and other "additive" changes.

All the exciting new stuff is supposed to happen on the trunk. The branch is there for those who want well-tested code that is (pretty much) guaranteed to work.

Alex

#17 Re:

by PsychoCS

Monday June 24th, 2002 9:01 AM

Reply to this message

The information is all here : <<http://www.mozilla.org/roadmap.html>>

If you're not willing to *really* test and are here to see a good browser, then my advice would be to stick with the branch builds (1.01, 1.02 etc.)

#18 Heh, meant to reply to the message above. (n/t)

by PsychoCS

Monday June 24th, 2002 10:59 AM

Reply to this message

st00pid