IT/Production Acceptance/PartnerRepacks
Start of project
- Project sponsor: Kev Needham / Business Affairs
- Main IT contact: TBD
- Main WebDev contact: TBD
- Main RelEng contact: Chris Cooper
- Main QA contact: Carsten Book (Tomcat)
- Main third party contact: TBD
- Final application owner/maintainer: John O'Duinn / RelEng
Overall goal of the project
Our current infrastructure and resource allocations allow for limited scaling of creating, testing, and authorizing customized versions of Firefox for redistribution by partners. Distribution creation, QA, and signing is a manual process, and the Automated Partner Repack system's primary goal is to automate as much of the current process as possible, and to provide a web-based front-end for creating and managing those distributions. The system's secondary goal is to provide an automation framework that can interact with third party systems and/or Mozilla services to facilitate the creation and distribution of customized builds by Partners directly.
There are three initial components that are required for this project, which include:
- A distribution generation system that stores information about multiple individual builds (partner and configuration information) in a central repository (i.e. an rdb), and can create customized distributions based on that information on demand automatically.
- A web-based administrative front-end that allows Mozilla to manage (add, modify, delete) the information stored about Partners and their customized distribution(s), and generate builds on demand or on release.
- A web-based public facing front end that will allow participants in the Build Your Own Browser program (target of late Q1/early Q2 2009) to register for the program, submit their proposed customizations, and (on approval) generate and distribute their customized builds.
Development is expected to be iterative over 2009, and will ideally add automated QA, marketing/bizdev review, and notification processes to the service, as well as integration with Business Affairs Contact and Contract Management systems.
Project Pre-Requisites
Technology: OSX Server (in-place, for BYOB a fault tolerant setup would be desired. OSX is required for DMG creation), storage capacity for 100 partners (approx. 75-100GB), apache, MySQL, CakePHP (legacy system developed w/Cake)
(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
- 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
- Operations documents filled for support & any training complete
- Monitors in place