JavaScript:New to SpiderMonkey: Difference between revisions

JavaScript:New to SpiderMonkey (view source)

113 bytes removed , 11 October 2016

→‎Workflow: treeherder, inbound

Confirmed users

329

edits

@@ Line 200: / Line 200: @@
 === Workflow ===
-Everything goes through bugzilla. We find a bug or have an idea, then submit it to bugzilla, then file patches to solve it. When it is solved, the patch is reviewed by team members, and is then committed to the [http://hg.mozilla.org/mozilla-central mozilla-central repository]. A link to the commit is then added as a comment to the bug.
+Everything goes through bugzilla. We find a bug or have an idea, then submit it to bugzilla, then file patches to solve it. When it is solved, the patch is reviewed by team members, and is then committed to the [http://hg.mozilla.org/integration/mozilla-inbound mozilla-inbound repository]. A link to the commit is then automatically added as a comment to the bug. mozilla-inbound is periodically merged to mozilla-central by a Sheriff. This exempts us from watching [https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound treeherder] to check for failures caused by our patches, and commits are automatically backed out if errors are found.
-As well as committing to [http://hg.mozilla.org/mozilla-central mozilla-central], we also have the option of committing to [http://hg.mozilla.org/integration/mozilla-inbound mozilla-inbound], which is automatically merged to mozilla-central by a Sheriff. This exempts us from watching [http://tbpl.mozilla.org tinderbox] to check for errors in our patches, and commits are automatically backed out if errors are found.
 ==== Sample Workflows ====