Mozilla.com/Workflow-improvements
This is an article about critiquing mozilla.com's workflow and improving it.
Overview
Work on mozilla.com is done by a team of 3-5 people, with additional localization changes from contributors. There is an even ratio between high frequency small changes and larger less frequent additions.
Everything is managed through SVN, with three different branches: trunk, stage, and production. All committers commit everything to trunk (many commits per day). QA tests bugs when they are finished off the trunk branch, and when verified, the committer selects the changes with SVN and merges it onto the stage branch, and pushes the new revision from stage to production. QA tests it on production, and if fixed, the bug is verified fixed.
There is not a clear process for rolling back, besides using SVN to roll files back to a specified revision.
The current process goes something like this:
+-------------------------+ +----------------------------+
| | qawanted | |
| developer guy |------------------->| QA guy |
| |<-------------------| |
| | qa-verified-trunk | |
+-------------------------+ +----------------------------+
| ^ | ^
| | | |
| svn up | | bug fix | testing
| | | |
| | v v
| +-------------------------+ +------------------------+
| | trunk |------->| www-trunk.mozilla.com |
| +-------------------------+ +------------------------+
|
|
+-------------------------------+
|
| push-needed
|
v