2003-04-28 - Summary of mozilla.org staff meeting
Gervase Markham
-------------------------------------------------
Present: Marcia, Myk, Asa, Scott, Dan, Chris and Gerv.
*1.4 Beta*
- Been frozen for nearly a week now
- Ideally would have shipped last Friday, but not as much hassle as for
alpha.
- 20 bugs left
- Earliest estimate is the end of this week
- dmose notes that we are statically linking libstdc++ at the moment.
*1.3.1*
- Done and sitting on the staging server.
- Asa needs to update the release notes and do an announcement.
- Done by the end of today.
- Contains Mac XPI fixes.
*Mozilla Firebird 0.6*
- It's been ready for ages
- Definitely better than 0.5
- David Tenser is busy doing the documentation for the release
- Likely to happen in the next week or so
*1.5 onwards*
- Branching for 1.4 in 3 weeks, and opening the trunk for 1.5
development.
- Brendan's roadmap is perhaps looking optimistic for a complete
transition to standalone in 1.5
- There's an issue over build resources.
- Sometime during 1.5 alpha cycle, we do the procedural stuff to get
Firebird and Thunderbird into the public view - tree rules, tinderbox,
nightlies etc. So 1.5alpha is a Firebird/Thunderbird-based release.
- Do we gain anything from the continued existence of the app-suite?
- Firebird will never have feature parity within itself, because that
would be a bug - extensions are the key
- 1.5 should be as good as 1.4
- 1.5 finish date is therefore flexible; it depends how fast we move.
- Try and be feature rather than date driven for that release.
- Composer/Chatzilla is not an immediate priority for early 1.5
- Need to get Browser and Mail in a good state first
- They will probably start as extensions rather than standalone apps.
- Glazman is interested in maintaining Composer - excellent
Gerv
Christian Biesinger
> Present: Marcia, Myk, Asa, Scott, Dan, Chris and Gerv.
Out of curiousity, is Dan=leaf or dmose?
Boris Zbarsky
> - Sometime during 1.5 alpha cycle, we do the procedural stuff to get
> Firebird and Thunderbird into the public view - tree rules, tinderbox,
> nightlies etc. So 1.5alpha is a Firebird/Thunderbird-based release.
>
> - Do we gain anything from the continued existence of the app-suite?
Well... if at the same time as all this is going on we also have heavy
back-end work, it would be good if DOM Inspector continued to function
through the transition. Not in a "ships with the default builds" way,
necessarily, but in a "I can build a Gecko-based application with my
changes and DOM Inspector so I can debug problems" way.....
Sorry to keep harping on this,
Boris
us...@domain.invalid
>
> - Branching for 1.4 in 3 weeks, and opening the trunk for 1.5
> development.
> - Brendan's roadmap is perhaps looking optimistic for a complete
> transition to standalone in 1.5
> - There's an issue over build resources.
>
> - Sometime during 1.5 alpha cycle, we do the procedural stuff to get
> Firebird and Thunderbird into the public view - tree rules, tinderbox,
> nightlies etc. So 1.5alpha is a Firebird/Thunderbird-based release.
>
Since this is a major change why not target a 2.0 version number?
I'm just a user (of builds :-)) but when something this big changes
I would expect a new major version number ...
Just my 2$cents...
Christopher Blizzard
Henrik Gemal
According to the branding doc it's called Mozilla Firebird and Mozilla
Thunderbird. Please remember to the next time, so that we can avoid
confusing...
I think it's important that the Mozilla people are consistent with this
so that the rest of the community will start using this term as well.
> - Do we gain anything from the continued existence of the app-suite?
>
> - Firebird will never have feature parity within itself, because that
> would be a bug - extensions are the key
> - 1.5 should be as good as 1.4
> - 1.5 finish date is therefore flexible; it depends how fast we move.
> - Try and be feature rather than date driven for that release.
>
> - Composer/Chatzilla is not an immediate priority for early 1.5
> - Need to get Browser and Mail in a good state first
> - They will probably start as extensions rather than standalone apps.
> - Glazman is interested in maintaining Composer - excellent
>
--
Henrik Gemal
Mozilla Evangelist
Mozilla Blog with news, devinfo, links, etc:
http://gemal.dk
Michael Lefevre
this has been asked before - see
http://www.mozillazine.org/forums/viewtopic.php?p=66260#66260 for an
answer I gave (which links to an answer from one of the Mozilla.org folks
at http://groups.google.com/groups?selm=3E9215AA.3070300%40meer.net )
--
Michael
Christian Biesinger
> Christian, it's probably Dan Veditz.
Seems unlikely, dveditz is no staff member according to:
http://www.mozilla.org/about/stafflist.html#Staff-Members
Grey Hodge / jesus X
I vote for glazou!
--
jesus X [ Booze-fueled paragon of pointless cruelty and wanton sadism. ]
email [ jesus_x @ mozillanews.org ]
web [ http://www.mozillanews.org ]
insult [ As usual, you've been a real pantload. ]
warning [ Don't touch that! You might mutate your fingers. ]
Michael Lefevre
> On 5/2/2003 11:51 AM Christopher Blizzard cranked up the brainbox and said:
>> mozil...@yahoo.com wrote:
>>> Christian Biesinger wrote:
>>>> Gervase Markham wrote:
>>>>> Present: Marcia, Myk, Asa, Scott, Dan, Chris and Gerv.
>>>> Out of curiousity, is Dan=leaf or dmose?
>>> Christian, it's probably Dan Veditz.
>> No, it's dmose.
>
> I vote for glazou!
ahem... seems like it might be a good idea to use full names (or userids
or something unique) in the published versions of these minutes.
and as has been pointed out elsewhere, would also be a good idea for the
minutes to follow the rules of the new branding strategy in the published
version...
--
Michael
Asa Dotzler
DOM Inspector should work with the Mozilla Firebird browser, Venkman too.
--Asa
Gervase Markham
>> Present: Marcia, Myk, Asa, Scott, Dan, Chris and Gerv.
>
> Out of curiousity, is Dan=leaf or dmose?
dmose. I must start using handles; they are, at least, unambiguous.
Gerv