Updates for the book: 13.8.0 : getting the code: * using GIT read only repository git clone git://git.apache.org/hbase.git * using SVN ? 13.8.1 : Creating a patch - using GIT: * grab the lastest src git pull or git pull origin master * hack... hack... hack * test... test... test * generate patch using git diff command git diff --no-prefix > HBASE-XXXX-v1.patch > no-prefix option is essential > do this from the root of the src tree Sometimes you may want to submit multiple patches. One way to do that is by creating a local git branch. Here is a sample work flow - patch 1 git pull hack.... git diff --no-prefix > HBASE-XXXX-1.patch - patch 2 # create a new git branch git checkout -b my_branch # save your work git add file1 file2 git commit -am 'saved after HBASE-XXXX-1.patch' # now you have your own branch, that is different from remote master branch # make more changes.... # create second patch git diff --no-prefix > HBASE-XXXX-2.patch 13.8.2 : Patch Naming Name patches after the issue number e.g. : HBASE-1234.patch HBASE-1234-v2.patch (if resubmitting the patch with modifications) 13.8.4 : Submitting a Patch via JIRA addition: Sometimes committers ask for changes for a patch. After incorporating the suggested/requested changes, it is time to submit the patch again. - do not delete the OLD patch file - version your new patch file using a simple scheme like this HBASE-{jira number}-{version}.patch e.g: HBASE-XXXX-v2.patch - 'Cancel Patch' on JIRA.. bug status will change back to Open - attach your new patch file (HBASE-XXXX-v2.patch) using 'Files --> Attach' - Click on 'Submit Patch'. Now the bug status will say 'Patch Available'. Committers will review the newer submission - rinse and repeat as many times as needed