2003-08-25 - Summary of mozilla.org staff meeting
Gervase Markham
-------------------------------------------------
Present: blizzard, chofmann, asa, mitchell, myk, brendan, scc.
*Foundation Update*
The first batch of servers have been moved over to the colo space.
*Releases*
Work to be done to get 1.5 beta out. We had late-breaking security
holes we had to patch. They're all in or in the late stages of being
fixed. Unless we find something today that needs to be added to the
list, we could ship tomorrow's builds as beta.
1.4.1 could come out in the next week or so. Not intended to be a
high-profile release, but part of the long-lived 1.4 branch and
something better to get out while 1.5 final isn't ready.
Asa will be syncing up with Chris on release plans so he can spend more
time with QA.
mscott wants to do a 0.2, so he's going to be doing something around
1.5beta. Mozilla Firebird is going to ship something off the 1.5
branch. By necessity they're going to sync up with 1.5 because they
have some fixing of regressions to do.
1.5 things have taken longer than they usually do, partially because Asa
hasn't been focused on it and took a few days off for health stuff, but
Asa doesn't think it was lack of engineering resources that caused the
delay.
Builds are on auto-pilot, but granrose helps out when they break. leaf
is on sabbatical.
Myk
Robert Pollak
> 1.4.1 could come out in the next week or so.
A significant part of the work to be done for 1.4.1 is to take all
accessibility patches from the trunk.
Sun wants to have this, see
<http://bugzilla.mozilla.org/show_bug.cgi?id=207171#c12>.
Some numbers:
8 bugs are currently blocking 1.4.1 [1],
14 bugs are candidates for blocking 1.4.x [2].
26 patches are waiting for 1.4.x approval [2].
--Robert
[1] keyword "fixed1.4.1" and flag "blocking1.4.x+"
[2] http://bugzilla.mozilla.org/request.cgi
Robert Pollak
[1] keyword does not contain "fixed1.4.1", flag "blocking1.4.x+" is set.
--Robert, trying to translate
<http://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&keywords=fixed1.4.1&chfieldto=Now&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking1.4.x%2B>
Andrew Schultz
> Some numbers:
> 8 bugs are currently blocking 1.4.1 [1],
> 14 bugs are candidates for blocking 1.4.x [2].
> 26 patches are waiting for 1.4.x approval [2].
>
> --Robert
>
>
> [1] keyword "fixed1.4.1" and flag "blocking1.4.x+"
"fixed1.4.1" bugs do not block 1.4.1, they're already fixed on the 1.4 branch.
there are 3 bugs with the blocking flag set and without fixed1.4.1 keyword.
--
------------------------------------------------------------------
Andrew Schultz | The views expressed might
ajsc...@eos.ncsu.edu | not represent those of NCSU.
http://www4.ncsu.edu/~ajschult/ | They are however, correct.
Michael Lefevre
> Robert Pollak wrote:
>> Some numbers:
>> 8 bugs are currently blocking 1.4.1 [1],
>> 14 bugs are candidates for blocking 1.4.x [2].
>> 26 patches are waiting for 1.4.x approval [2].
>>
>> --Robert
>>
>>
>> [1] keyword "fixed1.4.1" and flag "blocking1.4.x+"
>
> "fixed1.4.1" bugs do not block 1.4.1, they're already fixed on the 1.4 branch.
Yes - Robert corrected that in a followup post, what he queried for was
the flag and _not_ the fixed keyword.
> there are 3 bugs with the blocking flag set and without fixed1.4.1 keyword.
No, there are 8 as he said (and as the query URL he posted in the followup
shows). The other 5 are marked "FIXED", but they appear to be fixed only
on the trunk, not on the branch.
--
Michael