Mozilla 1.4 and Netscape 7 have shipped. This is the first simultaneous release sice, hmm, ever? Have we done that before? Maybe one of those Netscape 6.x releases coincide with 0.9.2 or 0.9.4? It's mostly a blur these days. I've been doing these releases for almost exactly 3 years now and I think with 1.4 I'm up to about 40 of them. Wow. Fun stuff.
Well, 1.4 makes me happy. It's a great relase with a darned good featureset but I'm even happier about Netscape 7.1 because it's shipping DOM Inspector and Venkman! This is really exciting to me because I think these are great tools and getting them into the hands of a larger audience of web developers is a great thing for everyone.
Posted by asa at June 30, 2003 10:40 PMCongratulations and kudos to all your hard work. I think i'll skip mozilla 1.4 in favor of firebird 0.6, but mozilla 1.5 would definitely be very interesting.
Posted by: vfwlkr on June 30, 2003 11:22 PMIt's all very exciting, but I think everyone is really looking forward to Mozilla 1.5 (Netscape 7.5?) for obvious reasons.
Posted by: MikeyC on July 1, 2003 12:03 AMI just checked Bugzilla and it still lists bugs 104532 (Status bar ticker fails to update when tabs switched) and 204374 (GDI Resources are used till the UI/website displays faulty) as open. 204374 is a blocker. Am I doing something wrong or have these slipped through the cracks?
I just wonder why ChatZilla is in the "Developer Pack". Is an IRC-client a developer tool?!
Sometimes it's really hard to understand Netscape's decisions. :)
Congrats on getting Mozilla 1.4 out the door. Here's to hoping for a successful and smooth 1.5 dev cycle. :)
Posted by: milbertus on July 1, 2003 04:53 AMFirstly, yay for getting 1.4. Just looked through a few dates, and I think it is the first simultaneous release - some of the others were quite short gaps, but not simultaneous, AFAICS.
And to adaxl - bug 104532 has the "verified1.4" keyword. If a bug has "fixed1.4" or "verified1.4" it means the bit of it that was blocking the release is fixed. That bug has a cover-up patch on the 1.4 branch, but hasn't yet been fixed on the trunk, so it remains open. The other bug really did "slip through the cracks", although not in the sense that it was forgotten, just that they didn't hold up the release for it after all. It doesn't really merit "blocker" severity, as there is a workaround. There's a couple of other fixes that should have been in 1.4 but didn't make it - I guess they'll be in 1.4.1...
Posted by: michaell on July 1, 2003 07:53 AMIs there any hope that Netscape will switch to the standalone browser approach as Mozilla has? Netscape will remain a non-factor until such time so it would be great if they'd do it soon. The enthusiastic response to Firebird demonstrates that this is a no-brainer.
Posted by: pb on July 1, 2003 08:46 AM