Chandler Engineering Meeting, Thursday February 1st 2007

Present: Heikki, Jared, Sheila, Katie, Ted, Aparna, Bear, Morgen, Philippe

0.7alpha5 Progress

• Recurrence branch landed
• Bugzilla dogfoodable flag: we're reverting the decision, suppress that flag and instead use the "blocker" value in "severity"
• EIM
  • Lots of sharing code is changing: serialization, networking, magic URL
  • Jeffrey working on the translator from recurring event to EIM
  • Brian not blocked on Edit/Update (Morgen delivered the API)
  • PJE working on Conflict Management
  • 2 weeks of work before we are complete on Chandler, then we'll need a good week of testing, then we'll be able to migrate some dogfooders.
  • Biggest risk: Cosmo interop, this will drive the Cosmo 0.6.1 realease, completion of code of this will be called "Integration complete"
  • EIM Migration plan: users will have to manually unpublish from the old URL scheme to the new magic URL(s) scheme
• Dump and Reload: can't be started before EIM/Sharing's done, we don't have a SWAG on that yet. This could be hold off the rest for "feature completion"
• Conflict resolution and Edit/Update: Blocked by the availability of an API from PJE
• Triage status: We had a design session on it this week and simplified the scenarios we'll cover for Preview (Mimi emailed the list with decisions). Should be completed by mid February
• Dashboard on track for mid February completion
• Search: one more cycle of discussion but converging very fast
• Performance: need to have people from Apps working with Andi to make progress

0.7alpha5 Schedule

• At least 5 weeks from Feature Complete (2 weeks for EIM + 1 week of testing + 2 weeks for Dump and Reload)
• That means that our schedule is moving 3 weeks in the future
• When EIM is landed and tested, Cosmo 0.6.1 schedule can be set, the first RC of it will be an "Integration Complete" milestone
• After FC, we'll need a period of 4 weeks for perf work, design tweaks and debug before we can hit Code Complete
• We'll then enter the pure debug phase that will lead to Release Candidate

Cosmo migration testing and privacy concerns

• Need to explain better to users what a migration is all about
• Need to write better Term of service, include provision for admin access
• Develop a script to extract a set of data for testing (though we'll still need to run full migration tests on the whole set from time to time before doing migrations)

QA

• Which version of Chandler do we certify Cosmo 0.6 against? We need to certify alpha4 because it's more stable. We can do some testing with alpha5 though.
• Interop Scenarios: Aparna to send an email to explain how people can help

Other

We decided to have this meeting weekly starting now till Preview.

-- PhilippeBossut - 01 Feb 2007