Preview Countdown Meeting - April 30th, 2007

Agenda

• Milestone review
• Chandler desktop performance update (Philippe)
• Chandler alpha4 support (Jared)
• Cosmo 0.6.1 migration plan (Aparna/Jared)

Notes

• Sheila will send out a Cosmo email re: schedule where we are and when we think we will have a final date
• Metrics on dashboard - move out 2 weeks
• Terms of service - slow but lawyer is still - plan should be resolved today

Desktop performance update

• The Chandler team met on Thursday
• We didn't quite meet our targets on everything
• We will continue working on this - most people
• Collaborative QA session for working on baseline
• Put a new set of data together and have a small group evaluating the end user experience.
• Eventually we will update the performance tests to use this new data.

Alpha4 support

• Some discussion that we don't support Alpha4.
• Migrate Alpha4 users to trunk.
• Suggestion #1: Once we have given a reasonable window for them to migrate we will stop.
• Suggestion #2: We support Alpha4 until we release Preview.
• Email going to the users - let them know what is happening.
• We could recommend a specific checkpoint.
• The group seems to be converging that we need to be prepared to support Alph4 (suggestion #2) until we release Preview. Support doesn't necessarily mean fixing bugs but it means that people can continue to use the server.

Cosmo 0.6.1 migration

• Jared
  • We had assumed we would upgrade osaf.us - option #1
  • Mikeal proposed a 2 server solution - option #2
  • Jared is not comfortable with the 2 server solution - not enough good arguments
  • Issues now revolve around additional resources required
  • Technical issues were discussed on the list
  • The main issue now resolve around the differences in QA effort
  • Setting up servers is more work for Jared
  • Breaks service continuity
• Aparna
  • Impact on QA - more costly to handle QA for 1 server vs 2 server
  • We will cut into our QA time for dogfooding
  • Believes that there might be extra effort in testing 2 server
• Mikeal
  • Leaning towards one server solution
  • Worried about migration of calendar data
• Effort issues with one server
  • Chandler trunk cloud XML over DAV still works after schema migration (Alpha4)
  • CALDAV sharing and interop works after schema migration
  • Cosmo feature to migration schemas will have to be tested
  • Load for service management
• Service requirement - DAV->EIM migration - change the hostname
• We already have done some mini migration tests and didn't run into any big problems
• DAV->EIM migration steps would be different
  • Potential dataloss problems
  • Some of the etags on the server change
  • Some publish steps are different
  • Different for 1 Chandler vs 2 Chandlers
• Important that people understand what the migration steps are - need these written up clearly
• People seem to be converging on 2 server solution based on QA effort and gut check on risk
• DT stamp issue - won't be a problem
• Decision: We are going to use 2 servers
• Morgen
  • When is the proper time to remove support for old style sharing from Chandler
  • Basically we need to support the old-style sharing through Preview
  • Could subscribe to old share - like a CALDAV client but wouldn't support anything but events
  • Want people who pick up new versions of Chandler to use new sharing code
  • Can we make it hard to use the old format - think about ideas for this so people don't get confused - send email to Cosmo list
  • Be nice to clean up a bunch of old code
  • Decision: Leave support in for Preview

Other stuff

• Neee a dogfood ready milestone - ready before Preview
• We can discuss this at the next Chandler meeting
• After 0.6.1 is up but before Preview
• Bigger push to recruit dogfooders

-- SheilaMooney - 30 Apr 2007