Tx for the feedback! Let's continue on JIRA, but I'd definitely welcome as much
help as is available.
Thanks,
+Vinod
On Mar 4, 2015, at 3:30 PM, Zhijie Shen zs...@hortonworks.com wrote:
+1. It¹s really helpful for branch development. To continue Karthik¹s
point, is it good make pre-commit
Thanks for reviving this on email, Vinod. Newer folks like me might not be
aware of this JIRA/effort.
This would be wonderful to have so (1) we know the status of release
branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
Jonathan's or Matt's proposal for including branch name
Hi all,
I'd like us to revive the effort at
https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit builds
being able to work with branches. Having the Jenkins verify patches on branches
is very useful even if there may be relaxed review oversight on the said-branch.
Unless there
+1
If we can make things look like HBase support for precommit testing on
branches (HBASE-12944), that would make it easier for new and occasional
contributors who might end up working in other ecosystem projects. AFAICT,
Jonathan's proposal for branch names in patch names does this.
On Wed,
+1. It¹s really helpful for branch development. To continue Karthik¹s
point, is it good make pre-commit testing against branch-2 as the default
too like that against trunk?
On 3/4/15, 1:47 PM, Sean Busbey bus...@cloudera.com wrote:
+1
If we can make things look like HBase support for precommit
