r11 - 27 Mar 2007 - 14:29:00 - PhilippeBossutYou are here: OSAF >  Journal Web  >  DevelopmentHome > ApplicationProject > AppsMeeting20050531

Apps meeting 31 May 2005

Agenda

  • Specs
  • Schedule
  • Engineering Issues
  • People
  • Open Mike

Summary

  • Plan : Nail 0.5.03 this week. Make progress on specs.
  • Progress : Few 0.5.03 bugs left. Move to SVN done.
  • Problems : Need to define and set expectation on what we can do for continuous stability.

Actions

  • All : Focus 0.5.03 bugs and tasks
  • Philippe, David : Plan for the interns
  • Code review : Philippe to write a proposal and circulate among ourselves, Lisa, Katie and Heikki

Minutes

Specs

Sheila is back from vacation. Welcome back!

Some iMAP talks last week. See proposal on Wiki. Brian K and Mimi driving. Objective right now is to get something functional without distracting the team from the "Usable Calendar" mission. Brian K thinks he could actually hack an experimental UI in CPIA. May need help from us to do so.

Trash and Deletion : need to schedule a review prior Alec's return. Philippe to act on that. Need to reconcile the need of garbage collection. Invite John to the review.

CPIA docs : Philippe needs to discuss this with John (level of doc we want to provide especially).

Schedule

0.5.03 is still the focus for this week. Lets review the bug list :

  • Donn : done with milestone tasks
  • Alec : done with milestone tasks (and in paternity leave)
  • David : 2750 won't make it. Worked one day on it already. Has something for Windows but does not work on Mac.
  • Jed : 2593 won't make it.
  • John : 2611 won't make it.
  • Bryan : 2878 and 2936 won't make it. Blocked by a crashing bug before commiting the 4 remaining open bugs.

None of those 5 bugs / tasks are major planned features that would warrant sliding the milestone.

Engineering Issues

Demoability / Stability : OSAF needs to keep a version demoable and a demo server. After a lively discussion, it appears that maintaining the daily build in a demoable state would be too much distraction on devs (Demo D for instance did consume a day from almost everyone). It seems that better communication of the expected stability of the various builds is necessary though so that people making demos are not flying blind. Some actions :

  • e-mail Dev list when making a change that is potentially disruptive and may create regressions. We won't run the smoke tests on all platform before such commits but we'll communicate preemptively...
  • Aparna already runs smoke test on the weekly check point build and log bugs. She'll make sure that her assessment and identified regressions (with bug numbers) are communicated more widely.
  • When there's a planned bug demo (like Demo D), whoever is making the demo should talk to Aparna to pick the most appropriate check point build. We may branch for such a demo (as for Demo D).

Notes : we discussed this during the milestone meeting and added the following :

  • Aparna will mark bugs that are regressions with the keyword "regression" in Bugzilla so that we can rapidly check the regression status of the current trunk.
  • We may decide to give a high priority (fix immediately) to severe regressions but we expect this to be the exception rather than the rule.
  • Let's remember that regression are not only annoying for demos but can potentially block other devs or teams (QA for instance if a whole part of the app is unaccessible to normal operation).

Bugathon : We will have a collaborative IRC session on June 8th (after the 0.5.03 milestone). All devs must participate, test and log bugs. Please test an area that is not the one you developed so that we get fresh pairs of eyes on every part of the app.

UI Tweak cycle with Mimi : Mimi would like to be able to review and iterate on some UI nit picky stuff before the bug gets marked fixed. How to do that? On UI heavy tasks, devs can always request Mimi's expert eye when making UI changes. On other bugs, lets stick with the existing Bugzilla workflow (bugs that are fixed can be reopened before getting closed if the UI is not satisfactory). Eventually, we need to make the CPIA UI editable (or show to Mimi how to do it now for those elements that can be edited).

Code Reviews : We agreed it was a great idea some weeks ago (on the back burner because of 0.5.03 focus). Philippe volunteered to write a doc process for this. Please send him your ideas and suggestions.

Move to SVN : Issues with SmartSVN?. Bugs reported by John to the SmartSVN? guys. We certainly need to flesh out the current Wiki page on SVN (tools, tips, basic usage).

Linux boxes : Let's get them in the App team while Chris is too busy with e-mail, etc... so that we can debug the Linux bugs we have.

wxWidgets : wxWidgets 2.6.01 was released yesterday night.

People

Arel (intern) starting next week (June 6th). David to mentor him. Need to define work load this week.


Status

Philippe

  • Spec reviews
  • Track 0.5.03 progress
  • Board Meeting preparation and presentation
  • Recruiting duties (Scooby screening)

John

  • While looking into why cursor keys don't work in tables, I needed to debug wxWidgets, so I decided to work on the MSVC project to build/debug wxWidgets. While I was at it I found another clean bug in wxPython and passed the fix along to David.
  • Bug #2746: odd behavior after clicking on table header and then click on a table cell. Seems to no longer happen. I suspect it was fixed by recent changes to the table.
  • Bug #3078: turned out not to be a bug in CPIA, but rather a logic bug in Morgen's handler. Reassigned to Morgen
  • Bug #3060: Drag and Drop out of a table causes subsequent selection problems. Fixed last week, but Donn reassigned this P1 bug to me, so I marked it fixed.
  • Bug #3066: Exceptions get lost when passing through the C++ layer. Fixed
  • Spent a lot of time trying to figure out why SmartSVN doesn't work on Macintosh and Linux
  • Integrated Robin's suggestions to wxImage code and SWIGed the changes
  • Worked updating the wxWidgets build to include MSVC project, necessary for bug #2611: Keyboard arrow keys don't work in chandler

Jed

  • Finished all but one 5.03 bug
  • Upgraded to svn
  • Installed linux at home because I need a linux environment
  • Discussed accessibility navigation with Mimi and Heiki

David

  • fixed 2-3 bugs for v5.03 milestone
  • identified "true" source of small toolbar images
  • applied even more wxWidgets patches to "internal/wxPython-2.5" CVS tree
  • submitted wxWidgets fix for wxFileConfig crash
  • did some preparation for arrival of Arel, the (wx?) intern
  • suffered through SVN upgrade (and still suffering)
  • for more info, see WxPythonProject

Alec

  • Hold'en baby Holden... smile

Bryan

  • Working on 0.5.03 bugs: stuck on a crashing bug with no good way to debug it; as a result, a few other tasks won't be done for tomorrow.
  • Good conversation last Friday with Jeffrey about recurrence implementation for DV; notes coming when I've finished my 0.5.03 work.

Donn

Closed out my bugs/tasks for the 5.03 release.

Did a lot of Drag and Drop work:

  • Added cursor support to Drag & Drop
  • Completed most of the Item-based Cut & Paste support in Drag & Drop
    • Calendar View now has partial support for Cut & Paste, Drag & Drop
    • Cut and Past of Items is not working on the Mac - wxWidgets bug?
  • Working on Text-based Drag & Drop

Put LaunchChandler unit test on the back burner. Plan to work with Mike to get Tinderbox support.

Did a lot of SVN conversion related work:

  • Updated my ShellScript wiki, made some improvements
  • Struggled for a long time with SmartSVN, reported bugs and did follow up.
  • I'm currently using a combination of the command line and the SmartSVN gui
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r11 < r10 < r9 < r8 < r7 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.