OSAF Weekly Status 07 April 2006
This report covers the period from Apr 1-Apr 7 2006 (one week).
Highlights
- Chandler
- PyLucene,PyICU no longer use SWIG
- Free/Busy, Scheduling are code complete for 0.7alpha2
- Cosmo
- Working on closing out 0.3 release. We have a small number of bugs to fix and the migration tool to finish.
- Scooby
- Work on some of the Scooby 0.2 features is already started.
- Scooby 0.2 officially kicks off on 4/11/06.
- Community/IT
- Wiki updated to new code base.
- More development work on the Scooby and Cosmo landing page sites in preparation for the Scooby 0.1 and Cosmo 0.3 bundle launch.
Design and PM (Sheila)
Progress:
Plans:
Application WG (Philippe)
Summary
- Progress
- Some features are code complete for 0.7alpha2
- Progress on all main features for 0.7alpha2
- Toolbar and multistate button
- Dashboard
- Plan
- The bugs failing functional tests in full build (and therefore wx tarball to roll out) seems to have a solution: expect a bunch of stuff that was blocked to show up next week.
- wxColumnHeader integration (now that the functional test break is fixed)
- Markup toolbar (now that multistate button is in)
- Continue to monitor 0.7alpha2 tasks and bugs count
- Need to make progress resolving the Build Policies issues (meeting this afternoon, Philippe driving)
More details available in
AppsMeeting20060406
Platform WG (Katie)
- Progress
- fixes for sharing and accounts tests
- background sync improvements
- Released setuptools 0.6a11, w/more new docs and many features/fixes
- More Python 2.5 work: enhanced garbage collection for generators, PEP 343 bug fixes, etc.
- Bug fixes for recurrence, reminders, alarms, timezones
- Bug:5209 (Use new smart-naive datetime for all new events)
- PyICU? no longer uses SWIG
- Plans
- domain model bugs (Bug:3531, Bug:1745)
- calendar service and interop bugs
- dump/reload requirements and proposal
- egg i18n proposal
- stabilize setuptools to 0.6b1 for inclusion in Python 2.5 alpha 2
More details available in
PlatformMtg20060404
QA, Build and Release (Heikki/Aparna)
- Progress:
- checkpoint build testing
- bug verification
- automated cosmo 0.3 test development
- chandler 0.7 functional spec review
- Plans:
- chandler 0.7 testplan development
- additional cosmo 0.3 test development and documentation
- revamping QA page to reflect status of all the 3 projects, chandler, cosmo and scooby
- new checkpoint build testing and assistance in debugging functional test failures related to wx39 tarball.
Cosmo and Scooby (John)
Progress:
- Cosmo
- Working on closing out 0.3 release. We have a small number of bugs to fix and the migration tool to finish.
- Work continues on our testing infrastructure.
- Started thinking for next release.
- Scooby
- Scooby 0.2 planning: We have a rough cut at a schedule for the team.
- We have a list of issues that we plan to push out the the Scooby mailing list this week for discussion. (Priscilla is coordinating this)
- Work on some of the Scooby 0.2 features is already started.
- Scooby 0.2 officially kicks off on 4/11/06.
Plans:
- Cosmo
- Get migration tool done this week.
- Fix remaining bugs for 0.3
- Get 0.3 release candidate into QAs hands this week.
- Brainstorm in server meeting on 0.4 plan.
- Scooby
- Finalize the Scooby 0.2 plan.
- Start discussing the design and architecture of Scooby for 0.2
- Write up specs for 0.2.
- Kick off development for 0.2
- Get discussions going on the mailing list for Scooby 0.2 features that need more discussion.
IT (Jared)
Progress:
- Wiki updated to new code base.
- Closed office bandwidth improvement project.
- Closed outbound port 25 to control spam.
- Desktop backups project proceeding; off-site rsync copies tested.
- VPN project proceeding; final configuration of private cert authority.
Plans:
- Close outstanding wiki migration issues.
- Ongoing physical security updates.
Community (Pieter/Ted)
Progress:
- More development work on the Scooby and Cosmo landing page sites in preparation for the Scooby 0.1 and Cosmo 0.3 bundle launch.
Plans:
- Testing of the demo of Scooby process and tweak any UI needs like adding Level-Of-Service statements at appropriate places.