Thunderbird/StatusMeetings/2009-01-20

last meeting | index | next week »

Thunderbird Meeting Details

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

Agenda

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

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
• Proposed: Slushy string freeze from: Monday 2nd February 23:59 PST (three weeks)
• Proposed: Firm string freeze and slushy Code freeze from: Thursday 5th February 23:59 PST

• Blockers/Wanted
  • TB 3.0b2 - blocking: 60 (-17)
  • TB 3 Needs 6 (0) Note: bug 402573 waiting 1.9.1 approval.
  • TB 3.0b2 - wanted: 42 (+11)
• Proposed Blocking
  • Proposed Blockers (b? + milestone): 7 (-2)
• Fixed:
  • TB 3.0b2 - blocking: 22 (+1)
  • TB 3.0b2 - wanted: 16 (+3)

• We need to drive bugs with large string changes, e.g., archive, auto config, activity manager. Some way of marking bugs needing strings would be useful.
  • Archive patch landed.
  • Activity Manager is awaiting a new patch from Emre.
  • AutoConfig bug 422814.

Thunderbird 3

• Thunderbird:Thunderbird3:DevRoadmap

• time to truly clamp down and ship sooner rather than later, even at the cost of substantial feature cuts
• we need to get everything tracked in bugzilla
• we will now have component drivers so that people actually own keeping subsets of bugs well-triaged
  • dmose to propose component assignments tuesday

• things to file & triage:
  • component drivers: blocking+ / blocking? bugs
  • davida: development roadmap
  • clarkbw: UX bugs from last weeks meeting
  • dmose: message reader bugs, tb3needs bugs

• new triage rules
  • to stay on blocking+ list, a bug must be owned by someone, even if that's (temporarily) the component driver
  • for each triaged bug on the blocking list: owner, target milestone, priority (P1 - P3; will be used to move bugs if milestone added)
  • criteria for blocking+: if this were the last blocker, we would make all of our users wait even longer for the existing changes in order to get the fix for this one?

• 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)
  • how do we want to handle existing wanted+ bugs? (throw them off the list?)
  • when should we target having the first round of filing / triage done? (1 week from Tuesday?)
  • There will be a TB 3 beta 3 (milestone created in bugzilla)

Roundtable

Status Updates

Standard8

Non-goal activities:

Two week goals (start of week 2):

• Finish driving in Password Manager
• Implement send in background
• Investigate Weave pop-tart system
• Try and get initial numbers for Ts to see if we can enable jemalloc.

rebron

Two Week Goal

• Distribution plan.
• Continue work on Support/Help plan.
• Beta 2 work.