Thunderbird/StatusMeetings/2009-03-10: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 111: Line 111:


===== gozer =====
===== gozer =====
* Build
** Try server (<i>in progress</i>)
** <b>Betatest updates ready for Alpha*/Beta1 => Beta2 {{bug|471584}}</b>
*** Complete updates all around except for 3.0b1 Linux/Mac en-US
*** Learned a lot more about patcher!
*** When/How do we go live with this ?
** Clobberer server! <i>(gozer/Standard8 have access, if you want it too, file a bug)</i>
* Web
** New website got a few performance fixups and tweaks
*** Saw > 2,200,000 hits in the last 24 hours
*** > 80k visits in the last 24 hours
*** > 40k unique visits to the 3.0b2 Start page in the last 96 hours
* Infrastructure
** Buildbot timeouts issues look like they have finally vanished beyond the 'acceptable' horizon
*** {{bug|476677}} & {{bug|476649}}
*** Various fixes, mostly about giving Buildbot more/faster I/O
* <i><small>80% recovered from the sick... better</small></i>


===== clarkbw =====
===== clarkbw =====

Revision as of 15:29, 10 March 2009

last meeting | index | next week »

Thunderbird Meeting Details :

Agenda

Action Items

New

Open

Closed

Thunderbird 3 Beta 3

Thunderbird 3

  • 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.
  • Trying to put together a schedule that will land features every week or two. dmose will be putting a plan together.

QA Updates

  • Testing updates for releases prior to beta2
  • Organized a DUPME bug day -> 10 bugs got changes on the dupme query
  • Will continue with bugdays until we have a better schedule for beta 3.
  • Hope we will be able to update prior releases to beta2 in oreder to figure out what is crashig in beta2.

Marketing Updates

Roundtable

Google Summer of Code

Please add your suggestions to the brainstorming page, doesn't matter if you don't want to be a mentor, ideas are the important part at this stage. Remember it needs to be about an 8-week chunk.

Students start discussing ideas on 18th March, start applying on 23rd March.

Status Updates

davida
dmose
nth10sd
  • bug 326483 - create sample email for test; seems WFM.
    • Won't Save Incoming Mail Attachment if Chinese file name
  • bug 460605 - Initial testing done, waiting on more info.
    • Message Reader: header pane context menu popup takes too long for contacts in long list with lots of addresses
  • Some security bug triage.
  • Bugdays, QA, etc.
Standard8
  • Reviews
  • Bug triage
  • Activity Manager
    • bug 477862 Activity Manager: activity list doesn't clear permanently until restart.
    • bug 482253 Fix Activity Manager's themes so that text can be read when window is not focused, and make it easier for themes to be applied across all activity types.
    • bug 481431 Provide a centralised alert/message service in mailnews to allow different front-end displays for alerts.
    • bug 482466 Hook activity manager into the new alert/error listening mechanism.
  • Misc
    • bug 479844 Consolidate checking for messages to send later into one function.

Two week goals:

  • Reduce review backlog to zero
  • bug 450134 - Autocomplete perf improvement (inc restore autocomplete on other email addresses).
    • Proposed a patch for this, got review comments, need to improve.
  • bug 440794 - Implement policy for sending in background, pref off to begin with.
    • Defferred due to activity manager improvements (and heading towards non-modal alerts).
  • bug 457296 - Design interfaces for a separate service (i.e. not directly linked to address book) to determine allowing remote images to load or not.
    • Initial design for back-end posted.
    • Need to figure out storage mechanism.
    • Have ideas for Pref UI changes.
asuth
bienvenu
gozer
  • Build
    • Try server (in progress)
    • Betatest updates ready for Alpha*/Beta1 => Beta2 bug 471584
      • Complete updates all around except for 3.0b1 Linux/Mac en-US
      • Learned a lot more about patcher!
      • When/How do we go live with this ?
    • Clobberer server! (gozer/Standard8 have access, if you want it too, file a bug)
  • Web
    • New website got a few performance fixups and tweaks
      • Saw > 2,200,000 hits in the last 24 hours
      • > 80k visits in the last 24 hours
      • > 40k unique visits to the 3.0b2 Start page in the last 96 hours
  • Infrastructure
    • Buildbot timeouts issues look like they have finally vanished beyond the 'acceptable' horizon
  • 80% recovered from the sick... better
clarkbw
wsmwk
beckley
Penelope
KaiRo
rkent

My mailnews work has focused recently on three primary activity threads:

  • Bayesian filter feature extensions, including more precise control of application, and use with rss and nntp
    • bug 478840 (landed) Support inherited folder properties
    • bug 481676 (in review) Move bayes listeners to nsMsgDBFolder
    • bug 471833 (next) Provide hooks to control calculation of bayesian filter traits
  • Prevent loss of message database information
    • bug 459680 (partial solution in review) Moves and copies should move all database info
    • bug 340886 (not started) Junk status changes to "unknown" when I delete or separate an attachment
  • Search all address fields capability
    • bug 310359 (parent, partial solution landed) search all address fields capability (Bcc:s too!)
    • bug 381667 (in review) Support BCC in message summary files
    • (unfiled) add BCC to All Messages search
    • (unfiled) support reordering of message search terms
    • (unfiled) support all message search in online IMAP search

I'm largely review limited at the moment, which I expect to get continually worse, so I think I only have another couple of weeks of mailnews patches before I can pretty much kiss further TB3 work goodbye.

rebron
Tsk
  • Done :
    • DUPME event - not satisfied by results
    • Attended MozCamp/Utrecht
      • Met a few interested people
      • Once STEEL's out we should attend Extension Workshop
  • Continuing:
    • QA plan
    • Engaging communities
  • Todo:
    • Try to communicate more effectively
    • explain what and why QA is important - to try to get w few more people onboard
    • Plan tb3.0b3 testing

Attendees