Mailing-List: contact common-commits-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Thu, 04 Dec 2014 17:28:36 -0000
Message-ID: <20141204172836.84297.90497@eos.apache.org>
Subject: 
 =?utf-8?q?=5BHadoop_Wiki=5D_Update_of_=22HowToContribute=22_by_YongjunZha?=
 =?utf-8?q?ng?=
Auto-Submitted: auto-generated

Dear Wiki user,

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

The "HowToContribute" page has been changed by YongjunZhang:
https://wiki.apache.org/hadoop/HowToContribute?action=3Ddiff&rev1=3D102&rev=
2=3D103

  =

  =3D=3D=3D=3D Naming your patch =3D=3D=3D=3D
  =

- Patches for trunk should be named according to the Jira, with a version n=
umber: '''jira-xyz.abc.patch''', eg hdfs-1234.001.patch.
+ Patches for trunk should be named according to the Jira, with a version n=
umber: '''<jiraName>.<versionNum>.patch''', e.g. HADOOP-1234.001.patch, HDF=
S-4321.002.patch.
  =

- Patches for a non-trunk branch should be named '''jira-xyz-branch.abc.pat=
ch''', eg hdfs-1234-branch-0.23.003.patch.  The branch name suffix should b=
e 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 ru=
n 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 n=
ame suffix should be the exact name of a Subversion branch under hadoop/com=
mon/branches/, such as "branch-0.23". Please note that the Jenkins pre-comm=
it build is only run against trunk.
  =

- It's also OK to upload a new patch to Jira with the same name as an exist=
ing patch. If you select the "Activity>All" tab then the different versions=
 are linked in the comment stream, providing context. However, many reviewe=
rs find the three-digit version number convenient, so including a version n=
umber is the preferred style.
+ It's also OK to upload a new patch to Jira with the same name as an exist=
ing patch. If you select the "Activity>All" tab then the different versions=
 are linked in the comment stream, providing context. However, many reviewe=
rs find it helpful to include a version number in the patch name (three-dig=
it version number is recommended), '''so including a version number is the =
preferred style'''.
  =

  =3D=3D=3D Testing your patch =3D=3D=3D
  Before submitting your patch, you are encouraged to run the same tools th=
at the automated Jenkins patch test system will run on your patch.  This en=
ables 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.