IT/Production Acceptance/Basket

Start of project

• Name each of the following:
  • Project sponsor: Marketing
    • Jane F / Eve M
  • Main IT contact: needed
  • Metrics contact: N/A
  • Main WebDev contact: Alex Buchanan
  • Main QA contact: Stephen Donner
  • Main Security contact: needed
  • Final application owner/maintainer: Alex Buchanan
• Outline the following:
  • Overall goal of the project
    • An RESTful service API for collecting email list subscriptions from multiple mozilla websites, including mozilla.com and AMO.
  • Any pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc)
    • Python 2.6+
    • Django
    • MySQL
    • Possible high traffic service. Service clients include submission from high traffic pages on mozilla.com (Firstrun, Whatsnew, Firefox Sync) and AMO.
  • Initial timeline
    • Stage week of June 1-4, 2010
    • Production launch week of June 7-11, 2010
  • External dependencies: N/A
  • Dev environment specs: what is this?
  • Does this project use any plugins or proprietary technology? No

Staging Signoff

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

• Code committed to Mozilla source control and tagged
  • Is GitHub bad?
  • http://github.com/abuchanan/basket
• Initial architecture review by IT and WebDev
• Plugin/tech review by Evangelism: N/A
• Security review must be in-process
• Site must be password protected: really? I don't think that's needed in this case. -Alex
• 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