Confirmed users
328
edits
JavaScript:New to SpiderMonkey: Difference between revisions
Jump to navigation
Jump to search
JavaScript:New to SpiderMonkey (view source)
Revision as of 15:44, 11 October 2016
, 11 October 2016→Commit: sheriffs watch our backs
(→Get a review: mrgiggles) |
(→Commit: sheriffs watch our backs) |
||
| Line 130: | Line 130: | ||
You can't commit to mozilla-central / mozilla-inbound until you have "level 3" access, so you'll need someone to do this for you. Try asking in [irc://irc.mozilla.org/#jsapi #jsapi], or add the <code>checkin-needed</code> keyword to the bug. After you have been contributing for a while, you can get level 3 access by [https://www.mozilla.org/hacking/commit-access-policy/ applying for it]. | You can't commit to mozilla-central / mozilla-inbound until you have "level 3" access, so you'll need someone to do this for you. Try asking in [irc://irc.mozilla.org/#jsapi #jsapi], or add the <code>checkin-needed</code> keyword to the bug. After you have been contributing for a while, you can get level 3 access by [https://www.mozilla.org/hacking/commit-access-policy/ applying for it]. | ||
After committing, a large series of tests will be run to make sure you didn't break anything. You | After committing, a large series of tests will be run to make sure you didn't break anything. You will need to hang around to make sure you didn't break something. It is difficult to determine what failures are real and what are what we call "intermittent oranges" ("orange" because that is the color used on our continuous integration dashboard for test failures). If you do break something, a sheriff will probably let you know via IRC and will probably back your patch out. You can always ask [irc://irc.mozilla.org/#jsapi for help] determining what is going on. (Over time you'll get a feel for figuring out when breakage is real on your own.) | ||
== Overview of the JS engine == | == Overview of the JS engine == | ||