Services/ProdReleasePlan

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

Introduction

This is a proposed Services Release Process. In the spirit of having time based releases, the goal of this process is to have a set interval when server side changes are pushed to production. This is to drive a consistent and predictable flow of changes on the server side. We will start with a weekly push and refine the process as we go.

Sequence of events

• Tuesday - Features going into that week's push are determined at the Services Weekly Meeting. A drop to Test will be made by EOB Tuesday.
• Friday - Test will sign off by EOB
• Monday - Production pushes will be done every Monday in the evening.

Open Questions

These are open questions. Answers will be incorporated into this page and this section can be removed subsequently.

• Who needs to be involved in the Monday night pushes? Someone from Services Ops, dev of the feature, tester of the feature?
• What other technical details should I include here? i.e. Bug components that are eligible for this process?
• Are there bugzilla queries that would be helpful to include here?
• What other requirements does Service Ops have for doing pushes on Monday nights?
• Anything else I've missed? (given I'm new I'm sure there's a bunch)
  • Coordination with client for features that require it
  • How about a push to stage first, giving us a cascaded release that we can, e.g., run CrossWeave against?