Desktop Team Meeting September 4th, 2007

Agenda

• Preview (15 min): RC4 is holding steady. [[Projects.ChandlerDesktopTestSpecifications ][Test plans] almost completely covered. Please help to complete the rest and stay alert on bugs. As soon as every plan has been completed (and assuming there's no must fix found), we'll be cutting a final and official 0.7.0 Preview. There'll still be some non code items to polish though (all assigned to either Philippe or Katie). Public release date is Sep 10th (next Monday).
• 0.7.1 (15 min): As soon as we branch, we'll be ready to commit changes to the trunk for 0.7.1. There has been a bunch of patches already attached to bugs. It'll be time to commit them. For those other bugs not patched yet, we'll need to review them. For them, that means SWAG them so that we can decided what makes it in this update, considering that we want this update within 4 to 6 weeks.
• Post Preview Desktop Strategy (15 min): Katie will be sending an email shaping the "post Preview" Chandler Desktop strategy soon. One important aspect will be: how do we organize so that we can release more often? This involves how we work with svn (should be all work on branches that we merge carefully in a constantly green trunk?) and how we minimize regression (i.e. need for more and more automation in testing). 15 minutes won't suffice to cover those 2 issues. We'll need discussions on the lists and certainly sessions during the "sprint week" for in person debate. Still, I'd like to hear some first shots/ideas during this meeting.
• Misc : (5 min)
  • Sprint week and celebration: gentle reminder to make your travel plan if you haven't yet.
  • Have something to announce? Issues to bring to the group? Please take the stage, er, mic.

Minutes

We had 2 discussions "all in one" about 2 of the agenda items

SVN Release Management

• Andi: what about code cleaning, refactor and other dev actions not currently captured in bugs?
• Philippe: we have 2 choices basically: a) a dev branch / release branch strategy (with sub plot as to what call "trunk" and what to call "branch"), b) a stable unique trunk and all devs using branches that they merge when ready
• Andi: we haven't had a lot of experience working with branches. Vote for using 0.7.1 as a branch and the trunk being the dev version.
• Grant: Perforce users usually work with branches.
• Andi: consider Git?
• Heikki: thinks we have too many bugs in 0.7.1 to branch. Should wait till we have less bugs to branch. Also reminds everyone that dividing TBoxes between trunk and branches has a cost.
• Gbaillie: in the Twisted project, you can ask to run your branch on TBoxes (so you get the test results on all supported configs).
• Heikki: may be switch to Buildbot? May be Builtbot on the dev branches only? Buy more hardware for TBoxes and/or Buildbots?
• Robin: in wxWidgets, some contributors running Buildbots
• Robin: in wxWidgets project, the wx trunk is the dev release, when the release stabilize, they branch and fix bugs. Devs runs into double development sometimes. Release every 6 months and 1 year.
• Philippe to summarize and put the conversation on dev list

Script Recording

• John: issues with scripting dialog but found some solution for this.
• Verification mechanism needs to be explained or discussed.
• Needs to check with Mikeal and Dan how we'll use this
• Philippe to start a conversation on this on the dev list

Status

Andi

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

Brian (bkirsch)

• Your status here...

Bryan (stearns)

• Your status here...

Grant

• Your status here...

Jeffrey

• Your status here...

John

• Fixed a bunch of problems with recording scripts that include typing returns. This also allows editing titles in events to be finished by typing return or tab
• Went through my RC1 tests on Linux and Windows. Ran into lots of problems on Linux. Also ran into several non-reproducable problems. I logged the bugs that seems the most serious and those that could be reproduced.
• Continued to test and fix problems I found during testing of script recording. I spent quite a bit of time on bugs that occur when typing return in controls, but more bugs remain to be fixed.
• I got a "proof of concept" working for scripting dialogs. This was particularly tricky because it depends on modifications to wxWidgets, a change to the format of recorded scripts, and discovering a new mechanism to refer to widgets in scripts where ther are no blocks involved. I was lucky to find good solutions to all these problems. The new mechanism for refering to widgets should simplify the existing code outside dialogs. This was the only large task on my list, that I felt was at risk for 0.7.1
• I spent more time understanding bug #10652: Linux: index error on empty trash
• Helped test Preview.

Morgen

• Your status here...

Philippe (pbossut)

• Your status here...

Phillip (PJE)

• Your status here...

Reid

• worked through test cases in TriageTestSpec
• investigated Bug#10693 under Linux (Send button not changing to Update on Linux)
• found, reported, and posted a patch for Bug#10769 (select all + delete of recurring events leads to never-dismissing recurrence dialog)

Robin

• Your status here...

-- PhilippeBossut - 04 Sep 2007