hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "HowToContribute" by EliCollins
Date Fri, 09 Sep 2011 21:59:20 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "HowToContribute" page has been changed by EliCollins:
http://wiki.apache.org/hadoop/HowToContribute?action=diff&rev1=59&rev2=60

  
  This way other developers can preview your change by running the script and then applying
the patch.
  
+ ==== Naming your patch ====
+ 
+ Patches for trunk should be named '''jira-xyz.patch''', eg hdfs-123.patch. Patches for a
specific branch should be named '''jira-xyz-branch.patch''', eg hdfs-123-branch-0.20-security.
+ 
+ It's OK to upload a patch to Jira with the same name as an existing patch, Jira will just
make the previous patches grey. They're still listed, sorted by date. If you select the "Activity>All"
tab then the different versions are linked in the comment stream, providing context. The branch
name allows the pre-commit tests to run against the correct branch (HADOOP-7435).
+ 
+ 
  ==== Testing your patch ====
  Before submitting your patch, you are encouraged to run the same tools that the automated
Jenkins patch test system will run on your patch.  This enables you to fix problems with your
patch before you submit it. The {{{dev-support/test-patch.sh}}} script in the trunk directory
will run your patch through the same checks that Hudson currently does ''except'' for executing
the unit tests.
  

Mime
View raw message