Thunderbird/StatusMeetings/2009-01-27

last meeting | index | next week »

Thunderbird Meeting Details : Cancelled

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

Agenda

• Who's taking minutes? --> rebron
• 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
• Slushy string freeze from: Thursday 29th January 23:59 PST (1.5 weeks)
• Firm string freeze and slushy Code freeze from: Tuesday 3rd February 23:59 PST
• Firm code/string freeze from: Thursday 5th February 23:59 PST
• l10n-mozilla-1.9.1 freeze from: Sunday 8th February 23:59 PST

• Blockers/Wanted
  • TB 3.0b2 - blocking: 33 (-21)
  • TB 3 Needs 5 (0)
  • TB 3.0b2 - wanted: 43 (+3)
• Proposed Blocking
  • Proposed Blockers (b? + milestone): 1 (-4)
• Fixed:
  • TB 3.0b2 - blocking: 44 (+11)
  • TB 3.0b2 - wanted: 21 (+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
• Blockers/Wanted
  • TB 3.0 (all) - blocking: 105
  • TB 3 Needs 5
  • TB 3.0 (all) - wanted: 188
• Proposed Blocking
  • Proposed Blockers (all): 12

• 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

davida

• triage, driving
• worked on activity manager bugs
• recruiting
• planning FOSDEM talk

dmose

• triage, 3.0 driving
• JavaScript-in-messages work

Standard8

Non-goal activities:

• Reviews, triage.
• Fixed calendar bug 474576 - error seen with calendars when using UTC.
• bug 473529 Archives folder doesn't use localized name in L10n builds.
• bug 474969 Dropped the old chrome start page, so that localizers don't need to work out what to set the urls to etc.
• Finally pushed through bug 453599 Shredder release notes menu item should point to a URL explaining that there aren't any.
• bug 474259 Outgoing email addresses get collected even if in OSX address book.

Two week goals (end of week 2):

• Finish driving in Password Manager
  • Fixed regression bug 473715 (LDAP Autocomplete not working).
  • One possible regression affecting Thunderbird & SMTP passwords bug 474115 - discussing with reporter.
  • One more strange regression reported bug 474439 that affects LDAP, investigating.
• Implement send in background
  • Fixed some assertions that were causing trouble with unit tests bug 474774
• Investigate Weave pop-tart system
  • Looked at this last week - easy for prompts, maybe harder for passwords.
• Try and get initial numbers for Ts to see if we can enable jemalloc.

Two week goals (start of week 1):

• Implement send in background and hook up to activity manager.
• Implement about:rights (bug 463367
• Try and get initial numbers for Ts to see if we can enable jemalloc.

KaiRo

• bug 467052 - ported GLOBAL_DEPS work to c-c, will look into over-eagerness to rebuild right now, which was caused by GLOBALS_DEPS, see bug 474732
• bug 475111 and bug 475120 - more build system ports from 1.9.1 to c-c
• The XUL ID check test I'm porting to Firefox in bug 474716 could also be helpful for Thunderbird, but no chrome test harness running there yet.