MozillaZine

Trunk Freezes for 1.4 Alpha Tonight

Tuesday March 25th, 2003

To prepare for the impending 1.4 Alpha release, the main Mozilla development tree will freeze at 11:59pm tonight (Pacific Standard Time). While the trunk is frozen, only checkins that have been approved by drivers@mozilla.org will be allowed to land. The tree will be reopened when Mozilla 1.4 Alpha is released (the current ideal release date is this Friday). See tinderbox and the Mozilla Development Roadmap for more information.


#1 This friday?

by jedbro

Tuesday March 25th, 2003 9:26 AM

Reply to this message

As I am all for 1.4 coming out this friday, can anyone tell me why 1.3 and 1.4 will be released so close together? Damn, I'm just digesting 1.3 at the moment *grin*.

I do realize that the trunk for 1.4 has been open for a long time, but what is so important about this release? Many have speculated that this is an important release for Embeders... is this true? Any factual links? Cheers

#2 Re: This friday?

by simifilm

Tuesday March 25th, 2003 9:40 AM

Reply to this message

Do you realize, that we're talking about 1.4 ALPHA here?

#20 how about speed improvements

by ph1nn <ph1nn@earthlink.net>

Wednesday March 26th, 2003 11:48 AM

Reply to this message

we need ownage on IE... that last benchmark test was embarassing, screw new features ;-)

#3 Re: This friday?

by AlexBishop <alex@mozillazine.org>

Tuesday March 25th, 2003 9:43 AM

Reply to this message

"As I am all for 1.4 coming out this friday, can anyone tell me why 1.3 and 1.4 will be released so close together?"

Well, they won't be really. Remember this is only 1.4 Alpha, not final.

"I do realize that the trunk for 1.4 has been open for a long time, but what is so important about this release? Many have speculated that this is an important release for Embeders... is this true?"

If it is, it will be important because embedders want it to be important, rather than mozilla.org just deciding it is (of course, mozilla.org will work with embedders to help Mozilla 1.4 meet their needs).

Alex

#7 Re: This friday?

by asa <asa@mozilla.org>

Tuesday March 25th, 2003 10:40 AM

Reply to this message

"can anyone tell me why 1.3 and 1.4 will be released so close together?"

1.4 _alpha_ has been open for 5 weeks of development and it's time for a milestone. We've learned over the years that a cycle between 4 and 7 weeks seems to best accomodate a number of factors like talkback data, milestone bug feedback, feature development, etc. As you can see at the roadmap <http://www.mozilla.org/roadmap.html> we release milestones pretty regularly. This is not 1.4. This is 1.4 alpha. We will have 1.4 beta in about a month and 1.4 final a few weeks after that. The actual relase of 1.4 isn't scheduled until mid-May.

"but what is so important about this release?"

We've been doing milestones every 4-7 weeks for the last 4 years (actually, I believe that M3 came out four years ago this week). We've fixed about 1000 bugs since 1.3 branched and we've added some great new features like smooth scrolling, a transaction manager and more for bookmarks, context menus and other improvements for junk-mail controls, access keys for the xp filepicker, clipboard buttons for composer. We've fixed nearly 50 crash bugs, about 15 memory leaks and we've made serious improvements to Web site compatability.

"Many have speculated that this is an important release for Embeders... is this true?"

We're working hard to make every milestone significantly better than the last. We expect that trend to continue. There are a number of organizations that are interested in using 1.4 branch code in their releases. The more testing and development resources we have focused on any given milestone, the better for the quality of that release. It's rare that we do a final release where some organization isn't interested in using that code but having several (or more) groups delivering products from one branch usually means more resources focused on making that branch as good as it can be. So the more support we can rally for one branch, the better for all those releasing products from that branch. The 1.4 rally is building momentum and I'd enourage anyone planning a Mozilla-based product this summer or fall to contact <drivers@mozilla.org> and seriously consider using the 1.4 branch.

--Asa

#10 Re: Re: This friday?

by jedbro

Tuesday March 25th, 2003 12:29 PM

Reply to this message

""We've fixed nearly 50 crash bugs, about 15 memory leaks and we've made serious improvements to Web site compatability. """

Great to hear that. Cheers for the response, I guess the delayed 1.3 made me think 1.4 alpha was very quick (hey, Im not complaining).

Cheers Asa, and alex, for your help.

#21 Re: Re: This friday?

by cginzel

Wednesday March 26th, 2003 11:52 AM

Reply to this message

Just a point of clarification for myself. Does all of "We've fixed about 1000 bugs since 1.3 branched and ... fixed nearly 50 crash bugs, about 15 memory leaks and we've made serious improvements to Web site compatability" get applied back to the 1.0 branch? And, at what point does the 1.0 die? I guess when API changes occur?

#25 Re: Re: This friday?

by ksheka

Friday March 28th, 2003 5:52 AM

Reply to this message

I think the APIs have changed. That's why some XPI plugins have been recompiled to work with newer versions of Mozilla (ie: Calander and Spallcheck).

Since there's been so much changes in Mozilla since 1.0, I can't imagine back-porting the bug fixes to the 1.0 branch.

It seems that 1.0 will die when no one releases code based on the 1.0 branch. Netscape's latest release was based on the 1.0 branch. Speculation has been that Netscape (and others?) will use 1.4 for future releases, so a long-lived 1.4.x branch may be appropriate. If no one uses the 1.0 branch, it will effectively die.

#4 who's car is this?

by macpeep

Tuesday March 25th, 2003 10:10 AM

Reply to this message

A friend of mine who lives in DC took this photo today: <http://68.100.156.166:8080/paw/temp/mozilla.jpg>

Who's car is it? :D

Peppe

#12 The question is

by googolplex

Tuesday March 25th, 2003 4:08 PM

Reply to this message

The question is:

Who's head is that in there? :P

#13 Re: who's car is this?

by AlexBishop <alex@mozillazine.org>

Tuesday March 25th, 2003 4:29 PM

Reply to this message

"A friend of mine who lives in DC took this photo today: <http://68.100.156.166:8080/paw/temp/mozilla.jpg> "

Was your friend driving at the time? Isn't that a bit dangerous?

Alex

#19 Re: Re: who's car is this?

by macpeep

Wednesday March 26th, 2003 9:37 AM

Reply to this message

I believe he was. Probably.

#17 Re: who's car is this?

by the_Rebel

Tuesday March 25th, 2003 8:37 PM

Reply to this message

Car? Looks like a truck to me. :)

#5 Re: Re: Great!

by damian <daemonc@netscape.net>

Tuesday March 25th, 2003 10:21 AM

Reply to this message

Wow, Mozilla.org is really committed to their release schedule. Can you name one other project this size that pushes out stable releases this fast? I can't...

#6 Re: Re: Re: Great!

by mlefevre

Tuesday March 25th, 2003 10:36 AM

Reply to this message

the fast schedule is good in many ways, but this isn't "stable", it's an alpha!

#14 What about Red Hat Linux...

by rkl

Tuesday March 25th, 2003 5:08 PM

Reply to this message

How about Red Hat ? :-) Red Hat Linux 8.0 came out on 10th September 2002 and on 31st March 2003, just over 6 months later, we will be seeing RH 9 being released (and they had something like 3 full multi-CD beta releases inbetween those as well). This is a massively fast churn speed for a major version jump of an entire operating system (I suspect even the quickest Mozilla cycles haven't been as fast as that).

What's a little more upsetting with Red Hat, and not really a problem with Mozilla, is that no fixes will be released for any pre-9 version after the end of this year, which effectively leaves them open to security vulnerabilites and forces the user to either re-compile affected packages from source+patches (not always easy) or be forced to upgrade to 9 (which is fine for desktops, but a nightmare for live production servers)..

At least with Mozilla, you just download a new nightly or wait for the next milestone release (and report any bugs you find inbetween to Bugzilla of course :-) ).

#15 [OT] i think you misunderstand red hat

by joschi

Tuesday March 25th, 2003 5:38 PM

Reply to this message

<http://news.com.com/2100-1016-994074.html>

if you need long term support, dont run their lighter desktop version of redhat (redhat 9), use their enterprise edition.

#22 redhat doesnt count anyway

by ph1nn <ph1nn@earthlink.net>

Wednesday March 26th, 2003 12:44 PM

Reply to this message

RedHat doesnt count anyway, they are coding a huge application like Mozilla, they dont have to worry about patches coming from every part of the globe, people hacking it together, keeping it stable and secure and getting it out there.

RedHat, like all distros for the most part are just a collection of the work everyone else has done in Linux packaged together and a team of tech support llamas.

I could be wrong... but i give more credit to the Mozilla team hackers

#23 Re: redhat doesnt count anyway

by AlexBishop <alex@mozillazine.org>

Wednesday March 26th, 2003 12:55 PM

Reply to this message

"RedHat, like all distros for the most part are just a collection of the work everyone else has done in Linux packaged together and a team of tech support llamas."

Red Hat do employ many people (e.g. Alan Cox) to contribute to Linux.

Alex

#24 plus mozilla and gnome hackers

by joschi

Wednesday March 26th, 2003 1:40 PM

Reply to this message

redhat employ many hackers, they definitely count :)

#8 1.3 final <-> 1.4 alpha

by gadeiros <Harald@Henkel.DAH.UUnet.DE>

Tuesday March 25th, 2003 12:21 PM

Reply to this message

What features and / or bug fixes in 1.3 final will not be in 1.4 alpha ?

Is there a simple select for this ?

#11 Re: 1.3 final <-> 1.4 alpha

by AlexBishop <alex@mozillazine.org>

Tuesday March 25th, 2003 12:44 PM

Reply to this message

"What features and / or bug fixes in 1.3 final will not be in 1.4 alpha ?"

1.4 Alpha will have everything that 1.3 does. Unless some features/bug fixes are backed-out, which doesn't happen that often and is usually for the greater good.

You'll probably find 1.4 Alpha is buggier overall than 1.3 though.

Alex

#9 1.3 final <-> 1.4 alpha

by gadeiros <Harald@Henkel.DAH.UUnet.DE>

Tuesday March 25th, 2003 12:21 PM

Reply to this message

What features and / or bug fixes in 1.3 final will not be in 1.4 alpha ?

Is there a simple select for this ?

#16 Mac Version since 03/25/03 crahses upon launch

by PaulB <pbergsag@home.com>

Tuesday March 25th, 2003 6:15 PM

Reply to this message

I hope 1.4a will wait until bug 199069 "Browser crashes upon launch". Is anyone else experiencing this on MacOS X?

#18 Editor embedding

by biswapesh

Tuesday March 25th, 2003 9:54 PM

Reply to this message

Since 1.4 is being touted as important for embeddors, does it mean that the editor APIs will br frozen, so that we can write native WYSIWYG HTML editors using the Editor control with, say, GTK ?

#26 Re: Editor embedding

by bzbarsky

Saturday March 29th, 2003 10:37 PM

Reply to this message

Last I looked at the Editor APIs, they were nowhere close to freezing or being freezable... it'd take some work to get them there.