Thunderbird/StatusMeetings/2008-04-08
From MozillaWiki
last week | index | next week »
Thunderbird Meeting Details
- Tuesday, April 8, 16:30 UTC (9:30am Pacific, 12:30pm Eastern)
- How to dial-in
Agenda
Action Items
Pending
- nth10sd & wsmWK: Bug day on Thursday 10 April 2008.
- nth10sd will be present for
all threetwo timeslots, probably sessions 2 and 3. - wsmWK will be on for session 1.
- Participation for (previous bug day's) sessions 1 and 2 was quite decent (~4 volunteers) but session 3 was pretty empty.
- Time change to promote session 3.
- Probably publicity would be better to get participation up.
- about:mozilla article up.
- Manpower issues:
- We should think of ways to have more regulars helping out during bugdays.
- The current method is very scalable but beyond the capabilities of just the two of us.
- Currently, wsmWK does most of the publicity to the community, while nth10sd does most of the metrics (results) and numbers behind the scenes.
- Especially if 10+ volunteers appear for a session, we can get swamped helping them out (and leaving little in terms of actual triaging).
- Something to consider for the future as the Thunderbird community rises again.
- Community has been helping each other, some getting canconfirm privileges, hopefully we'll have some regulars that way.
- This heavy process (planning and executing bugdays) takes a huge cycle of energy to get moving initially.
- A lot of work ahead, advertising and publicity, we'll be keeping the momentum up.
- In a couple of months we hope to have a dedicated community in this regard.
- Feel free to ping dmose if help is needed during bugdays.
- nth10sd will be present for
- Triage old bug review queues.
- 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.
- Not exactly an agenda item, more like an ongoing process.
- Feel free to get back to the reviewers within a reasonable timeframe.
- Feed reader progress
- Did talk with Myk, Joey and Callek.
- Great ideas for feeds, thoughts here.
Completed
- Previous bug day (03 April 2008)
- More volunteers helped out this bugday.
- Re-tuning timing of session 3 for the upcoming bugday due to low (no?) turnout on 04-03. Alter session 3 to be one hour later and 3hr span (instead of 2hr)
- Publicity
- about:mozilla / Devnews, QMO, Rumbling Edge, newsgroups
- put up and advertised Thunderbird:Bugdays_Planning
Thunderbird:Thunderbird_3.0a1
- Driving
- Freeze still planned for 2008-04-22, 23:59 PDT.
- Two weeks from today.
- Please nominate bugs (serious usability issues, crashes...)
- Point is to get us back to a releasing mode.
- Moving forward with bug 418551
- Regressions - bug 427614?
- Mark might have a prototype patch up soon for testing memory leak and bloat performance.
- Performance and testing numbers haven't really been looked at though.
- Getting up and running.
- dmose suggests to backing out patch, patch will probably miss Alpha 1, until performance tests are out.
- After patch is backed out, indexes should be rebuilt. (Mork -> SQLite and now we decide to go back to Mork for the moment)
- Or leave it in the tree and try to fix.
- But we don't have the numbers before the landing.
- We should get metrics out first before landing the patch again.
- We need to understand the consequences first
- dmose will back out the patch.
- Freeze still planned for 2008-04-22, 23:59 PDT.
- davida will blog about getting people to nominate bugs for Alpha 1
- We need better infrastructure to know that what we are doing is actually the "right thing".
- Mark is getting some tests up and running MailNews:Performance_Testing.
- Mark has taken a look at mochitests, if anyone is interested.
- If anybody's got spare cycles, they should explore mochitests or increasing test coverage in other areas e.g. unit tests.
- Instead of re-inventing wheels, we should look at Firefox's model.
Roundtable
NOTE: Please update the notes weekly with each person's work done the past week prior to the meeting.
- davida will be in MV from Tuesday night till Friday evening.
- asuth had a blog post about what he's doing
- About extracting useful information from DTrace and try and present that in a useful way
- Anyone who's online can take a look
- Someday we can automate this to get the performance numbers?
- Useful numbers especially with regards to performance.
- Locally in git, but he can put it anywhere, including on Mercurial, for all to use.
- We should put something at hg.mozilla.org
- Since others in MoCo are already starting to use it.
- Great stuff!
- We have to have unit test style testing.
- Long term plan for more test infrastructure.
- Use tests to do low-level folder cache switching stuff.
- The test numbers will tell us how much the patch improves.
- We should have startup numbers and memory numbers at least, and more!
- Worth playing and experimenting with.
- When someone writes code, we should have tests before and after the code lands.
- rick
- Was in MV to meet with the build team and learn about the release engineering process last week.
- Thunderbird 2.0.0.13 on hold due to Firefox 2.0.0.14 fire-drill.
- We'll do a Thunderbird 2.0.0.14 release.
- Will be doing Thunderbird 2.0.0.14 with help from Nick Thomas.
- Attended meetings to discuss the current process.
- Talos are pretty much specialized tests, e.g. loading IMAP folders from local IMAP server.
- We would have to build up our own test infrastructure because the requirement for us (Thunderbird) is different.
- We should know how much Talos is re-write is needed or just a re-configuration needed.
- Some work on Buildbot with Nick. Mozilla is trying to move towards Buildbot -> build process only, which currently is Buildbot -> Tinderbox -> build process.
- Lots of learning about the build schedule.
- Will take a look at a potential timing conflict between 2.0.0.14 and 3.0 Alpha 1.
- dmose
- Mostly driving and community reviews.
- Sort out module owner stuff and sub-module owner stuff.
- Will look at getting more metrics for Bugzilla / Bonsai stuff.
- e.g. More numbers to tell how fast patches are getting reviewed etc.
- clarkbw
- Done and commented on a bunch of bugs last week.
- Address book and search-related work.
- And writing an extension.
- Gary: great work on the extension.
- It's a great idea and spices up Bugzilla emails.
- Noted some known issues. (The extension leaks!)
- clarkbw documented the work taken on writing the extension.
- Ultimately helps the community by showing the development process of writing a Thunderbird extension.
- Standard8
- Google Summer of Code.
- Applications should be in by now.
- 8 interested in doing the Google Contacts extension.
- We will taking in only one of those.
- 63 applicants for all of Mozilla applicants.
- 1 for Vista Search Integration.
- (Post meeting: the other one was Email Volume Graphs)
- Quite good!
- Re: testing front
- We will have something up soon about performance numbers (Post Meeting: MailNews:Performance_Testing)
- Joshua's got a patch for nsIABCard interface bug 413260
- First of few big patches to go in.
- Google Summer of Code.
- emre
- Mostly IMAP protocol and related issues.
- More information coming soon?
- Talking to David Bienvenu about similar issues.
- Learning about Mozilla development codebase and process on the detail level.
- 1 wiki page on that, still in progress.
- nth10sd
- Bugdays preparation and execution every week.
- Wayne does community involvement publicity, Gary more for behind-the-scenes such as results and metrics etc.
- beckley
- davida: Is there a way we could share workload on shared code? (Yes.)
- Helping out in the process of mentoring on Vista Integration in GSoC.
- Penelope would also like the functionality
- Great to have some overlap between goals of Penelope and Thunderbird 3.
- Gerv is the right person to talk to re: GSoC
- dmose: some issues with SQLite to sort out though.
- MoFo has some connections with SQLite to get them to work directly on what is preferred.
- davida: Is there a way we could share workload on shared code? (Yes.)
- davida
- SyncML issues.
- Would we have an extensions on extensions on extensions situation in the future?
- AMO extensions:
- Do we have ways of contacting the extension authors?
- We should find out why some extension authors haven't supported 2.0.
- We are making great progress on weekly bugdays, patch reviews, checkins
- We should have some planning on a larger architectural change such as full-text indexing?
- We need to think longer term.
Attendees
davida (David), emre, dmose (Dan), nth10sd (Gary), rick, asuth (Andrew), clarkbw (Clark), wsmWK (Wayne), beckley (Jeff), Standard8 (Mark)