From MozillaWiki
Revision as of 10:09, 20 April 2011 by Firepug (Talk | contribs)

Jump to: navigation, search was launched on November 29, 2005 with the Firefox 1.5 release with the goal of simplifying the experience of obtaining Mozilla products.

The mission of is to:

  • provide a quick and easy path for obtaining our software
  • educate visitors about the advantages of our software
  • connect users with other Mozilla web properties they may be looking for

The audiences for

  • End users of Mozilla products (both consumers and power users)
  • Current Firefox and Thunderbird users looking for upgrade information
  • Visitors interested in information about Mozilla Corporation



For Q2 the following projects are going on:

  • Mobile friendliness
    • Create design/coding standards for making sites mobile-friendly
    • Use metrics to determine pages to focus on
    • Begin implementing design/coding standards for
  • Execute Phase 1. of the .com/.org merge
    • Complete content inventory & audit of pages on .com that will be redirected to .org
    • Redirect .com pages specified in the inventory to .org
    • Complete IA review & finalize revised IA for .com/.org merge (eliminating redundant content)
    • Begin/complete update to .com design that will become the new skin for .org pages
    • Analyze current workflows:
    • Keep discussing strategy
  • Automated tests
    • Hook up Raymond's tests and get them running on Hudson
    • Write tons of more tests
  • Git transition
    • Work with localizers to warn them of switch
    • Work with IT on switching live site to git
    • Use github from then on

These mostly came out of Q2 onsite meetings.

See the following page for more general Q2 goals:



Work is developed, tested, and reviewed on trunk, pushed to staging to be queued for rollout, and pushed to a production branch to go live.

  1. dev works on a bug and makes a commit to trunk with bug number, leaves a comment on bug with trunk revision
  2. work is reviewed and when fixed, bug is marked "resolved fixed"
  3. add keyword "qawanted" to bug to move to testing
  4. bug is tested and re-opened if not fixed, marked "qa-verified-trunk" if fixed
  5. dev merges all changes into "stage" branch, leaves comment on bug with stage revision
  6. if change is a one-off, add keywork "push-needed" for immediate rollout
  7. bug is rolled out individually (push-needed) or with milestone (staging is merged onto production)
  8. and "push-needed" keywords are removed
  9. QA checks on production, marks "verified fixed"; if there's a problem, re-opens bug, dev might revert changes on production if problem is critical

Here are a few example SVN commands one might use:

commit to trunk (r100)
  svn commit -m 'bug 60000 - spread happiness around'

merge to staging (r50)
  svn merge --ignore-ancestry -c100,104 trunk tags/stage
  cd tags/stage && svn commit -m 'r100,104 from trunk for bug 60000'

merge to prod (r40)
  svn merge --ignore-ancestry -c50 tags/stage tags/prod
  cd tags/prod && svn commit -m 'r50 from staging for bug 60000'

revert on prod
  cd tags/prod && svn merge -c-40 .

The important point in this process is that the developer can commit what he/she wants to trunk, but he/she is responsible for merging those changes into stage to be rolled out.

QA usually tests on trunk ( SVN Source

The source behind (PHP, HTML, images, CSS, javascript, etc.) is hosted and managed in Subversion. For details merging from trunk to stage, see the SVN Guidelines.


See all bugs related to