Firefox/Kinto: Difference between revisions

formatting
(import release instructions)
(formatting)
Line 63: Line 63:
==== TDD mode ====
==== TDD mode ====


Using *inotify*, we will detect a file change in the `dist/` folder and run a series of commands to execute the tests automatically.
Using ''inotify'', we will detect a file change in the `dist/` folder and run a series of commands to execute the tests automatically.


First, install `inotify-tools`:
First, install ''inotify-tools'':


     sudo apt-get install inotify-tools
     sudo apt-get install inotify-tools
Line 86: Line 86:
> Patch are contributed to kinto.js and kinto-client.js, which are first released on NPM.
> Patch are contributed to kinto.js and kinto-client.js, which are first released on NPM.


**DO NOT** land files that are not tagged officially on upstream repositories.
'''DO NOT''' land files that are not tagged officially on upstream repositories.


==== Become a contributor =====
==== Become a contributor =====
Line 105: Line 105:
See https://wiki.mozilla.org/ReleaseEngineering/TryServer
See https://wiki.mozilla.org/ReleaseEngineering/TryServer


Or use a *gecko-dev* fork from Github, and with install [moz git tools](https://github.com/mozilla/moz-git-tools)
Or use a ''gecko-dev'' fork from Github, and with install [https://github.com/mozilla/moz-git-tools moz git tools]


     git push-to-try -t --rev master..HEAD ~/hg/mozilla-central/ -b do -p linux,linux64,macosx64,win32,win64 -u xpcshell -t none
     git push-to-try -t --rev master..HEAD ~/hg/mozilla-central/ -b do -p linux,linux64,macosx64,win32,win64 -u xpcshell -t none


==== Submit for review ====  
==== Submit for review ====  
See http://mozilla-version-control-tools.readthedocs.org


     # Commit with link to Bugzilla
     # Commit with link to Bugzilla
Line 122: Line 124:
     # Go back to «master»
     # Go back to «master»
     hg update central
     hg update central
Examples:
* https://reviewboard.mozilla.org/r/45445/
24

edits