Skip to main content

Visit Mozilla.org

mozilla-central

From MDC

mozilla-central is a Mercurial repository of the Mozilla code: http://hg.mozilla.org/mozilla-central . It is a stable integration point for changes which will be incorporated into the Mozilla 2 codebase.

The Tinderbox page for mozilla-central is located at http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla2 .

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.

Contents

[edit] mozilla-central tree rules

The mozilla-central codebase should be stable on the tier-1 platforms at all times:

  • Automated unit tests must pass
  • Automated performance and leak tests must not regress
  • Any regressions are cause for immediate backout of the offending patch.
  • Developers should not do test-landings into mozilla-central to check whether a patch regresses performance or unit tests. The Try server should be used instead.

[edit] API Changes

In preparation for 1.9.1, the following rules govern API changes:

  • changes to frozen APIs are not currently permitted
  • changes to nonfrozen APIs should be carefully considered.
    • Any impact on JS extensions should be avoided or minimized and carefully documented.
    • Reviewers should explicitly approve API changes if necessary.
    • If in doubt, ask the mozilla.dev.platform or mozilla.dev.apps.firefox newsgroup.

These rules will change after 1.9.1 branches.

[edit] Pushing changes to mozilla-central

All developers who have CVS checkin access should have received an email with LDAP login details for pushing to hg.mozilla.org. If you believe you should have access to mozilla-central but don't know your login details, file a bug. You can use the hg push command to push changesets to the server.

  • 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.
  • Changes must be pushed to ssh://hg.mozilla.org/mozilla-central/, check Mercurial FAQ#How do I check stuff in? for details of how to set up your configuration.

[edit] See also

Retrieved from "http://developer.mozilla.org/en/docs/mozilla-central"