Thunderbird/StatusMeetings/2009-08-04

last meeting | index | next meeting »

Thunderbird Meeting Details :

• Tuesday, August 4th, 16: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.

Action Items

Open

• Autoconfig process
  • Webapp currently being tested to fix some initial problems, will open up for broader testing soon, i.e., move the webapp to a place where more people can access it.

Thunderbird 3 Beta 4

• Release Driver: Standard8
• Build Engineer: gozer

• Blockers/Wanted
  • TB 3.0b4 - blocking 79 (-3)
  • b3ux TBD
• Proposed Blocking (all milestones)
  • Proposed Blockers (all): 72 (-7)
• Fixed:
  • TB 3.0b4 - blocking 20 (+13)

• Main things we want to land:
  • gloda (by default)
  • background sending,
  • message headers improvements
  • autoconfig
    • With ispdb
    • locales string
  • autosync space/time policies sorted out.

• This week will see more aggressive cutting down of the blocking and proposed bugs, figuring out what we don't really need for the release
• Proposed Dates (any feedback to Standard8 please):
  • Friday, September 11th is the proposed target for code freeze
  • Tuesday September 22th, is the proposed estimated release day
  • Following with the final string freeze 1 week after release
  • RC1 proposed date Tuesday, November 3rd for code freeze
  • Final release dates will depend on RC1

Thunderbird 3

• Thunderbird:Thunderbird3:DevRoadmap

• Blockers
  • blocking-thunderbird3+ 147 (-2)
  • Chart
  • TB 3 Needs: 11 (+2)
• Proposed Blocking
  • Proposed Blockers (all): 72 (-7)
• Wanted
  • Wanted Thunderbird 3 249

• 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

• Worked on upates for B2 to B3
  • Large amount of users using b3
  • No new spike in crash-stats
• Had a normal bug day.
• Monitoring crash-stat and filling bugs for it.

This week working on :

• Weekly [Thunderbird:QA_Daysevent | with the community] will focus on dumpe tagged bug
• Long term - come up with an overall strategy for upgrade path testing

IT update

• ISPDB Preview moving along
• MozMill tests have been going on comm-1.9.1 and comm-central for a week now
• Thunderbird 3 Beta 3 Uptake

Roundtable

Status Updates

nth10sd

• Working a bit on Mozmill through a No. 8 Typhoon Signal.
• UNCOnfirmed TB bugs now below 2k
• Found regression window for bug 501045
• qawanted bug 503987
• Usual bugdays, b.m.o cleanup, QA

Standard8

• Reviews and driving
• Finished last patch to bug 121647 POP/IMAP server passwords are inappropriately forgotten.
• Fixed some intermittent test failures in test_sendBackground.js bug 495776
• Came across and did some debugging on bug 504552 Default tab show only a message and no other panes.
• Starting to pick up send in background work again.

Next Week:

• Send in background

gozer

Thunderbird supercomputing cluster

• Build
  • Shipped Thunderbird 3 Beta 3 Updates
  • Mozmill running in staging
  • CCNightlyFactory / CCNightlyRepackFactory tested in staging
    • Will remove a lot of custom code
    • Will address lots of l10n build/repacks problems
    • Parallel l10n repacks

• Web
  • ISPDB Preview in progress
    • Small tweaks and bugfixes

• Infrastructure
  • Trying to repurpose the Thunderbird supercomputing cluster
  • Better spam filtering for @mozillamessaging.com e-mail addresses

Tsk

Last week:

• Looked up at ispdb
• Weekly event
• Tested updates

Upcoming week:

• Start launching upgrade testing effort
• Daily maintainance

bwinton

Last week:

• Closed bug 498519.
• Posted a localization patch for bug 498519.
• Posted patches for bug 503436, and bug 507533.
• Added unit tests for bug 465269.
• Posted a screenshot for bug 495478
• Created bug 507386 and bug 508267, both with patches.

This week:

• Try to close bug 495478 and bug 490097.
• Continue working on bug 465269.
• Also work on bug 507533, and bug 503436.
• Start working on bug 248681 if we know what we want it to look like.