mozilla

Revision 129654 of mozilla-central

  • Revision slug: mozilla-central
  • Revision title: mozilla-central
  • Revision id: 129654
  • Created:
  • Creator: Beltzner
  • Is current revision? No
  • Comment 14 words added, 15 words removed

Revision Content

mozilla-central is a Mercurial repository of the Mozilla code: http://hg.mozilla.org/mozilla-central .

The Tinderbox page for mozilla-central is located at http://tinderbox.mozilla.org/showbui...i?tree=Firefox .

{{ Note("Unlike the Mozilla CVS repository, only Firefox and XULRunner sources are included in mozilla-central. Separate repositories will be used for code specific to other applications and projects.") }}

mozilla-central tree rules

Requirements

  • Do not check in until you have appropriate review, including super-review and approval if needed. Check the tree rules page to see the current checkin policy for the tree.
  • Do not check in when any box is orange or red, unless the failure has been starred with a bug number or a fix.  (You should be pretty sure the next cycle will be green and all recent intermittent failures are understood.)
  • You should be available for the next hour or two in case something goes wrong with your checkin.  (This is roughly the time it takes to get unit test results from all platforms.)

Regressions

Any regressions on tier-1 platforms are cause for immediate backout. Regressions on tier-2 platforms are usually not cause for backout, but you will be expected to help fix them if needed.

If you think your patch might cause regressions, land on {{ mediawiki.interwiki('wikimo', 'Build:TryServer', 'Try server') }} first.

Pushing changes to mozilla-central

See How do I check stuff in? for help with hg commit and hg push. If you believe you should have access to mozilla-central but don't know your login details, file a bug.

  • Changes must not introduce multiple heads into mozilla-central.
  • Please try to keep history tidy. A single commit or a few independent changesets are preferable to many "work in progress" changesets which clutter history. Consider using Mercurial queues to manage patches before checkin.
  • At least the final changeset being pushed should list the bug number and reviewer for the relevant change.
  • Your commit comment must include the bug number and reviewers.  It should contain the summary of the bug or a clear explanation of the fix.  A typical format of commit comments which is generally accepted by the community consists of:
    • Bug number (example: "Bug xxxxxx" or "b=xxxxxx"; the former form is preferred)
    • Summary of the change.  This can be the summary of the bug itself if it's descriptive enough.
    • The reviewers approvals, in one or more of the following forms:
      • r=reviewer (for multiple reviewers, separate by commas)
      • sr=super-reviewer (for multiple super-reviewers, separate by commas)
  • If you are not the author of the code, make that clear, using commit -u "Patch Author <email@example.com>".

Here is an example of a good commit comment:
      Bug 505691 - Remove unnecessary include of nsIPref.h. r=vlad

There are special rules related to the copies of NSPR and NSS in mozilla-central.

See also

{{ languages( { "ja": "ja/Mozilla-central", "es": "es/Mozilla-central" } ) }}

Revision Source

<p><strong><code>mozilla-central</code></strong> is a <a href="/en/Mercurial" title="en/Mercurial">Mercurial</a> repository of the Mozilla code: <a class=" external" href="http://hg.mozilla.org/mozilla-central" rel="freelink">http://hg.mozilla.org/mozilla-central</a> .</p>
<p>The <a href="/en/Tinderbox" title="en/Tinderbox">Tinderbox</a> page for mozilla-central is located at <a class=" external" href="http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox" rel="freelink">http://tinderbox.mozilla.org/showbui...i?tree=Firefox</a> .</p>
<p>{{ Note("Unlike the Mozilla CVS repository, only Firefox and XULRunner sources are included in mozilla-central. Separate repositories will be used for code specific to other applications and projects.") }}</p>
<h3 name="mozilla-central_tree_rules">mozilla-central tree rules</h3>
<h4 name="API_Changes">Requirements</h4>
<ul> <li>Do not check in until you have appropriate <a class="internal" href="/en/Code_Review_FAQ" title="En/Code Review FAQ">review</a>, including <a class="external" href="http://www.mozilla.org/hacking/reviewers.html" title="http://www.mozilla.org/hacking/reviewers.html">super-review</a> and <a class="link-https" href="https://wiki.mozilla.org/TreeStatus" title="https://wiki.mozilla.org/TreeStatus">approval</a> if needed. Check the <a class="external" href="http://wiki.mozilla.org/TreeRules" title="http://wiki.mozilla.org/TreeRules">tree rules page</a> to see the current checkin policy for the tree.</li> <li>Do not check in when any box is orange or red, unless the failure has been <strong>starred with a bug number or a fix</strong>.  (You should be pretty sure the next cycle will be green and all recent intermittent failures are understood.)</li> <li>You should be available for the next hour or two in case something goes wrong with your checkin.  (This is roughly the time it takes to get unit test results from all platforms.)</li>
</ul>
<h4 name="API_Changes">Regressions</h4>
<ul> <li><a class="internal" href="/en/Mozilla_automated_testing" title="En/Mozilla automated testing">Automated unit tests</a> must pass and not leak.</li> <li><a class="link-https" href="https://wiki.mozilla.org/Performance:Tinderbox_Tests" title="https://wiki.mozilla.org/Performance:Tinderbox_Tests">Automated speed tests</a> must not regress (<a class="external" href="http://www.mozilla.org/hacking/regression-policy.html" title="http://www.mozilla.org/hacking/regression-policy.html">performance regression policy</a>).</li>
</ul>
<p>Any regressions on <a href="/en/Supported_build_configurations" title="en/Supported_build_configurations">tier-1 platforms</a> are cause for immediate backout. Regressions on tier-2 platforms are usually not cause for backout, but you will be expected to help fix them if needed.</p>
<p>If you think your patch <em>might</em> cause regressions, land on {{ mediawiki.interwiki('wikimo', 'Build:TryServer', 'Try server') }} first.</p>
<h3 name="Pushing_changes_to_mozilla-central">Pushing changes to mozilla-central</h3>
<p>See <a href="/en/Mercurial_FAQ#How_do_I_check_stuff_in.3F" title="en/Mercurial_FAQ#How_do_I_check_stuff_in.3F">How do I check stuff in?</a> for help with hg commit and hg push. If you believe you should have access to mozilla-central but don't know your login details, <a class="link-https" href="https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&amp;component=Server+Operations:+Account+Requests">file a bug</a>.</p>
<ul> <li>Changes must not introduce multiple heads into mozilla-central.</li> <li>Please try to keep history tidy. A single commit or a few independent changesets are preferable to many "work in progress" changesets which clutter history. Consider using <a href="/en/Mercurial_Queues" title="en/Mercurial_Queues">Mercurial queues</a> to manage patches before checkin.</li> <li>At least the final changeset being pushed should list the bug number and reviewer for the relevant change.</li> <li>Your <em>commit comment</em> must include the bug number and reviewers.  It should contain the summary of the bug or a clear explanation of the fix.  A typical format of commit comments which is generally accepted by the community consists of:<br> <ul> <li>Bug number (example: "Bug xxxxxx" or "b=xxxxxx"; the former form is preferred)</li> <li>Summary of the change.  This can be the summary of the bug itself if it's descriptive enough.</li> <li>The reviewers approvals, in one or more of the following forms:<br> <ul> <li>r=reviewer (for multiple reviewers, separate by commas)</li> <li>sr=super-reviewer (for multiple super-reviewers, separate by commas)</li> </ul> </li> </ul> </li> <li>If you are not the author of the code, make that clear, using commit -u "Patch Author &lt;<a class=" link-mailto" href="mailto:email@example.com" rel="freelink">email@example.com</a>&gt;".</li>
</ul>
<p>Here is an <a class="external" href="http://hg.mozilla.org/mozilla-central/rev/737a77143f49" title="http://hg.mozilla.org/mozilla-central/rev/737a77143f49">example</a> of a good commit comment:<br>
      <span style="font-family: Courier New;">Bug 505691 - Remove unnecessary include of nsIPref.h. r=vlad</span></p>
<p>There are special rules related to the copies of <a class="internal" href="/En/External_CVS_snapshots_in_mozilla-central" title="En/External CVS snapshots in mozilla-central">NSPR and NSS in mozilla-central</a>.</p>
<h3 name="See_also">See also</h3>
<ul> <li><a class="external" href="http://developer.mozilla.org/devnews/index.php/2008/06/02/mozilla-central-open-for-business/">mozilla-central: open for business</a> devnews post.</li> <li><a class="link-https" href="https://bugzilla.mozilla.org/showdependencytree.cgi?id=433384&amp;hide_resolved=1">Tracking: issues making development difficult on mozilla-central</a></li>
</ul>
<p>{{ languages( { "ja": "ja/Mozilla-central", "es": "es/Mozilla-central" } ) }}</p>
Revert to this revision