IT/Production Acceptance: Difference between revisions
< IT
Jump to navigation
Jump to search
| (15 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
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. | 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 = | = Current Projects = | ||
* [[Labs/Personas]] | |||
* [[IT/ | *[[IT/Production Acceptance/Basket|Basket]] | ||
* [[IT/ | *[[Labs/OpenWeb]] | ||
* [[IT/ | *[[Labs/Personas]] | ||
* [[IT/ | *[[IT/Production Acceptance/CAD]]: [https://intranet.mozilla.org/Community_Take_Action_Week_2009 Community Take Action Week] | ||
* [http://wiki.mozilla.org/IT/Production_Acceptance/download-day Download Day] | *[[IT/Production Acceptance/all.html redesign]] | ||
* [[IT/ | *[[IT/Production Acceptance/CommunityStore]] | ||
* [[IT/ | *[[IT/Production Acceptance/Retention]] | ||
* [[IT/ | *[http://wiki.mozilla.org/IT/Production_Acceptance/download-day Download Day] | ||
* [[IT/ | *[[IT/Production Acceptance/CRM|CRM]] | ||
* [[IT/ | *[[IT/Production Acceptance/DRM|DRM]] | ||
* [[IT/ | *[[IT/Production Acceptance/Prior Art|Prior Art]] | ||
*[[IT/Production Acceptance/Headrush|Headrush]] | |||
*[[IT/Production Acceptance/PartnerRepacks|Automated Partner Repacks]] | |||
*[[IT/Production Acceptance/CommunityDesign|CommunityDesign]] | |||
*[[IT/Production Acceptance/OpenWeb|OpenWeb]] | |||
*[[IT/Production Acceptance/MozillaServiceWeek|Mozilla Service Week]] | |||
*[[IT/Production Acceptance/FiveYearsofFirefox|Five Years of Firefox]] | |||
*[[IT/Production Acceptance/SecurityQuiz|Security Quiz]] | |||
*[[IT/Production Acceptance/DXR|DXR]] | |||
*[[IT/Production Acceptance/Hacks|Hacks]] | |||
*[[IT/Production Acceptance/ChoiceCampaign|EU Choice Campaign]] | |||
*[[IT/Production Acceptance/Student Reps/Mozilla.org pages|Student Reps/Mozilla.org pages]] | |||
*[[IT/Production Acceptance/Sheriff_Duty|Sheriff Duty]] | |||
= Template = | = Template = | ||
| Line 20: | Line 32: | ||
** Project sponsor | ** Project sponsor | ||
** Main IT contact | ** Main IT contact | ||
** Metrics contact | |||
** Main WebDev contact | ** Main WebDev contact | ||
** Main QA contact | ** Main QA contact | ||
| Line 48: | Line 61: | ||
* Final QA signoff | * Final QA signoff | ||
* Final Security signoff | * Final Security signoff | ||
* Final Metrics signoff | |||
* Operations documents filled for support & any training complete | * Operations documents filled for support & any training complete | ||
* Monitors in place | * Monitors in place | ||
Latest revision as of 23:22, 17 June 2010
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
- Basket
- Labs/OpenWeb
- 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
- OpenWeb
- Mozilla Service Week
- Five Years of Firefox
- Security Quiz
- DXR
- Hacks
- EU Choice Campaign
- Student Reps/Mozilla.org pages
- Sheriff Duty
Template
Start of project
- Name each of the following:
- Project sponsor
- Main IT contact
- Metrics 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
- Final Metrics signoff
- Operations documents filled for support & any training complete
- Monitors in place