Preview Meeting May 14th, 2007

Agenda

• Milestone update
• Cosmo 0.6.1 status
• Cosmo 0.6.1, desktop and hub coordination issues
• Risks brainstorm (cont'd)
  • Desktop features that landed near feature complete
  • 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 it
  • 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

Notes

Milestone update

• Many of the dates are out of whack.
• Sheila will update the Cosmo 0.6.1 dates for next Monday.
• Need to work with Philippe and Ted to figure out right dates for 0.7.

Cosmo 0.6.1 status

• Spent last week testing since all the blockers were fixed
• Met on Friday and any new problems are not critical for 0.6.1
• Cosmo 0.6.1 is released and we are working on the announcement
• We could send something out to Cosmo dev announcing the release
• Service has been updated and we are currently testing and we will have a service announcement
• Philippe will try migrating his collections over to chandlerhub.org today
• We could consider a QA testing session for this on Wed
• We will have more people internally try this out
• Official announcement will likely be tomorrow but we still need to do some more migration testing

Cosmo, Chandler and Hub coordination

• Aparna sent an email about this
• When we finished QA on Cosmo 0.6.1 we decided we would use the Chandler checkpoint for last Monday
• Fixes were made during the week
• Do we need a new build or should we wait until the following checkpoint for Chandler (today)?
• Releasing Cosmo 0.6.1 without migration testing
• Easier if there was one owner who knows what is going on and can act as uber coordinator
• There is a service component that Jared should be driving - when is the service ready, what is the Chandler we need to use for people to use the service
• Possibly an element for Philippe to figure out what the right desktop checkpoint is
• Sheila coordinates the Preview deliverables
• We haven't really run into this before so it's a new situation
• Not everyone knew about the changes to the Chandler desktop - didn't cross over to PPD or Philippe
• We will use the Chandler checkpoint today
• No known migration blockers - as of this moment
• For next time - identify an owner for the coordination between releases
• We are driving the release to production service ( Cosmo and Hub - need a release manager who is checking in on both projects
• Was the release process followed
• Should have had a release meeting so we have a shared understanding of who the release manager is - Priscilla
• Regular release meetings during this period
• Need to explicitly notify the release manager when there is new information
• Review Cosmo release process
• Any changes for the service side - service checklist?
• Some tension between service and release manager responsibility
• Priscilla will coordinate the next release

Risks discussion and how to mitigate them

• Desktop features that landed near feature complete
  • Worried about big gaps that are going to surprise us at the last minute
  • Read only issue is one example
  • Conflict UI and edit/update
  • No more big features coming in now but there are lots of interactions that we know
  • Mitigation is usage and getting the dogfooders up and running so we can get real usage
  • More QA sessions
  • Going out to more dogfooders
  • Getting some of this stuff tested earlier
  • Main way to address the risk is to get Cosmo 0.6.1 up and we are working on
  • After we get the desktop checkpoint send a message to the users list - recruit dogfooders to test this stuff specifically
  • Target the QA test sessions around these features when the checkpoint is ready
• QA coverage for edit/update and communication status icons
  • Need wider coverage
  • Mitigate the risks by doing above
  • PPD help regularly - resuming the PPD and QA test sessions
• Coverging QA cycles for desktop and server 0.7
  • Planning in advance
  • Shifting around resources
  • Assigning developers to do some QA
  • Take another stab at the dates and schedules to map out Preview
  • How to structure people's time to make it helpful to have them testing
  • IRC testing sessions
  • Assigning parts of the test plans to people - a single thing is more efficient
  • Feature driven session
  • Planning and feature schedule for Cosmo 0.7 0 - look at staging the testing
  • Think about things that only QA can do rather than delegating - ie: writing test plans
• Performance - Desktop and Cosmo
  • Cosmo - next action is hand UI assessment test to identify big areas to look at
  • Desktop - next action is the test session with the uniform data set - organize the session
• Interop
  • Sheila to write-up email and create import/export page
• Cosmo 0.7 schedule
  • 2 weeks behind
  • Mitigate risks - proactively cut more features
  • Proactively planning and prioritization of the features and tasks
  • Plan for a series of small branches that get rolled out after Preview
  • Next action: Ted will work with PPD to look at what is left
• Trademark lawyers search on logo
  • Pieter has the logo and will move forward with the trademark search

-- SheilaMooney - 14 May 2007