Mobile/Fennec/Android: Difference between revisions

Mobile/Fennec/Android (view source)

Revision as of 22:07, 24 April 2015

948 bytes added , 24 April 2015

→‎Creating commits and submitting patches

Liuche

Confirmed users

400

edits

@@ Line 66: / Line 66: @@
 === Creating commits and submitting patches ===
-For tips on using version control to save and share your code, see [[#Mercurial tips]].
+Mercurial (hg) is the the main version control system that Mozilla uses, and to submit code for review, you should be able to generate patches or commits. Be sure to run mach mercurial-setup when cloning the source code repository -- this will ensure you have good default settings and extensions.
+Historically, Mozilla has used Mercurial patch queues to submit code changes for review. However, Mozilla developers are now encouraged to use a Mercurial bookmark-based workflow.
+If you're a contributor and new to Mercurial, patch queues are conceptually simple and fine for getting your first few patches up; see the instructions on [https://developer.mozilla.org/en-US/docs/Mercurial_Queues Mercurial patch queues].
+If you're interested in using bookmarks, take a look at [http://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/bookmarks.html bookmarks-based development].
 After writing the patch, make sure the commit message is of the correct format:<br />
@@ Line 77: / Line 83: @@
 Once the patch gets an r+ on review, if you don't have tree privileges, ask someone to land it for you; or, set checkin-needed in the keywords field AND ask someone to push it to the try server.
+(If you want more information about bookmarks-based workflow, gps has some [https://people.mozilla.org/~gszorc/mastering-vcs/#1 slides].)
 === Android NDK and SDK version notes ===