hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zheng, Kai" <kai.zh...@intel.com>
Subject RE: IMPORTANT: testing patches for branches
Date Wed, 22 Apr 2015 22:34:56 GMT
Hi Allen,

This sounds great. 

>> Naming a patch foo-HDFS-7285.00.patch should get tested on the HDFS-7285 branch.
Does it happen locally in developer's machine when running test-patch.sh, or also mean something
in Hadoop Jenkins building when a JIRA becoming patch available? Thanks.

Regards,
Kai

-----Original Message-----
From: Allen Wittenauer [mailto:aw@altiscale.com] 
Sent: Thursday, April 23, 2015 3:35 AM
To: common-dev@hadoop.apache.org
Cc: yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: IMPORTANT: testing patches for branches

	
Hey gang, 

	Just so everyone is aware, if you are working on a patch for either a feature branch or a
major branch, if you name the patch with the branch name following the spec in HowToContribute
(and a few other ways... test-patch tries to figure it out!), test-patch.sh *should* be switching
the repo over to that branch for testing. 

	For example,  naming a patch foo-branch-2.01.patch should get tested on branch-2.  Naming
a patch foo-HDFS-7285.00.patch should get tested on the HDFS-7285 branch.

	This hopefully means that there should really be no more 'blind' +1's to patches that go
to branches.  The "we only test against trunk" argument is no longer valid. :)



Mime
View raw message