B2G/Hacking: Difference between revisions

Every code change to Gecko must have a corresponding bug on file where the general approach can be discussed. The bug should eventually be assigned to somebody who will upload one or more patches for review. Code can only be reviewed by module owners and their peers; see [[Services/Code_Review|code review policy]] for more information. If the review has been granted and all review comments have been addressed, the patches may be checked into [https://hg.mozilla.org/integration/mozilla-inbound mozilla-inbound]. If the changes pass the automated tests there, they will eventually be uplifted to [https://hg.mozilla.org/mozilla-central mozilla-central] which is the canonical repository for Gecko. If they don't pass the tests, they will be backed out. The bug is where all this status is tracked.

 

It is not uncommon to track bugs that are part of a larger, more long term project in so-called "tracking" or "meta" bugs. This allows people to watch the those meta/tracking bugs and receive updates whenever one of the dependencies change.