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.
Thanks
chris h.
Christopher Blizzard wrote:
> This is just a friendly reminder that the tree will be closing on the
> 7th of Febrary for the Mozilla 0.8 release. There should be about three
> days where the tree is closed to anything but low risk checkins. After
> that we'll cut the branch and the release should happen a couple of days
> before that, hopefully by the 12th.
>
> I'm _sure_ that it goes without saying but we would appreciate if if
> people didn't slam the tree right before the 0.8 closing. If you have a
> lot of code that might be somewhat destabilize the tree please consider
> waiting until after the 0.8 branch is cut.
>
> If you know of features that were added since 0.7 or bugs that you know
> will end up in 0.8 please take the time to add release note information!
> We have a tracking bug open for it.
>
> http://bugzilla.mozilla.org/show_bug.cgi?id=67204
>
> Please let [EMAIL PROTECTED] know if you have any questions or comments.
>
> --Chris
>
> --
> ------------
> Christopher Blizzard
> http://people.redhat.com/blizzard/
> ------------
