hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From st...@apache.org
Subject git commit: Note on make patch for master branch first and a small note on hadoopqa -- to be expanded
Date Mon, 04 Aug 2014 19:08:19 GMT
Repository: hbase
Updated Branches:
  refs/heads/master e91e2659a -> 8f1fc9a79


Note on make patch for master branch first and a small note on hadoopqa -- to be expanded


Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/8f1fc9a7
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/8f1fc9a7
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/8f1fc9a7

Branch: refs/heads/master
Commit: 8f1fc9a79cae4f2d1c83afd135232b06cbd76df3
Parents: e91e265
Author: stack <stack@apache.org>
Authored: Mon Aug 4 12:08:06 2014 -0700
Committer: stack <stack@apache.org>
Committed: Mon Aug 4 12:08:06 2014 -0700

----------------------------------------------------------------------
 src/main/docbkx/developer.xml | 10 ++++++++++
 1 file changed, 10 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hbase/blob/8f1fc9a7/src/main/docbkx/developer.xml
----------------------------------------------------------------------
diff --git a/src/main/docbkx/developer.xml b/src/main/docbkx/developer.xml
index 93d8a61..2aa6bd6 100644
--- a/src/main/docbkx/developer.xml
+++ b/src/main/docbkx/developer.xml
@@ -1634,6 +1634,16 @@ public class MyHBaseIntegrationTest {
           repository.  Patch files can also be easily generated from Eclipse, for example
by selecting "Team -&gt; Create Patch".
           Patches can also be created by git diff and svn diff.
           </para>
+          <para xml:id="patch.master.first">Make patches against the master branch.
Do the master
+              branch first even if you want the patch in another branch altogether.  We operate
by
+              apply fixes first to the master branch and then backporting.  Another reason
to patch
+              master first is because our patch testing system only works against the master
branch.
+              Attach your patch to your JIRA and then mark the issue 'Patch Available'. 
This will prompt
+              the HadoopQA system to run your
+              patch through all unit tests and report back the results to the JIRA. It may
take a few hours
+              for your patch to be run. HadoopQA runs the most recently attached patch to
the JIRA regardless.
+              If you want to rerun your patch against HadoopQA perhaps to verify that indeed
a certain test
+          failure is the result of your patch, then reattach your patch and it will be run
again.</para>
           <para>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. </para>
       <para>


Mime
View raw message