IT/Maintenance/DevServices

Document Status	Last Reviewed
DRAFT	Aug 13 2012

Introduction

Developer Services is a set of project-wide services that support development. Any impact to these services could cause tree closures and as such we limit the window in which we make changes.

The schedule for these windows follows the 6-week release cycle. Emergencies or other external events can postpone a Scheduled Maintenance Window. Mozilla IT will always confirm with Release Coordinators before scheduling work.

Scheduled Maintenance

The schedule mimics the 6-week release cycle.

Week 1	Status
Monday	Merge day
Tuesday	Ship Release
Thursday	Ship Beta
Friday	Aurora enabled

Week 1

• Merge day on Monday
• Release ships on Tuesday
• Beta ships on Thursday
• Aurora enabled on Friday

Week 2

• Usually decide by Wednesday whether to ship a .1 release
• If a .1 release is necessary, typically release by Friday

Week 3

• A .1 is sometimes released as late as Monday (as with the mobile 15.0.1)
• Tuesday onwards should be clear

Week 4 & 5

• Clear

Week 6

• Preferable not to make major changes, as we're chasing down release issues and building a release candidate

Notifications

• Announced by noon (Pacific) one week before planned work
• Reminders sent by noon (Pacific) two days before planned work
• Notification Distribution List:
  • infra-cab@mozilla.com
  • infra-sre@mozilla.com
  • devservices-notifications@mozilla.org
  • dev-planning@lists.mozilla.org
  • release-drivers@mozilla.org

Developer Services

The above policies primarily to, but not limited to, the following services:

• hg.mozilla.org
• svn.mozilla.org
• git.mozilla.org
• bugzilla.mozilla.org