Preview Meeting July 2, 2007

Agenda

• Cosmo status check-in (Ted)
• Desktop status check-in (Philippe)
• "Desktop Localizable Strings Freeze" milestone (Philippe)
• Launch plan
• Risks/Issues - I thought it might be worth doing another round of this

Notes

Cosmo

• Cosmo feature freeze
  • Officially reached feature freeze
  • Ted will send an update to the list with the plan going forward from here
  • Already started testing the latest code on qacosmo
  • People have been working on bugs as well.
• Katie: Should we set a milestone when testers can be testing out 0.7 (round trip desktop and server) prior to going out live on the hub.
  • Jared: This hasn't worked in the past because people have had to switch their production collections.
  • Bear: Eventually we will have to switch tinderbox to 0.7. It will expose some bugs.
  • Ted: We need a way to test up to date versions of server and desktop against each other.
  • Bear: Switching tinderboxes - we can point dogfooders to this. We can point Chandler to the tinderbox instances. It currently points to 0.6.1 off qa sharing server.
  • Probably unrealistic for people to do this with their production data.
  • Possible steps
    • Step 1: Manual
    • Step 2: Tinderbox
    • Step 3: ????
  • Do we have data sets that cover enough different use cases
  • When do we want to try and get people to start testing off of qacosmo - step #1
  • Stuff is broken right now
  • Next step is to identify these blockers
  • Bug council should be starting to meet more often - 2-3 times a week
  • Look at full list of P1s.
  • Which bugs block a full manual test?
  • Do we do this in stages? Are identify everything?
  • Next action: Schedule more frequent bug councils
  • Next action: Ask Mikeal to go through the list of bugs and identify blockers
  • Next action: Sheila will send out an email to the Cosmo list crafting the issues
• Katie: Matthew's bug count is very high
  • He has a lot of dashboard bugs
  • He also has a bunch of rebranding items
  • We know this and still have yet to do a bug prioritization and redistribution of some of his items.

Desktop

• No significant developments
• Observation - Bug count is not going down - in the last week
• Need to punt, clean and move things out
• Many bugs logged recently
• Identify the real blockers
• Code dependent documentations need to be identified as blockers
• Next action: Sheila will go through and mark all code dependent bugs a higher priority and get working on next actions
• Some people are kind of loaded with bugs - hard to redistribute because of people away on vacation
• We could give an assessment of time required to fix P1s and P2s
• Next week we can look at punting the P3s from the list

"Desktop Localizable Strings Freeze" milestone

• Milestone suggested by bkirsch
• He will be leading sprints at Europycon
• After that date, people wouldn't be able to modify strings in the code - we would use a localization file
• We won't be adding any new strings
• Is there some work that needs to be done in order to declare this milestone?
• There are a couple of bugs that needs to be fixed in advance. Branding stuff.
  • ie: Welcome note
• Next action: Philippe will help identify the items that need to be fixed before this date
• Milestone set for July 9th right now. No objections to this.

Launch plan

• Not discussing the details in this meeting.
• Read what Ted sent out to the PR list and respond - particularly the Ops team members.

Issues/Risks

What's on everyone mind now that we are in the final stretch of Preview.

• Philippe
  • Stability - many things broken in the app.
  • Still haven't been successful recruiting new dogfooders to help test before Preview.
• Katie
  • End to end testing.
  • Interop - people's ability to migrate stuff in - are there obstacles for people to get started.
  • Make it a personal goal to demo once a week to someone new - outward focus.
  • Have people list out what they are most excited about - what they like best.
  • Easy to get overwhelmed - deadline looming. Need to pull on inner enthusiasm, shift mindset.
• Jared
  • Worried about personal resources and the list of tasks committed to. Release stuff as well as wiki, content. Worried about holding up the launch.
  • Immediately after launch - Ted suggested weekly update - our process might not be able to support this. In particular we need to work out process and personal issues and we will be trying to speed up at the same time.
• Bear
  • Soft launch - need a rapid response team, plan for getting fixes up quickly. How do we prepare so people will know what to do.
  • Feels comfortable that people are paying attention
• Ted
  • Mostly concerned about making the end date - complete Preview end date, not just Cosmo goals.
  • Server issues
  • Launch plan - post preview people working on bug fixes, no new feature work planned.
• Mimi
  • Not really worried but might be concerned about making sure the dashboard working correctly. There are a bunch of weird bugs - stuff popping into NOW, still not working.
  • Getting into a defensive mindset. Need to positive feedback - what we have vs what we don't have.
• Sheila
  • Dogfooders
  • The date and getting to RCs
  • What's happening post-preview - process goals and plan for updates
• Themes emerging....
  • Stability - end-to-end coverage and number of bugs
    • Concerns about getting all the dashboard problems resolved - those we know about now and the integration issues with Cosmo.
  • Launch plan - post-preview updates - talking about process for handling this
  • Dogfooders
    • A few suggestions for next actions already
    • Blog posts about new features
    • Showing the app to others
    • Talk about postives - think about outward focus
  • The date and the current reality

Other

• Mitch sent Katie some dogfooding feedback - he will send this to the list for the desktop
• Cosmo stuff might go to Ted first
• Mitch would like to have someone review Cosmo features with him
• Katie will follow-up with both Ted and Sheila about the right next steps

-- SheilaMooney - 02 Jul 2007