Partnering/Repacks/Policy and Process

Version Control

Mozilla keeps all of our partner repack configuration files under version control in Mercurial (hg).

If you are unfamiliar with hg, Mozilla has some good dev resources for getting started:

• The basics
• Getting Mozilla Source Code Using Mercurial
• Using Mercurial

The partner-repacks repository (repo) is publicly available here: https://hg.mozilla.org/build/partner-repacks

Creating a patch

This section assumes that you are already familiar with the basics of hg.

Here is a generalized workflow:

• clone the partner-repacks repo
  • if you already have the repo, run hg pull instead
• make sure you don't have any existing changes in source clone by running hg status
• make any necessary changes to your partner repack files
  • make sure you run hg add to add new files, or hg remove if you are removing files
• commit changes to your local repository, hg commit ...
• export the changeset using hg export REV, where REV is the revision number of the changeset, e.g.:

$ PARTNERNAME=aol
$ hg export tip > repack_config_changes_for_$PARTNERNAME.diff

Submitting a patch

TODO: bug filing template