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 YongjunZhang: https://wiki.apache.org/hadoop/HowToContribute?action=diff&rev1=102&rev2=103 ==== Naming your patch ==== - Patches for trunk should be named according to the Jira, with a version number: '''jira-xyz.abc.patch''', eg hdfs-1234.001.patch. + Patches for trunk should be named according to the Jira, with a version number: '''<jiraName>.<versionNum>.patch''', e.g. HADOOP-1234.001.patch, HDFS-4321.002.patch. - Patches for a non-trunk branch should be named '''jira-xyz-branch.abc.patch''', eg hdfs-1234-branch-0.23.003.patch. The branch name suffix should be the exact name of a Subversion branch under hadoop/common/branches/, such as "branch-0.23". Please note that the Jenkins pre-commit build is only run against trunk. + Patches for a non-trunk branch should be named '''<jiraName>-<branchName>.<versionNum>.patch''', e.g. HDFS-1234-branch-0.23.003.patch. The branch name suffix should be the exact name of a Subversion branch under hadoop/common/branches/, such as "branch-0.23". Please note that the Jenkins pre-commit build is only run against trunk. - It's also OK to upload a new patch to Jira with the same name as an existing patch. If you select the "Activity>All" tab then the different versions are linked in the comment stream, providing context. However, many reviewers find the three-digit version number convenient, so including a version number is the preferred style. + It's also OK to upload a new patch to Jira with the same name as an existing patch. If you select the "Activity>All" tab then the different versions are linked in the comment stream, providing context. However, many reviewers find it helpful to include a version number in the patch name (three-digit version number is recommended), '''so including a version number is the preferred style'''. === 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.
