Desktop Team Meeting August 21st, 2007

Agenda

• Preview (15 min): We need to close on ZBR. See my email on the dev list yesterday night. Comments on that strategy? Alternatives? Risk/Mitigating actions we could take?
  • Testing the RC: Aparna to talk to us about how that'll happen. We'd like to have the whole team involved here so that we can expedite the process and make it more thorough.
  • Policies on dot release numbering: If we do a quick fix with just a couple of scary bug fixes, should we name it 0.7.0.1 or 0.7.1? There're pros and cons for a longer scheme so I'd like to hear from you on this.
• 0.7.1 (15 min)
  • Some people are starting on their 0.7.1 bugs and adding patches as attachments to Bugzilla. We need to branch (declare ZBR) fast so that we can reopen the trunk and get those in and build/test. I'm concerned about waiting too long and having a deluge of changes with a red tree and having a hard time to track what causes what (we've been there before...). Questions / comments on that?
• Calconnect and interop (5 min): This will be happening in September. We won't have a Desktop representative there but we need to stay involved with the testing remotely. It's important to track Apple interop testing especially. Ideally, we do some tests before hand so that we can send questions/concerns to Apple engineers along with Mikeal who'll be there with them.
• SoC and intern update (5 min):
• Misc : (5 min)
  • Sprint week and celebration: Week of Sept 24th to 28th, make your travel plan if you're remote.
  • Have something to announce? Issues to bring to the group? Please take the stage, er, mic.

Minutes

Preview

• Jeffrey: Are we overstating the index problems? May be those index issues are on the periphery of the app and not that critical.
• Grant: There's a high regression rate on those problems (solving one solves a lot of them). Andre though has been in no pain finding new ones almost every day...
• Morgen: May be we should also have a menu item to clean the indexes (the same as we have at start up). The problem is that it blocks Chandler and it's sometimes too late, once the app is running, to clean the indexes. Better do that on launch (as we offer today in the Ctrl dialog).
• John: Can we run check regularly and automatically? May be at the time of compacting (every week). Interesting idea, Philippe to log a bug on this (Bug#10588).
• John: We should have long duration, stress tests (running over days, syncing and making regular checks for instance).
• All: Releasing an RC with the code as is today doesn't seem too risky, good level of confidence that despite the recently found bugs, the app is globally stable.

Testing the RC

• Run through the acceptance tests. Those are 33 rather complex integration tests scenarios.
• Usually takes a week to go through it for the QA team. Having help from devs will help a lot.
• QA also would like to go through all the recently fixed bugs. Make sure we don't have regressions.
• We can help running these scenarios, especially the critical new features (like Edit/Update).
• Aparna to send an email on how we can help.

Policies on dot release numbering

• Katie, Aparna: prefers the 0.7.0.x numbering
• Stearns: could be confusing for users but no veto
• Grant, Stearns: move 0.7.1 to 0.8 and use 0.7.x for patches
• Reid: move the current load of 72 bugs to "0.7.5" and use the 4 intermediate numbers between now and then (which is not too far anyhow)
• Consensus: none really but no one ready to have a religious battle over it. Philippe to drive to a conclusion on the list.

0.7.1

• No one feels the pressure to branch too early. Easier to make sure Preview is out in a stable way.

Calconnect and interop

• Jeffrey will be working on this. Hard to test Apple server in advance though...
• Morgen also will be participating remotely to the testing sessions

SoC and interns

• All our in house interns gone, that's really the end of the summer
• Thursday at staff meeting: SoC presentations and demos

Sprint week and celebration

• BKirsch may not be able to do it
• PJE still ok for the moment

Status

Andi

• http://kumu.osafoundation.org/~vajda/logs.cgi

Brian (bkirsch)

• Your status here...

Bryan (stearns)

• Investigating bugs as they come up
• Started looking into script recording and playback

Grant

• Your status here...

Jeffrey

• Your status here...

John

• Finished my bugs for the Preview release.
• Took a break after working hard to finish my release tasks
• Reviewed my tasks for 0.7.1
• Worked on search for 0.7.1
• Narrowed down an assert Morgen and Reid were seeing in my code. Concluded it should not affect the Preview release. I still need to follow up on a fix with Jeffrey after Preview.
• Fixed bug#9442: Recorded script quick entry creation of an item with apostrophe.

• Spent way to much time trying to upgrade my ubuntu machine. Finally decided to give up.
• Have fix for bug #8772: Recorded script recTestKeepOutOfDashboard fails
• Spent a bunch of time working on bug #8953: Script recording Attribute error dragging a recurring event lozenge which turned out to be much more difficult that I thought
• Have a fix for bug #9758: Script recording - unable to name an event on creation
• Spent a bunch of time on fixing editing of calendar event in the Calendar, but don't yet have a fix.
• Worked on review comments for Chandler movies.

Morgen

• Your status here...

Philippe (pbossut)

• On PTO last week
• In the week before: Preview monitoring including daily Bug Council, bug testing, wiki review and writing

Phillip (PJE)

• Your status here...

Reid

• On vacation last week.
• caught up on mail, svn, etc
• attached a fix for Bug#10371 (which is targetted for 0.7.1)
  • there is code parsing hard-coded strings using time formats that can be localized

Robin

• Fixed Bug#10373: clicking on 'view pending changes' banner raises assertion and freezes chandler on linux
• Investigated Bug#10538 (No longer able to edit lozenge titles) and was not able to reproduce.
• Released wxPython 2.8.4.2. Tried working with the Ubuntu MOTU group to try and get it included with Ubuntu 7.10, but I got no response from them until after their upstream version freeze so now I am looking into getting an exception from the freeze.
• Reviews and other work for the Google Summer of Code projects assigned to wxPython
• I got a new MacBook Pro that I am going to switch to for my "primary" computer, and spent time getting my development environments set up on it for the three platforms as well as installing and configuring various other software.
• Various community support activities via email and IRC.

-- PhilippeBossut - 21 Aug 2007