WeeklyUpdates/2006-07-24

<< previous week | index | next week>>

Meeting Details

• 1:00pm PDT (20:00 GMT)
• Mozilla HQ, 1st floor conference table
• 866-432-7917 (US)
• 334-309-0297 (INTL)
• join irc.mozilla.org #staffmeeting for attendance taking

Agenda

1. Development Updates
2. IT Updates
3. Product Management and Marketing Updates
4. Foundation Updates
5. Roundtable
6. Other Business

Development Updates

FF/TB 1.5.0.5

• An easily reproducible data loss regression in FF 1.5.0.5 was identified Friday. It is bug 344249. This pushed the release date to Wednesday, July 26th. The bug only affects MacOS.
• The bug was fixed very early Sunday morning. Respins for en-US, L10n an updates were completed around mid-day Sunday. Some focused testing was done on Sunday.
• We plan to complete the testing of FF1.5.0.5 by early Tuesday and then staging will occur Tuesday evening in preparation for the Wednesday release.
• TB1.5.0.5 Should be released Thursday, July 27th. There are a few testing steps remaining.

FF 2.0

• Beta2 planned for Early August. Daily triage happening.

TB 2.0

• Code and Release Notes Are Ready For The Alpha Release
• Build Team is starting to have some free cycles to help package up the Alpha.
• Tim's team has volunteered to do a smoketest once we have packaged bits!

Build

• By the end of this week, we should have two more UB-capable build machines, which will ease pain on the cycle time all around, as well as offer UB capabilities to other products that don't currently have it (XULRunner, etc.) Mac coverage on those products may be spotty this week, as we upgrade these machines.

• We've been asked a few times about publishing updates for Firefox Beta 1 RC N -> Beta 1 Release, due to numbers of premature downloads of RC1. The current plan is, minimally, to publish those updates for the Firefox Beta 2 release. There is a chance this upgrade path will be used for some update infrastructure testing pre-Beta 2 release.

• The Build buglist continues to be triaged; if we accidentally close soemthing that is really needed, please re-open with an explanation/clarification.