Thunderbird/StatusMeetings/2008-11-04

last meeting | index | next week »

Thunderbird Meeting Details

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

Agenda

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

Calls For Help

• davida would appreciate assistance on the autoconfiguration branch. (The awesome create-a-new-account screen where you just enter your e-mail address and it figures out most/all of the details for you.) One particular area that could use assistance is handling certificates in the connection detection logic.

Action Items

Open

• dmose: drive JS-in-mail discussion
• davida: will escalate issue of separate messaging crash-stats server
  • Crash-stats is looking reasonable at the moment. Do we still want to do this?
• davida: needs to identify the major work items for thunderbird 3 and break them down by the beta/release they will be in.
• From the Alpha 3 post-mortem (individuals should take your own items and go through them):
  • sipaq: Document details on what should happen before, during and after the string freeze, and the effects on developers at the relevant times.
  • wsmwk: Put up tracking bug for issues from releases during litmus tests.
  • wsmwk: Need to define what tests (e.g. smoketests/basic functional/unit tests etc) should go where and where they are filed.
  • standard8: Generate some gristmill example scripts, and encourage others to use gristmill and file bugs to help improve it.
  • tb-drivers: Go through current MailNews/TB relnote bugs and work out what is really necessary.

Thunderbird 3 Beta 1

• bienvenu is release driver
• gozer is build engineer
• Proposed String freeze date: 2008-11-13
• Code Freeze date: 2008-11-18

• davida will identify the must-absolutely-have items for beta 1 (part of the new action item planning what must happen by when)
  • Proposed intermediate target (to prevent everything either landing at the end or missing) for major items: Friday, October 31
    • Gloda
      • Definitely land with the pref turning it off for Friday
      • dmose progressing reviews.
    • AutoConfig
      • Definitely land as an additional menu item, not yet replacing account wizard
      • depends on how much time bienvenu has as to if this will make it or not.
    • Kill-RDF
      • SeaMonkey note: need to land ASAP as it may cause problems
      • Currently going through reviews. May or may not make it by the date.
    • Cross-folder views
      • Currently going through reviews, should make it.
• pre-release testday(s)
  • purpose: solidify functionality & stability for big features/changes
  • testday 1 - pre-freeze - if wanted on Friday Nov 7, and want publicity via about:mozilla, then need good info by Oct 30
  • testday 2 wanted during bake time / post-freeze, but before release candidate is available? For example ~ Nov 20 (code freeze target is Nov 18). (And might help draw draw more people to QA b1.)

Thunderbird 3

• Draft Thunderbird:Thunderbird3:DevRoadmap identifies major work items on the plate for Tb3 -- much of it needs scheduling, owning, breakdown.
  • folks interested in helping with front-end stuff, some simple, should ask in #maildev

QA Updates

• crash stats

Roundtable

Status Updates

nth10sd

• "Old" bug queries, with MailNews and Calendar added, at testday focus -- only 30 TB UNCO non-enh bugs have no comments before TB2 release date.
• The number was >2,200 when bugdays first started 7.5 months ago, end-March 2008.

Standard8

• Reviews
• Tidied up bloat test documentation and patches (bug 428398), in preparation for moving the bloat boxes to tinderbox
• Fake servers now have debug for received/sent commands
• Filed some calendar bugs (bug 462304, bug 462305, bug 462306, bug 462317)
• Tested calendar with respect to leak, filed bug 462326
• Played around with doing a harness for startup performance tests (this will help assessment of TB + Lightning, bug 462280
• bug 462835 Rename address collector in preparation for work on improving address collector (first step will be so it checks across multiple directories).