Thunderbird/StatusMeetings/2009-02-03

last meeting | index | next week »

Thunderbird Meeting Details :

• Tuesday, Feb 03th, 17:30 UTC (9:30am Pacific, 12:30pm Eastern)
• How to dial-in

Agenda

• Who's taking minutes? --> davida
• Minute taking Schedule. Talk to davida for schedule changes/additions.

Action Items

Open

• davida to look at status meeting agenda due to the drivers meeting that follows later in the morning.

Thunderbird 3 Beta 2

• For reference, Gecko 1.9.1b3: Jan 13 Code Freeze, Jan 15 QA, Jan 26 Release according to their plan.

• clarkbw is release driver
• gozer is build engineer
• Slushy string freeze from: Tuesday 10th February 23:59 PST (1 week)
• slushy Code freeze from: Thursday 12th February 23:59 PST
• Firm code/string freeze from: Tuesday 17th February 23:59 PST
• l10n-mozilla-1.9.1 freeze from: Thursday 19th February 23:59 PST

• Blockers/Wanted
  • TB 3.0b2 - blocking: 33 (+1)
  • TB 3 Needs 4 (-1)
  • TB 3.0b2 - wanted: 41 (-2)
• Proposed Blocking
  • Proposed Blockers (b? + milestone): 4 (+3)
• Fixed:
  • TB 3.0b2 - blocking: 52 (+7)
  • TB 3.0b2 - wanted: 22 (+1)

Mark bugs needing strings with status white board — [affects l10n]

• We need to drive bugs with large string changes, e.g., archive, auto config, activity manager
  • Archive patch landed.
  • Activity Manager is awaiting a new patch from Emre.
  • AutoConfig bug 422814.
    • Moved to Thunderbird:Thunderbird 3.0b3 release

Thunderbird 3

• Thunderbird:Thunderbird3:DevRoadmap
• Blockers
  • blocking-thunderbird3+ 117
• Proposed Blocking
  • Proposed Blockers (all): 22

• we now have component drivers so that people actually own keeping subsets of the blocking list well-triaged
• bug list much more believable, thanks to last week's work
• things to file & triage:
  • component drivers: blocking+ / blocking? bugs
  • dmose: message reader bugs

• new triage rules
  • to stay on blocking+ list, a bug must be owned by someone, even if that's (temporarily) the component driver.
    • owned-by-driver bugs should have [needs owner] in status whiteboard

• to think about:
  • when do we branch? (i suspect immediately after b2)
  • when do we lock down the branch for only blocking+ and approved+ (i suspect a couple of weeks after b2)
  • There will be a TB 3 beta 3 (milestone created in bugzilla)