Thunderbird/StatusMeetings/2009-04-07

last meeting | index | next week »

Thunderbird Meeting Details :

• Tuesday, Mar 31st, 16: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.

Thunderbird 3 Beta 3

• Planned Freeze Dates ( All dates use time of 23:59 PST )
  • Slushy String freeze date: 2009-04-21 (Tuesday)
  • Slushy Code Freeze date: 2009-04-23 (Thursday)
  • Firm String / Code freeze date: 2009-04-28 (Tuesday)
  • l10n-mozilla-1.9.1 freeze date: 2009-04-30 (Thursday)
  • Target Build Ship date: 2009-05-05 (Tuesday)
• dmose is release driver
• gozer is build engineer

• Blockers/Wanted
  • TB 3.0b3 - blocking 74 (-8)
  • TB 3.0b3 - wanted 20 (-2)
  • b3ux 34 (-2)
• Proposed Blocking
  • Proposed Blockers (b3) 1 (-2)
• Fixed:
  • TB 3.0b3 - blocking 50 (+11)
  • TB 3.0b3 - wanted 14 (+4)

• Five weekly milestones ([m1] - [m5]) have been created to help spread out b3ux feature work across the milestone and avoid lots of hard landings / misses at the end of the cycle.
  • please update status whiteboard with status of your bugs for the next week's milestone by the end of each Thursday, dmose will poke these on Friday

• Bug-owners: please try to find a little time (an hour?) and go through as many bugs as you can and add a few paragraphs about implementation strategy and test plan. This will be helpful for both QA and for convincing people to step up to the plate for new bugs, and the hope is that it will actually be a net win as far as time spent goes, despite requiring the time-investment up-front.

Thunderbird 3

• Thunderbird:Thunderbird3:DevRoadmap
• Blockers
  • blocking-thunderbird3+ 125 (-9)
  • TB 3 Needs: 5 (-2)
• Proposed Blocking
  • Proposed Blockers (all): 11 (-4)

• Please set bugs to assigned status (as well as owner to you) if you want to do them.
• If you have other bugs assigned to you that you don't want to do, please reassign or discuss with drivers.

QA Updates

• Held the last One year of bug day events
  • Result look bad in numbers , maybe one new contributor joined
• Having the first B3 test day this week
  • this depends heavily on what will land
• Working on moving some litmus test to mozmill
• QA contribution from our user base is low
  • Maybe 05-15 people triaging.
  • This needs to increase.
• Still only one description written

Roundtable

Status Updates

nth10sd

• Working on Mozmill.

Standard8

• Reviews and triage
• Proposed revised content policy (bug 374578, bug 466527) to allow us (and extensions) to be able to correctly load remote content into iframes (and/or browser) elements in non-mail tabs.
• bug 455246 Yet more versions of the final patch for card -> contact renames.
• bug 482489 Adding extra information to alerts system so that we can get account information at UI level (and be able to group it errors/warnings in activity manager).
• More work on Mozmill alongside _Tsk_
  • was hoping to get running for content policy changes
  • Andrew has proposed a way for hooking Mozmill tests up, which I think may work for running tests automated.
  • still looking at hooking up to bloat (bug 458352), and trying to sort out issues with current trunk builds. There is one issue remaining that seems to mean we aren't running any tests when running mozmill from the command line. Once that is fixed, already have an idea for clean shutdown, and as a result we should be able to fix bloat tests.
• Looked at hooking activity manager up to status bar
  • Some issues as "loading..." message overrides the last item, e.g. Moved 1 message to x.
• Tracked down two trunk Lk regressions (which were actually caused by mozilla-central) and suggested that they have an automated Lk regression tracker (as they have for Talos).
• Tracked down regression from bug 487202 which causes trunk builds to break (start up, but broken js file), waiting to hear if this is an issue with TB code or not.

Goals for this week:

• Hook up activity manager to the status bar in some form.
• Start looking at password manager alerts.
• Further work on sending mail in background.

KaiRo

• Reworked SeaMonkey test buildbot configs to closely match the Firefox "mozilla2" cionfigs, wrote a custom factory class to be used there, investigated doing it builders as well, found+filed another issue with abstracted builder classes, this all should end in the possibility to use one slave pool per platform for all branches, builds and tests in each of SeaMonkey and Thunderbird configs