diff --git a/src/docbkx/developer.xml b/src/docbkx/developer.xml index cb724ccece6..e56bcee8ed0 100644 --- a/src/docbkx/developer.xml +++ b/src/docbkx/developer.xml @@ -126,5 +126,61 @@ mvn test -Dtest=TestXYZ + +
+ Getting Involved + HBase gets better only when people contribute! The following are highlights from the HBase wiki on + How To Contribute. + +
+ Mailing Lists + Sign up for the dev-list, and the user-list too for greater coverage. See the + mailing lists page. + +
+
+ Jira + Check for existing issues in Jira. + If it's either a new feature request, enhancement, or a bug, file a ticket. + +
+
+ Submitting Patches +
+ Create Patch + Patch files can be easily generated from Eclipse, for example by selecting Team -> Create Patch. + + Please submit one patch-file per Jira. For example, if multiple files are changed make sure the + selected resource when generating the patch is a directory. Patch files can reflect changes in multiple files. +
+
+ Patch File Naming + The patch file should have the HBase Jira ticket in the name. For example, if a patch was submitted for Foo.java, then + a patch file called Foo_HBASE_XXX.patch would be acceptable where XXX is the HBase Jira number. + +
+
+ Unit Tests + Yes, please. Please try to include unit tests with every code patch (and especially new classes and large changes). +
+
+ Attach Patch to Jira + The patch should be attached to the associated Jira ticket. + + Once attached to the ticket, click "submit patch" and + the status of the ticket will change. Committers will review submitted patches for inclusion into the codebase. Please + understand that not every patch may get committed, and that feedback will likely be provided on the patch. Fear not, though, + because the HBase community is helpful! + +
+
+
+ Committing Patches + + See How To Commit in the HBase wiki. + +
+ +
diff --git a/src/docbkx/performance.xml b/src/docbkx/performance.xml index b9f3d5c5103..796f09db1f6 100644 --- a/src/docbkx/performance.xml +++ b/src/docbkx/performance.xml @@ -320,8 +320,8 @@ htable.close();
Concurrency: Monitor Data Spread - When performing a high number of concurrent reads, monitor the data spread of the target tables. If there target table(s) are in - too few regions then the reads will fall on only a few nodes. + When performing a high number of concurrent reads, monitor the data spread of the target tables. If the target table(s) have + too few regions then the reads could likely be served from too few nodes. See , as well as