1,241
edits
Websites/Processes: Difference between revisions
Jump to navigation
Jump to search
→Process
Ryansnyder (talk | contribs) |
Ryansnyder (talk | contribs) |
||
| Line 52: | Line 52: | ||
* Decider: Product Owner | * Decider: Product Owner | ||
* Driver: TPM | * Driver: TPM | ||
During the implementation phase, the Web Dev and UX teams write the website code following Mozilla guidelines (forthcoming). | |||
== Process == | == Process == | ||
1. TPM schedules and drives the [[Websites/Processes/Meetings/Weekly_Meeting_Agenda|weekly meeting]]. | |||
Once the initial code base has been created, and the website is functioning as indicated in the specs in a development environment, the | Once the initial code base has been created, and the website is functioning as indicated in the specs in a development environment, the remaining process may begin. | ||
2. TPM ensures the stage server is up and running, and the website is functioning as indicated in the specs. | 2. TPM ensures the stage server is up and running, and the website is functioning as indicated in the specs. | ||
* Stage server will be set to auto-update from master branch of code repository every 5 minutes. | * Stage server will be set to auto-update from master branch of code repository every 5 minutes. | ||
3. The following processes begin; each team follows Bug Life Cycle process. | 3. The following processes begin; each team follows Bug Life Cycle process. | ||
* Accessibility Review begins. | * Accessibility Review begins. | ||
* SEO Review begins. | * SEO Review begins. | ||
4. Web Dev notifies TPM that all required strings and code have been committed to stage. | 4. Web Dev notifies TPM that all required strings and code have been committed to stage. | ||
* Web Dev continues to fix bugs, but only commits code to a development branch. | * Web Dev continues to fix bugs, but only commits code to a development branch. | ||
5. TPM notifies team that: | 5. TPM notifies team that: | ||
* feature freeze is in effect. | * feature freeze is in effect. | ||
* string freeze is in effect. | * string freeze is in effect. | ||
6. The following processes begin; each team follows Bug Life Cycle process. | 6. The following processes begin; each team follows Bug Life Cycle process. | ||
* IT testing begins. | * IT testing begins. | ||
| Line 75: | Line 80: | ||
* L10N process begins. | * L10N process begins. | ||
* QA testing begins. | * QA testing begins. | ||
7. QA signs off on initial round of tests. | 7. QA signs off on initial round of tests. | ||
8. TPM notifies team that code freeze is in effect. | 8. TPM notifies team that code freeze is in effect. | ||
* Web Dev continues to fix bugs, but does not commit code to master branch. | * Web Dev continues to fix bugs, but does not commit code to master branch. | ||
9. Infrasec testing begins; team follows Bug Life Cycle process. | 9. Infrasec testing begins; team follows Bug Life Cycle process. | ||
10. TPM notifies team that code freeze is no longer in effect. | 10. TPM notifies team that code freeze is no longer in effect. | ||
* Web Dev may again commit code to master branch. | * Web Dev may again commit code to master branch. | ||
11. QA signs off on final round of tests. | 11. QA signs off on final round of tests. | ||
12. TPM prepares Bugzilla ticket for Production Push. | 12. TPM prepares Bugzilla ticket for Production Push. | ||