Websites/Processes: Difference between revisions

Jump to navigation Jump to search
Line 53: Line 53:
* Driver: TPM
* Driver: TPM


During the implementation phase, the Web Dev and UX teams write the website code following Mozilla guidelines (forthcoming).
== Mozilla Web Development Guidelines ==
 
During the implementation phase, the Web Dev and UX teams write the website code following Mozilla guidelines:
 
* Developers are expected to follow:
** [[WebDev:FrontendCodeStandards|Code best practices guidelines]]
** [[WebAppSec#Secure_Development_Guidance|Security guidelines]]
 
* At least 1 Mozilla web developer responsible for the [[Webdev:Flux:Code_Review_Process|code review]] of all code committed to the code repository.
 
* [http://bugzilla.mozilla.org Bugzilla] is the ticket tracking system that will be used to for bug reporting and project overviews.  Developers are expected to adhere to the [[QA/Execution/Web_Testing/Project_Checklist#Optimal_Bugzilla_Workflow|Bugzilla Workflow]] for tracking tickets.


== Process ==
== Process ==
Line 79: Line 89:
* Legal review begins.
* Legal review begins.
* L10N process begins.
* L10N process begins.
* QA testing begins.
* [[QA/Execution/Web_Testing/Project_Checklist|QA testing]] begins.


7. QA signs off on initial round of tests.
7. QA signs off on initial round of tests.
Line 94: Line 104:


12. TPM prepares Bugzilla ticket for Production Push.
12. TPM prepares Bugzilla ticket for Production Push.
== Supplementary Documents ==
* [[WebDev:FrontendCodeStandards|Code Best Practices Guidelines]]
* [[Webdev:Flux:Code_Review_Process|Code Review]]
* [[QA/Execution/Web_Testing/Project_Checklist#Optimal_Bugzilla_Workflow|Bugzilla Workflow]]
* [[QA/Execution/Web_Testing/Project_Checklist|QA Process]]
* [[WebAppSec#Secure_Development_Guidance|Security Guidelines]]
* Accessibility Review
* SEO Review


= Deployment =
= Deployment =
1,241

edits

Navigation menu