Thunderbird/StatusMeetings/2008-04-01

last week | index | next week »

Thunderbird Meeting Details

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

Agenda

Action Items

Pending

• nth10sd & wsmWK: Bug day on Thursday 03 April 2008.
  • nth10sd will be present for all three two timeslots, probably Asian and American timeslot.
  • wsmWK will be on for the American timeslot.
  • draft results

• Triage old bug review queues (Update: still ongoing)
  • Feel free to get back to the reviewers within a reasonable timeframe
    • A day or two is reasonable
    • Some reviewers may not have read the bugmail regarding the review request.
  • Ping the reviewer on IRC, or send a personal email

• Feed reader progress (Update: dmose will see to it and clarify)
  • No updates
  • dmose will ping myk
  • No idea if Callek pinged either

• Two folks looking to submit patches for Tb? RSS? - not sure of topic

Completed

• Previous bug day
  • Great for a start!
  • Low turnout though.
  • We should learn from Calendar wiki pages.
  • We need more publicity.
    • Having a schedule with more PR is good.
    • Reach out to people who already do QA for Fx / Tb / Cal.
    • Helpful to keep track of progress of numbers of volunteers and bug counts.

Thunderbird:Thunderbird_3.0a1

• Driving
  • Code freeze still set for Tuesday 2008-04-22 2359h PDT.
    • We'll freeze first, then bake for 3-4 days.
    • Especially if a topcrash gets discovered.
  • meeting schedule?
    • Drivers hope to have own weekly driving meetings.

• Should we branch off for Thunderbird 3.0 Alpha 1?
  • We probably won't need to, because
    • Backend is close to frozen.
    • Firefox 3 RCs due at that time period.

• Nomination issues for blocking/wanted-thunderbird3/3.0a1
  • dmose has done up wiki page.
  • dmose will post on newsgroups.

Bug Day

• Improve doc and process
  • advice has been: be more inviting, simple as possible (reduce barriers), attention to first timers, provide "training" before bugday?
  • draft schedule (compare to QMO)
  • solicit feedback from participants
• statistics
  • what items do we want to track/graph over time?
  • Draft Google Spreadsheet
• Which bugs to focus for future bugdays? Next bugday 2008-04-03
• weekly until further notice?
• participation / international
  • issue-dates: session 1 is evening of bugday-1 for PTD/Americas
  • issue-evenings: Americas have no evening session (session 1 starts 11pm PTD) - solutions add session 4 or move session 1 by N hours? (Clint "volunteers I've met and talked to all work on Mozilla after work")
  • need list of why we need intl participation ..
    • to address bugs with intl issues (which are probably not easily testable or of interest to English-speaking participants)
    • broaden the base of participation
    • ...
  • and work at how we get there (some relevant also to non-intl community)
    • made some key contacts before first bugday, and some more since then
    • L10N team. Contacts?
    • Blog periodically ("helped us a lot in Calendar world")

• We should not emphasize on geographical sessions
  • i.e. Asians should *only* attend Asian sessions etc.
  • It's a bug day, after all.
  • wsmWK has reworked the schedule on the wiki to remove any geographical hints.
  • Standard8 had pointed this out on the wiki.

• Google Spreadsheets is good for listing progress throughout the bug days.
  • The table of results is pretty much reusable as well
    • Just replace the relevant dates in the search parameters.
    • Update the actual bug counts on the wiki.

• Another issue about the bug day -> we may have been assuming people know what a "bug day" is.
  • Questions: why it is important, who should help, how someone could go about doing it..
    • wsmWK will work on it.
  • Spreading out into multiple wiki pages can help reduce long wiki pages as well.

• What should be focused on?
  • Test crash / dataloss bugs
  • We want to ship Alpha 1 to get people to use it.
  • Thunderbird litmus cases?
  • Bugdays vs testdays
    • Suggested days are 17 and 24 April, near 22 April (code freeze date)
    • We should focus on crashes / dataloss bugs as mentioned
    • We should not shift back and forth between these two because it's too early stage.
    • Nominations should be done regularly by the regulars, but we would welcome nominations from others as well.
    • Bugdays are for bugs that are to be dealt with on a pretty much long term basis, not very difficult to triage such bugs.

• Sipaq: Blog about bug/testdays
  • Very important for publicity.
  • Increases number of testers by 4-5 times.
  • Should post at mozillaZine as well.
    • We did post at the build forum, but we should extend to support forum as well.

• Shift a session or do we add an evening slot for American folks?
  • nth10sd and wsmWK will sort this out.
  • We should test the waters or we won't know how it will turn out.

Roundtable

• Strategize improved QA environment - what direction(s) should we go? Examples
  • Bug 193873 – Add Mozilla logging to UI.
  • Bug 257942 – need connection / communication Activity Log
  • clarkbw has been cc'ed.

• Should have more QA stuff throughout.
  • Esp. if we were to engage folks who aren't really very technically savvy.
  • "We drive the right solution and not the right bug"
  • We should reduce the level of verbose QA output (debug stuff?) as we enter beta / release candidate stage
    • But fine for Alphas though.
    • And the bugs found from such output are still important.

• Things we're working on, besides the above:
  • nth10sd:
    • Working with Wayne for bug day stuff, general QA, see above notes.
  • emre: bug 410747
    • He knows what's causing it.
    • Also the bug on Thunderbird "hanging" after waking from sleep.
    • Touching on other blockers as well.
  • dmose:
    • Mostly code reviews.
  • clarkbw:
    • Search-related UI developments.
    • Uploading to wiki a bunch of search examples.
    • Will work on search flows, along with the basic UI of improved search.
    • Will include some markups on some of his ideas.
  • asuth:
    • Just got pretty much started.
    • Working on calendar trunk's performance tests.
    • Got DTrace going
    • sipaq: Should interact with some calendar devs.
    • Will do that soon.
  • Standard8
    • Done some reviews, some really big ones.
    • Joshua's patch coming up soon.
    • Address book stuff.
    • Fix up something about mailing lists as well.
    • Looking at bug 424218.
  • rick
    • Part time build engineer.
    • Just arrived in MV.
    • Learning about build processes now.
  • davida
    • Not working on code but would love to.
    • In California next week?
    • Going to Calendar F2F meeting in mid-April.
    • Blogging about Thunderbird and related news.

• Google Summer of Code
  • We are pretty much short on mentor bandwidth.
  • Thus, we aren't likely to have many projects.

• Contractors
  • Any possible folks who want to work as contractors for certain wanted features by companies, please contact davida.
    • For calendar, sipaq as well.
  • (Not a bad problem at all. :) )

• Calendar
  • Status phone meeting tomorrow.
  • Everyone is encouraged to attend to get a heads up on some of their work.
  • sipaq: Mac 0.8 RC2 builds out, real hopeful that RC2 is the final 0.8 release.
  • Started triaging bugs for 0.9 release.
  • No need to remove old flags for resolved bugs, just for old nominations that still float around along with +/-ed unresolved bugs should be mass-renominated.

• Congratulations to Wayne!
  • Nominated as a Friend of the Tree.
  • For his work in getting Thunderbird's first bug day up and running.

Attendees

davida (David), dmose (Dan), emre, clarkbw (Bryan), asuth (Andrew), wsmWK (Wayne), nth10sd (Gary), sipaq (Simon), Standard8 (Mark)