services, dev platform and repository meeting 15 Nov 2005

agenda

• intro question
  • What platform(s) do you develop and test on regularly? (by platform I mean windows, linux, mac)
  • Question, problem, or issue for the agenda?
• 0.6 release
• PerformanceProject
• ZeroPointSixDocumentation
• ZeroPointSevenArchitecture
• sprints: functional test sprint, parcel writing sprint

notes

platform? Grant, Andi and Brian are working primarily on mac, occasionally working and testing on the other platforms. Ted is primarily working on linux; Heikki, Katie and PJE on windows. A shared linux box is available for anyone who don't currently have a linux environment. Most people are regularly testing on at least 2 platforms, but few people regularly test on all 3 platforms -- probably rational as long as we have a few people using each platform for primary development. Sheila (as well as Philippe, Mitch, Lisa, etc.) are primarily using the mac for dogfooding the app. Linux is receiving the least attention, mac the most. Formal test coverage (automated tests, acceptance tests) is performed equally on all 3 platforms.

functional test sprint? Although we talked about it at bug council, we're not going to take the focus away from 0.6 bug fixing to do a big push to write more functional tests. We do want put effort into more functional tests (and other automated tests) in general. Heikki pointed out that we have a lower regression rate than other projects he's worked on, which he attributes to the amount of automated testing we do have. Others pointed out that our test coverage is still pretty weak, and we had general agreement that it is worth pushing for more test coverage. We'll organize a sprint to do functional tests after 0.6 (or at least after code freeze).

epydoc? We had an objective to write epydoc for all public apis. As we don't currently have clarity on what are the public apis, this is probably not a reasonable objective for 0.6. We're going to focus on making sure we have epydoc for at least apis used by the tutorials. Any useful epydoc is welcome, of course. We still have a few outstanding problems (tracked as bugs) with the epydoc generation.

updated specs? Before 0.6 is over, specs written at the beginning of the release should be updated to match the release. You should have bugs logged against you for this (see ZeroPointSixDocumentation).

status

Katie

• Progress
  • Bug:2222 (moved the test menu refactoring to Bug:4617)
  • bug council activities, including scrubbing some perf bugs
  • added perf tests (Bug:4631, Bug:4619)
  • started working on architecture doc
• Plan
  • architecture doc for 0.6
  • bug council
  • follow up on schema/content model question that came up in recurrence review
  • 0.7 planning -- extensibility and content model

Brian K

• Progress
  • Tackled windows i18n Bug:4383
  • Researched i18n resource structure in Visual C++ and work on Bug:4450
  • Created unit test for Amazon i18n Bug:4594
  • Worked on Bug:4447
• Plan
  • Work on Bug:3957
  • Work on Bug:4674
  • Incorporate Heikki suggestions in to Amazon i18n unit test Bug:4594
  • Documentation and Zoabao i18n unit test as time permits

Morgen

• Progress
  • Bug:3272 Subscribe to Collection... does not reprompt for username...
  • Bug:4034 Allow non-overlapping changes within an item to be merged...
  • Bug:4294 set DAV:displayname property when creating dav resources
  • Bug:4418 Corrections to an incorrect username/password during subs...
  • Bug:4533 Can't re-obtain the sharing tickets after restoring shares
  • Bug:4572 The "Collection > Sync" menu item should not change depen...
  • Bug:4574 Manage Share dialog is confusing
  • Bug:4581 Move to Trash/dragging an event to Trash from an imported...
  • Bug:4633 Progress bar when restoring shares
  • Bug:4647 Not Authorized message when subscribing to a collection f...
  • Bug:4651 Synching changes to a shared calendar on cosmo-demo throw...
  • Bug:4654 Filtering: making a share's filter more restrictive doesn...
  • Bug:4678 Move "Restore shares" menu item from Test to Collection
• Plan
  • Bug:2218 Localhost sharing unit test
  • Bug:4525 Sharing performance test case

Lisa

• Progress
  • IETF meetings: Chaired IMAPEXT, CALSIFY, XML-Patch-Ops BOF.
  • Attended: Apps area general meeting, internationalized email, DKIM, Lemonade x 2, Sieve, Pesci, HTTP-Auth bar BOF
  • CalDAV draft "debugging" session with Bernard
  • New draft of vision document in HTML format: http://ietf.webdav.org/users/lisa/chandler-vision
  • Read Sieve Notify draft, Chris' message event draft, all the Internationalized Email drafts
• Plans
  • Plan for When 2.0
  • More hiring work/follow-through
  • More Chandler dogfooding
  • Publish revised version of RFC2518bis draft?
  • Close last-call on LISTEXT draft in IMAPEXT working group
  • Follow up on call for volunteers sent to WAC

Grant

• Progress
  • Ongoing reviews of other devs' patches.
  • Reviewed & committed:
    • 4169 clicking on python/app icon osx dock bar should open chandler window and bring it to the foreground
    • 4533 Can't re-obtain the sharing tickets after restoring shares
    • 4294 set DAV:displayname property when creating dav resources
  • Performance:
    • 4579 (restarting Chandler hangs for 1-2 seconds between module imports): Tracked the actual cause of the problem to a problem with twisted (4376), that BrianKirsch patched. There are still noticeable dynamic linking issues on the Mac, especially on slower machines; I'll be looking at these further this week.
    • 4275 (minical rendering performance): Change reviewed and checked in. Green boxes in tinderbox performance output observed.
    • 4118/4119 (Event creation performance): I have a somewhat gross fix that leverages AlecFlett's hints mechanism.

• Plan
  • Continue work on 3052/4579 (Mac linker performance)
  • Follow up on 4118/4119.
  • Other 0.6 performance work, as well as bug fixes and documentation.

Ted

• Progress
  • Bug:4394 and Bug:4582 triaged to 0.7
  • Investigated adding changed attribute information to notifications for John Bug:3079 - decided to defer to 0.7 due to Bug:4653
  • More community plan stuff
  • 1st draft of repo type document Bug:4028
  • Non Code deliverables meeting
• Plan
  • Docs
  • community plan
  • 0.6 landing page tasks Bug:4335

PJE

• Progress
  • Windows DLL rebasing research and writeup
  • Misc. assists, performance research
  • began review of schema API docs, prep outline for rewrite
  • Some work on Bug:4661
• Plan
  • schema API doc rewrite

Heikki

• Progress
  • Bug council triages - down to about 20 blockers
  • Profiling, found some minor issues in minicalendar
  • Maintenance work on perf test reporting
  • Bunch of code reviews
• Plans
  • More bug council work, perf work