IT/Production Acceptance

This document outlines the process to get a new application or website hosted within Mozilla's production infrastructure. The goal is to keep this process as lightweight as possible, while maintaining control, quality and scalability within our systems.

Current Projects

• Labs/Personas
• IT/Production_Acceptance/CAD: Community Take Action Week
• IT/Production_Acceptance/all.html_redesign
• IT/Production_Acceptance/CommunityStore
• IT/Production_Acceptance/Retention
• Download Day
• CRM
• DRM
• Prior Art
• Headrush
• Automated Partner Repacks
• CommunityDesign

Template

Start of project

• Name each of the following:
  • Project sponsor
  • Main IT contact
  • Main WebDev contact
  • Main QA contact
  • Main Security contact
  • Main third party contact (if developed externally)
  • Final application owner/maintainer
• Outline the following:
  • Overall goal of the project
  • Any pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc)
  • Initial timeline
  • External dependencies
  • Dev environment specs
  • Does this project use any plugins or proprietary technology?

Staging Signoff

In order to get an app into staging, the following should be completed:

• Code committed to Mozilla source control and tagged
• Initial architecture review by IT and WebDev
• Plugin/tech review by Evangelism
• Security review must be in-process
• Site must be password protected
• Review timeline to go live
• Review any production requirements so IT can order any new hardware needed

Production Signoff/Launch

• Final WebDev signoff
• Final IT signoff
• Final QA signoff
• Final Security signoff
• Operations documents filled for support & any training complete
• Monitors in place