Minutes of the mozilla.org Staff Meeting of Monday 2nd June 2003
Monday June 16th, 2003
The minutes of the mozilla.org staff meeting of Monday 2nd June 2003 are now online. Issued discussed include the Creating XPCOM Components book, 1.4 final and 1.5.
>Ideally we will have simultaneous Mozilla 1.5beta, Firebird 0.8, >and Thunderbird 0.1 releases.
Is 1.5b goint to be a bundle of Moz FB 0.8 and TB 0.1? It's not clear from the minutes.
#10 Re: They previously said they were not!
Tuesday June 17th, 2003 5:36 AM
> Is 1.5b goint to be a bundle of Moz FB 0.8 and TB 0.1? It's not clear from the minutes.
That's because it's not yet clear. :-)
Doesn't look like it at this point. Months of work still remain to integrate Firebird and Thunderbird development into the trunk.
Actually, I'm a bit confused about this for sometime now.
People say MozillaFirebird and MozillaThunderbird are codename of Mozilla 1.5 development builds. But I currently see that Mozilla1.5a trunk (SeaMonkey) and MozillaFirebird+MozillaThunderbird are on development at the same time (right now).
So how does it actually work?
They are still standalone components. They always will be. But Mozilla 1.5 will now have Firebird and Thunderbird as its browser and mail/news.
Yea, I know Browser and mail/news will become stand alone in 1.5.
I was actually not asking about 1.5 FINAL. I was asking about 1.5a. The current 1.5a is clearly a complete suite. And they are shipping 1.5a trunk (seamonkey) and Firebird and Thunderbird together right now. So I just wonder what they will do to make Firebird and Thunderbird to replace SeaMonkey. (e.g. Are they going to keep developing seamonkey and firebird+thunderbird at the same time and make them "closer and closer"? Or.. etc)
As far as I understand they intend to convert all the internal bug tracking system, etc to FB/TB as soon as 1.4 "final" is out. However, it does not look very promising at this point that 1.5 schedule will be met. 1.4 is nowhere near to be released.
I guess it will take a month to move fully to FB/TB and only after that "real" development start happening, also considering that we have summer now, most probably a lot of developers will have some sort of holidays. I guess the best would be to postpone 1.5 "until it is ready". Thunderbird needs real work to be done with it to make it a good replacement of Outlook Express for many users. Also none of the optimization was done so far, afaik - since TB takes full 50Mb of ram (physical + virtual). And both projects still use their own GRE, even thought as I understand they should have one in common. Well, I'm not really expecting to see anything "working" until later this fall, but may thats a good approach, since both TB&FB lack some needed functionality.
My only wish is for them to make MIDAS work in FB as soon as humanly possible, also most of the recent nightly builds of FB are broken completely, not being able to display even simpliest of the websites. :( I had to go back to Gecko 1.4b releases.
#13 Re: Re: Re: Why does it take so long
Tuesday June 17th, 2003 11:13 AM
Hey, you get problem wiwth FB nightly builds? What problem? I am using the latest nightly builds of FB on RedHat8 and WinXP. It works fine for me on both platform. I'm in fact using this to post this post.
#14 Re: Re: Re: Why does it take so long
Tuesday June 17th, 2003 11:56 AM
> also considering that we have summer now, most probably a lot of developers will > have some sort of holidays
Which in the case of all the developers who are students means they actually have time to work on Mozilla... ;)
I find it interesting that they mention Firebird 0.8 as being the 1.5 releases! What I find so cool about this is that means the wait for 0.7 won´t be so far off!! Yay!! (Not that i´m not happy with 0.6, but there seems to be some performance regressions, a bit slower)
> Need to hook up DOM Inspector, site nav, Venkman, style switching into a 'default build'
Will there be a minimalist build? I certainly don't use any of the above. I know they're important for development purposes, but I sure would prefer a smaller download.
I think it just means that there have to be a few internal hooks. DOMI is already available as an extension and the current Mozilla installer doesn't force you to include it either.
No, it actually means: "We must have Mozilla builds usable by Mozilla developers and QA, which means that they need to include all of the developer/QA stuff in a single tarball or zip archive". None of the people who would be getting said builds actually use the installer...