Operations Group Meeting Notes - August 15th 2006

Hiring Discussion

Release Management (Ted)

• Some of the questions raised....
  • What is Marketing's role, how does Pieter get looped in at the right place?
  • What is the build/release team's role? What are the expectations and how do we make sure they are looped in as well?
  • What are the general expectations for transparency of the release process, and how are we doing?
  • Who is the 'release manager', and what are the expectations? How do we make this clear to everyone on the team?

• Ted has raised some concerns
• Do we have enough transparency around the release process?
• Issues at the end of Alpha4 - people not knowing what is going on.
• Who the release manager is - what their responsibilities are?
• Invite Pieter to the bug council
• Tag emails on the dev list to make them easier to see
• There is a release manager - they own decisions - Heikki
• Need to make sure the process is clear and the transition between steps
• Matrix of all the steps in the process - tasks assigned to people
  • You can look at this list and see where we are
  • This gets updated and sent out to the list with updates
• Need a release management handbook
• On the desktop there are regular emails but we are missing some context
• Templates for the release process
• Should unify this across projects

• Next Actions
  • Need to clearly specify release manager for all projects
  • Put together template for steps
  • Philippe and Heikki responsible for Chandler desktop
  • Katie responsible for Cosmo

Sprint/Cosmo

• PPD owns agenda
• For each session we should have facilitator, time keeper, note taker

WWDC follow up

• Check if Grant and/or Jeffrey want to post something
• Mikeal knows about the unit tests - we could use these

Staff Meeting

• No meeting this week
• Sheila will change the Chandler office calendar and notify Esther

Mainstream Intern Work

• Some stuff will get into Beta
• Even stuff that doesn't get into Beta - should we do doing something to make it so people can get at it
• The issue is - stuff that isn't in the distribution doesn't get tested formally. Many of the test parcels break all the time.
• We have looked at this before - contrib area - sandbox that we don't have to maintain
• Decide which ones...
  • We fold into Beta
  • We add to examples - some comittment to maintain them
• Focus on Beta
• Bring stuff in if it's contributing to Beta
• The other reason to bring stuff in that doesn't directly contribute to Beta - there is a group of people committed to maintaining it.

-- SheilaMooney - 15 Aug 2006