Re: About reset branch-3.1 to trunk before release.

2018-03-20 Thread Wangda Tan
.com] > Sent: Tuesday, March 20, 2018 2:38 AM > To: Akira Ajisaka <ajisa...@oss.nttdata.co.jp> > Cc: Vinod Kumar Vavilapalli <vino...@apache.org>; > yarn-...@hadoop.apache.org; Hdfs-dev <hdfs-...@hadoop.apache.org>; > common-dev@hadoop.apache.org; mapreduce-...@hadoop.apac

RE: About reset branch-3.1 to trunk before release.

2018-03-19 Thread Chen, Sammi
rg>; common-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org Subject: Re: About reset branch-3.1 to trunk before release. Done JIRA fix version update: Moved all JIRAs with fixVersion = 3.2.0 to 3.1.0 except following few fixes (which committed after 49c747ab187d0650143205ba57ca19607ec4c6

Re: About reset branch-3.1 to trunk before release.

2018-03-19 Thread Jonathan Kelly
Thank you! On Mon, Mar 19, 2018 at 3:34 PM Vinod Kumar Vavilapalli wrote: > Thanks for reporting this. > > It's straight forward. Done, commit pushed. > > Thanks > +Vinod > > > On Mar 19, 2018, at 2:54 PM, Jonathan Kelly > wrote: > > > > I just

Re: About reset branch-3.1 to trunk before release.

2018-03-19 Thread Vinod Kumar Vavilapalli
Thanks for reporting this. It's straight forward. Done, commit pushed. Thanks +Vinod > On Mar 19, 2018, at 2:54 PM, Jonathan Kelly wrote: > > I just pulled the latest from branch-3.1 and noticed that now that it was > reset to trunk, the version in the pom.xml files is

Re: About reset branch-3.1 to trunk before release.

2018-03-19 Thread Jonathan Kelly
I just pulled the latest from branch-3.1 and noticed that now that it was reset to trunk, the version in the pom.xml files is 3.2.0-SNAPSHOT instead of 3.1.0-SNAPSHOT. Is somebody going to submit a new commit to change this version back to 3.1.0-SNAPSHOT in this branch? Thank you, Jonathan On

Re: About reset branch-3.1 to trunk before release.

2018-03-19 Thread Arpit Agarwal
Thanks Wangda. On 3/19/18, 11:38 AM, "Wangda Tan" wrote: Done JIRA fix version update: Moved all JIRAs with fixVersion = 3.2.0 to 3.1.0 except following few fixes (which committed after 49c747ab187d0650143205ba57ca19607ec4c6bd) YARN-8002.

Re: About reset branch-3.1 to trunk before release.

2018-03-19 Thread Wangda Tan
Done JIRA fix version update: Moved all JIRAs with fixVersion = 3.2.0 to 3.1.0 except following few fixes (which committed after 49c747ab187d0650143205ba57ca19607ec4c6bd) YARN-8002. Support NOT_SELF and ALL namespace types for allocation tag. (Weiwe i Yang via wangda) HADOOP-15262.

Re: About reset branch-3.1 to trunk before release.

2018-03-19 Thread Wangda Tan
Thanks Akira for the additional vote, With help from Apache Infra Team (Daniel Takamori), we just reset branch-3.1 to trunk (SHA: 49c747ab187d0650143205ba57ca19607ec4c6bd). Will update JIRA fix version shortly. - Wangda On Sun, Mar 18, 2018 at 6:10 PM, Akira Ajisaka

Re: About reset branch-3.1 to trunk before release.

2018-03-18 Thread Akira Ajisaka
+1 for resetting branch-3.1. Thanks, Akira On 2018/03/18 12:51, Wangda Tan wrote: Thanks for sharing your thoughts. We have done build and single node cluster deploy / test for the latest trunk code (commit: 49c747ab187d0650143205ba57ca19607ec4c6bd). Since there are no objections, so I will

Re: About reset branch-3.1 to trunk before release.

2018-03-17 Thread Wangda Tan
Thanks for sharing your thoughts. We have done build and single node cluster deploy / test for the latest trunk code (commit: 49c747ab187d0650143205ba57ca19607ec4c6bd). Since there are no objections, so I will go ahead to do the branch replace. Since we don't have force push permission to

Re: About reset branch-3.1 to trunk before release.

2018-03-14 Thread Vinod Kumar Vavilapalli
I see one new feature: https://issues.apache.org/jira/browse/YARN-7626: Allow regular expression matching in container-executor.cfg for devices and named docker volumes mount. There are 21 sub-tasks. There are three feature-type JIRAs in those - https://issues.apache.org/jira/browse/YARN-7972,