Thunderbird/StatusMeetings/2008-05-06

last week | index | next week »

Thunderbird Meeting Details

• Tuesday, May 6, 16:30 UTC (9:30am Pacific, 12:30pm Eastern)
• How to dial-in

Agenda

Action Items

1. Prepare Thunderbird 3 Alpha 1 release notes for the upcoming release.
   • nth10sd has the next revision out.
   • Everyone: Please comment on how we can improve the release notes (ping davida if you want to see the staging version).
   • davida still has to fill in some bits.
2. We need a code name for non-release TB builds.
   • Discussions in the newsgroup.
     • Currently no clear winner.
   • We have to have the equivalent of Firefox's Minefield/Gran Paradiso combination though.
   • davida post in newsgroup asking for scary names.
   • Lots of work to do to set it up, so this won't be done for Thunderbird 3.0a1.

Thunderbird:Thunderbird_3.0a1

• Code freeze entered on Wednesday, April 23, 23:59 Pacific
• 4 remaining blockers
  • One needs review, one is release notes.
  • The newsgroups one will probably have the patch backed out due to lack of information and understanding.
  • Last one tbd, but may not be a blocker or already fixed.
  • We should be able to clear the blockers today.
• Verbiage is on the Tinderboxen forbidding checkins to mail/ and mailnews/ of non-3.0a1-blocking bugs without explicit approvals. Those directories will remain closed until we've cleared the blocker list (either by fixing or cutting remaining bugs), spun builds, and tagged the release.
  • dmose posted update on current status and expectations to newsgroups
• We're building a release checklist as we go, so that this stuff is written down somewhere, possibly either updating or starting from http://developer.mozilla.org/en/docs/Mozilla_Release_Checklist. http://wiki.mozilla.org/Firefox3/Beta2ReleaseChecklist looks like useful source material as well.
  • nth10sd to add QA activities to release check list
  • Rick to add build activities to release check list
• Once dev is happy with code-base, could use date or tag to "mark" the build.
  • Must keep a clear record written down somewhere.
  • Best to use date or a tag and check-in to trunk and tag any remaining required fixes.
• Not planning on doing automatic updates between alphas
  • Mainly due to QA load.
  • Could use start-page to notify users of new version instead.
  • Rick to check that the correct channel is set so that we won't provide updates to alpha people, but we can later provide updates between betas.
• Release Builds
  • Expect problems, we'll be using buildbot and Firefox didn't do its alphas with the buildbot automation.
  • Rick to talk to MoCo build engineers to find out when the builds are likely

AMO recommended list

We need to identify a recommended list of Tb addons, per category. See bug 425333 for the list of candidates. Any takers to coordinate feedback before I (DavidA) blog about it?

• clarkbw to co-ordinate and summarise community discussion on best add-ons.
• nth10sd has a list in a comment in that bug after a quick glance, though still un-categorized.

(see also the Talk Page)

QA Updates

Bug day results are constantly updated in a spreadsheet. UNCO Graph continues to look good - dropped ~250 bugs in 1.5 months.

Last Bug Day Thursday 1st May 2008

Next Bug Day Thursday 8th May 2008

Test Day

Thunderbird 3 Alpha 1 testday to be decided, once Rick comes up with the Alpha builds.

• We can always change Bug Days to Test Days late in the day if specific items need testing.

Roundtable

Improvement of Start page for future Alphas

• Proposed by Ron K on the previous bugday session.
• bug 430762 filed to track this idea.
• Would be good to have especially if http hosted.

davida:

• Set up a ui-review flag, so that the bugs where UI review is really needed can be flagged up to Bryan.

Standard8:

• Located some memory leak issues bug 431404, bug 431414
• Removed some dead code bug 431415
• Password Manager
  • Started tidying up the SMTP service/url code and related items in preparation to help Password Manager migration (wallet -> toolkit) work.
  • Will need some detailed look at.
• Unit Tests bug 406227
  • 2 out of 5 bugs now fixed.
  • 1 bug has patch that needs extending and test case
  • I have a basic understanding of at least the causes of the failures for the other 2 bugs.
• Want to look at this week:
  • Review policy/Guidelines proposal for tests in mailnews (in co-ordination with dmose?)
  • Get (updated) patches up for all of the remaining unit test bugs
  • Password Manager
  • Possibility for Ts tests

nth10sd:

• Preparation for QA testday in view of Thunderbird 3 Alpha 1, IRC meeting held
  • Bought improved hardware (Memory & disk space) for testing in VMs
  • Also prepared QA wiki pages for the alpha release, formulated QA testplan
• Release notes now done by davida
• Patches for some trivial UI naming issues bug 218500, bug 249620
• Occasional bug triage
  • Testday coming up on Thursday, hopefully we'll have Alpha 1 bits out.