Preview Countdown Meeting - May 7th 2007

Agenda

• Cosmo 0.6.1 - possible release schedule (Sheila)
• Risks (Katie)

Notes

Cosmo 0.6.1

• Blocker bugs fixed
• Starting the bug validation process now
• There were some bugs that we had targeted as blockers for 0.6.1 but the flags didn't get set properly
• If we have 0 blockers - QA certification process done by Wed
• Valuable to have a set of links to blockers, nominations, bug list that others can easily get to
• After we have the release candidate Jared can put on on chandlerproject.org to test
• Jared: Blocked on getting SSL certificate - SSL UI is broken and KEI is working on it
  • The vendor that we purchase SSL tickets from - the UI is not working
• Plan - announce internally and get people to migrate their data and try it out
• Announcement process
  • Detail write-up explaining to users how to migrate
  • Posted on wiki, blog
  • QA migration document
  • Go out to lists before we blog and update a wiki page
• Open issue from the thread on accounts
  • Have people create new accounts
  • Create accounts for those users - additional work for QA and Jared
  • Jared will drive this issue and do a last call today
• Splash page for hub.chandlerproject.org will have instructions for migration and to create new accounts
• Cosmo landing page
  • Update release number (Pieter)
  • Migration instructions (Priscilla)
  • Release notes for some minor UI changes (Priscilla)
  • Release notes with link to discussion of new sharing protocol - why do we have this as a release? (Priscilla can steal some info from the developer stuff)
  • Open issue on instructions - use Chandler x.y and later - target today's checkpoint
  • Write-ups done by Thursday - Chandler Server

Risks

• What are risks for Preview - what should we be doing now to mitigate the risks
  • Desktop performance - addressed this with the perf period
  • Discussion on design list - read only features and sharing format
  • What are areas of new functionality where we are still getting the details right
  • Interop
• Risks brainstorm
  • Desktop features that landed near feature complete
  • Cosmo detail view and other potential design work
  • QA coverage for edit/update, communication icons
  • Converging QA cycles for both Server 0.7 and Desktop 0.7
  • Performance
  • Interop - importing other ics files and interop with other calendar products
  • Getting Cosmo 0.6.1 into production and getting dogfooders up and using
  • Cosmo 0.7 schedule - 2 weeks behind where we were supposed to be
  • Trademark lawyers search on logo
  • Getting the community up to speed on where the product is - frame the launch announcements (old copy)
  • Cosmo re-branding for UI stuff
• What should we be doing to tackle this
  • Get dogfood feedback
  • Tight testing session

Cosmo detail view

• Most important thing - don't risk necessary for the superfluous
• Not risk the schedule
• There is some value in experimenting on the server side
• Same user seeing different stuff
• The target users are different
• What are the costs of doing the new design
• If the time to develop is the same are the risks the same in either case
• If we don't experiment now - will we have a chance to do it later
• Ted talked to Matthew about the level of developer effort they are about the same
• If we agreed to do the new one and no negotiation on any design aspects, then it would purely be a dev risk
• No time for design discussion without impacting the schedule
• Unresolved translation issues with the desktop design
• We also have unresolved issues with the new design
• The rest of this discussion will continue on the list and we will resolve it by the end of the day

-- SheilaMooney - 07 May 2007