User:Clarkbw/Release Driving

From MozillaWiki
Jump to: navigation, search

Initial Work

Initial tasks that need to be done at the start of a new release

  • Create a Development Page, like: 3.0b2
    • Create initial 'straw man' dates for freezes and releases
      • Indicate the strength of these dates as you update them with "initial proposal", "strong", "weak", etc.
    • Build out release milestones weeks
      • Create a milestone for every week in release cycle
      • Name milestones b2week1, b2week2, b2week3, etc
      • Plan landing of items (features/bugs) in each week
      • Set status whiteboard of bugs with milestone names
      • Work with Q/A to plan sessions testing milestone one week after it lands

Ongoing Work

Weekly tasks that need to be performed during a release cycle

  • Communicate release decisions from Thunderbird:Driver Meetings
    • Make sure there are notes for each meeting and they are clear
    • Communicate drivers meeting notes to Newsgroup - mozilla.dev.apps.thunderbird
    • Blog major decisions if possible
  • Update dates on development page if necessary
    • Update date strength meter if necessary for the given week
  • Update Development Section on Weekly Status meeting page
    • Include major points that need to be communicated to the group

Pre-Release Work

Tasks that need to be done within the weeks before a release is scheduled

Clone Bugs! Cloning the previous release bug pulls in the old cc list of release workers and saves time

  • Clone a Release Tracking Bug, like: bug 477103 or bug 467363
    • Make the following bugs blockers of the release tracker bug
      • Clone an existing Release Notes Bug, like: bug 477097
      • Clone an existing Start Page Bug, like: bug 477107
      • Clone an existing What's New Bug, like: bug 477110

Post-Release Work

Tasks to be done directly after the release to clean up and setup for the next driver

Retrieved from "https://wiki.mozilla.org/index.php?title=User:Clarkbw/Release_Driving&oldid=128366"