IT/Production Acceptance/Hacks: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
Line 36: Line 36:
== Staging Signoff [DONE] ==
== Staging Signoff [DONE] ==
In order to get an app into staging, the following should be completed:
In order to get an app into staging, the following should be completed:
* Code committed to Mozilla source control and tagged: Done (http://viewvc.svn.mozilla.org/vc/projects/hacks.mozilla.org/trunk/)
* Code committed to Mozilla source control and tagged: Checked in, but not sure if everything is tagged. (http://viewvc.svn.mozilla.org/vc/projects/hacks.mozilla.org/trunk/)
* Initial architecture review by IT and WebDev: Done
* Initial architecture review by IT and WebDev: Done
* Plugin/tech review by Evangelism: Done
* Plugin/tech review by Evangelism: Done

Latest revision as of 23:57, 28 December 2009

Start of project

    • External dependencies: None
    • Dev environment specs
    • Does this project use any plugins or proprietary technology?
      • WP Plugins: Co-Authors Plus, FC Pagination, Stats, TMH Pagehits, and ShareThis (already checked into SVN and tested on stage)

Staging Signoff [DONE]

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

  • Code committed to Mozilla source control and tagged: Checked in, but not sure if everything is tagged. (http://viewvc.svn.mozilla.org/vc/projects/hacks.mozilla.org/trunk/)
  • Initial architecture review by IT and WebDev: Done
  • Plugin/tech review by Evangelism: Done
  • Security review must be in-process: N/A
  • Site must be password protected: N/A
  • Review timeline to go live: N/A
  • Review any production requirements so IT can order any new hardware needed: N/A

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