Chris Hofmann wrote:
> Just to add a bit..
>
> We currently have a pretty big bug list open
>
> non targeted nominations for mozilla0.8 : 37 bugs found.
> scheduled for mozilla0.8 : 322 bugs found.
> fixed/not verified in mozilla0.8 : 148 bugs found.
> fixed/verified in mozilla0.8 : 135 bugs found.
>
> Now is the time to start to triage bugs and move non-critical
> bugs off the M0.8 list so we can, read the bug list and
> get some real visibility into the most critical fixes that
> need to go into m0.8 to make it a good testing and evaluation
> check point.
>
> It would be great if we could bounce off zarro bugs right around
> the Feb. 6th tree close. That helps is to see the key problems
> and get the tree opened up as quick as possible.
>
> The target is to try and create a m0.8 branch late Thursday
> or Friday and get the trunk back open. We can only do this
> with a set of stable builds and a good understanding of the bug list.
>
Could somebody nominate the following Mac only bugs so that they at least are
entered in rel notes? None of them has target milestone yet, but every one of
them severely affects usability.
http://bugzilla.mozilla.org/show_bug.cgi?id=57083
http://bugzilla.mozilla.org/show_bug.cgi?id=57762 (nsbeta1- but it deserves rel
note, because it is not easy to workaround without info)
http://bugzilla.mozilla.org/show_bug.cgi?id=58721
http://bugzilla.mozilla.org/show_bug.cgi?id=66508
http://bugzilla.mozilla.org/show_bug.cgi?id=66526
http://bugzilla.mozilla.org/show_bug.cgi?id=66527
http://bugzilla.mozilla.org/show_bug.cgi?id=67268
If the current trend continues, Moz 0.8 for Mac can only be based on 20001222
build, which has an unstability issue because fixes for bugs 58728 and 62643
landed later.
Thanks.
Masakazu Hirata
