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 <vino...@apache.org>
wrote:

> Thanks for reporting this.
>
> It's straight forward. Done, commit pushed.
>
> Thanks
> +Vinod
>
> > On Mar 19, 2018, at 2:54 PM, Jonathan Kelly <jonathaka...@gmail.com>
> 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 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 Mon, Mar 19, 2018 at 11:43 AM Arpit Agarwal <aagar...@hortonworks.com
> >
> > wrote:
> >
> >> Thanks Wangda.
> >>
> >>
> >> On 3/19/18, 11:38 AM, "Wangda Tan" <wheele...@gmail.com> 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. Support NOT_SELF and ALL namespace types for
> allocation
> >> tag.
> >>(Weiwe
> >>i Yang via wangda)
> >>
> >>HADOOP-15262. AliyunOSS: move files under a directory in parallel
> >> when
> >>rename a directory. Contributed by Jinhu Wu.
> >>
> >>MAPREDUCE-7066. TestQueue fails on Java9
> >>
> >>YARN-8028. Support authorizeUserAccessToQueue in RMWebServices.
> >>Contributed by Wangda Tan.
> >>
> >>YARN-8040. [UI2] New YARN UI webapp does not respect current
> >> pathname
> >>for REST api. Contributed by Sunil G.
> >>
> >>Thanks,
> >>Wangda
> >>
> >>On Mon, Mar 19, 2018 at 11:12 AM, Wangda Tan <wheele...@gmail.com>
> >> wrote:
> >>
> >>> 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 <
> >> ajisa...@oss.nttdata.co.jp
> >>>> wrote:
> >>>
> >>>> +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 go ahead to do the branch replace.
> >>>>>
> >>>>> Since we don't have force push permission to release branches. I
> >> just
> >>>>> filed
> >>>>> https://issues.apache.org/jira/browse/INFRA-16204 to get help from
> >>>>> Apache
> >>>>> infra team.
> >>>>>
> >>>>> Please hold any commits to branch-3.1, will keep this email thread
> >>>>> posted.
> >>>>>
> >>>>> Best,
> >>>>> Wangda
> >>>>>
> >>>>> On Wed, Mar 14, 2018 at 3:14 PM, Vinod Kumar Vavilapalli <
> >>>>> vino...@apache.org
> >>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>
> >>>>> 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,
> >>>>>> https://issues.apache.org/jira/browse/YARN-7891 and
> >>>>>> https://issues.apache.org/jira/browse/YARN-

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 Mon, Mar 19, 2018 at 11:43 AM Arpit Agarwal 
wrote:

> 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. Support NOT_SELF and ALL namespace types for allocation
> tag.
> (Weiwe
> i Yang via wangda)
>
> HADOOP-15262. AliyunOSS: move files under a directory in parallel
> when
> rename a directory. Contributed by Jinhu Wu.
>
> MAPREDUCE-7066. TestQueue fails on Java9
>
> YARN-8028. Support authorizeUserAccessToQueue in RMWebServices.
> Contributed by Wangda Tan.
>
> YARN-8040. [UI2] New YARN UI webapp does not respect current
> pathname
> for REST api. Contributed by Sunil G.
>
> Thanks,
> Wangda
>
> On Mon, Mar 19, 2018 at 11:12 AM, Wangda Tan 
> wrote:
>
> > 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 <
> ajisa...@oss.nttdata.co.jp
> > > wrote:
> >
> >> +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 go ahead to do the branch replace.
> >>>
> >>> Since we don't have force push permission to release branches. I
> just
> >>> filed
> >>> https://issues.apache.org/jira/browse/INFRA-16204 to get help from
> >>> Apache
> >>> infra team.
> >>>
> >>> Please hold any commits to branch-3.1, will keep this email thread
> >>> posted.
> >>>
> >>> Best,
> >>> Wangda
> >>>
> >>> On Wed, Mar 14, 2018 at 3:14 PM, Vinod Kumar Vavilapalli <
> >>> vino...@apache.org
> >>>
>  wrote:
> 
> >>>
> >>> 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,
>  https://issues.apache.org/jira/browse/YARN-7891 and
>  https://issues.apache.org/jira/browse/YARN-5015. These should be
> okay -
>  not major disrupting features.
> 
>  Everything else is either a bug-fix or an improvement so we
> should be
>  good.
> 
>   From the list, it doesn't look like resetting will destabilize
> 3.1, +1
>  for
>  doing this.
> 
>  Thanks
>  +Vinod
> 
>  On Mar 14, 2018, at 1:54 PM, Wangda Tan 
> wrote:
> >
> > Hi mapreduce/yarn/common/hdfs-devs,
> >
> > As of now, we have all blockers done for 3.1.0 release [1]. The
> release
> >
>  is running behind schedule due to a few security-related issues.
>  Because of
>  this and since branch-3.1 is cut 5 weeks before on Feb 8, trunk
> 3.2 is
>  already diverging. There're 64 commits in trunk but not in
> branch-3.1.
>  [2]
> 
> >
> > I took a quick scan of them, most of them are good fixes which we
> > should
> >
>  bring to 3.1.0 as well. And this can also reduce differences
> between
>  3.2.0
>  and 3.1.0 release for less maintenance burden in the future.
> 
> >
> > Unless anyone objects, we will reset branch-3.1 to trunk in 1-2
> days
> > and
> >
>  cut RC after that.
> 
> >
> > Thoughts?
> >
> > - Wangda
> >
> > [1] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in
> > (Blocker,
> >
>  Critical) AND resolution = Unresolved AND "Target Version/s" =
> 3.1.0
>  ORDER
>  BY priority DESC
> 
> > [2] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND fixVersion in
>

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

2017-12-19 Thread Jonathan Kelly 
Thanks, Andrew!

On Mon, Dec 18, 2017 at 4:54 PM Andrew Wang <andrew.w...@cloudera.com>
wrote:

> Thanks for the spot, I just pushed a correct tag. I can't delete the bad
> tag myself, will ask ASF infra for help.
>
> On Mon, Dec 18, 2017 at 4:46 PM, Jonathan Kelly <jonathaka...@gmail.com>
> wrote:
>
>> Congrats on the huge release!
>>
>> I just noticed, though, that the Github repo does not appear to have the
>> correct tag for 3.0.0. I see a new tag called "rel/release-" that points to
>> the same commit as "release-3.0.0-RC1"
>> (c25427ceca461ee979d30edd7a4b0f50718e6533). I assume that should have
>> actually been called "rel/release-3.0.0" to match the pattern for prior
>> releases.
>>
>> Thanks,
>> Jonathan Kelly
>>
>> On Thu, Dec 14, 2017 at 10:45 AM Andrew Wang <andrew.w...@cloudera.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> I'm pleased to announce that Apache Hadoop 3.0.0 is generally available
>>> (GA).
>>>
>>> 3.0.0 GA consists of 302 bug fixes, improvements, and other enhancements
>>> since 3.0.0-beta1. This release marks a point of quality and stability
>>> for
>>> the 3.0.0 release line, and users of earlier 3.0.0-alpha and -beta
>>> releases
>>> are encouraged to upgrade.
>>>
>>> Looking back, 3.0.0 GA is the culmination of over a year of work on the
>>> 3.0.0 line, starting with 3.0.0-alpha1 which was released in September
>>> 2016. Altogether, 3.0.0 incorporates 6,242 changes since 2.7.0.
>>>
>>> Users are encouraged to read the overview of major changes
>>> <http://hadoop.apache.org/docs/r3.0.0/index.html> in 3.0.0. The GA
>>> release
>>> notes
>>> <
>>> http://hadoop.apache.org/docs/r3.0.0/hadoop-project-dist/hadoop-common/release/3.0.0/RELEASENOTES.3.0.0.html
>>> >
>>>  and changelog
>>> <
>>> http://hadoop.apache.org/docs/r3.0.0/hadoop-project-dist/hadoop-common/release/3.0.0/CHANGES.3.0.0.html
>>> >
>>> detail
>>> the changes since 3.0.0-beta1.
>>>
>>> The ASF press release provides additional color and highlights some of
>>> the
>>> major features:
>>>
>>>
>>> https://globenewswire.com/news-release/2017/12/14/1261879/0/en/The-Apache-Software-Foundation-Announces-Apache-Hadoop-v3-0-0-General-Availability.html
>>>
>>> Let me end by thanking the many, many contributors who helped with this
>>> release line. We've only had three major releases in Hadoop's 10 year
>>> history, and this is our biggest major release ever. It's an incredible
>>> accomplishment for our community, and I'm proud to have worked with all
>>> of
>>> you.
>>>
>>> Best,
>>> Andrew
>>>
>>
>

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

2017-12-18 Thread Jonathan Kelly 
Congrats on the huge release!

I just noticed, though, that the Github repo does not appear to have the
correct tag for 3.0.0. I see a new tag called "rel/release-" that points to
the same commit as "release-3.0.0-RC1"
(c25427ceca461ee979d30edd7a4b0f50718e6533). I assume that should have
actually been called "rel/release-3.0.0" to match the pattern for prior
releases.

Thanks,
Jonathan Kelly

On Thu, Dec 14, 2017 at 10:45 AM Andrew Wang <andrew.w...@cloudera.com>
wrote:

> Hi all,
>
> I'm pleased to announce that Apache Hadoop 3.0.0 is generally available
> (GA).
>
> 3.0.0 GA consists of 302 bug fixes, improvements, and other enhancements
> since 3.0.0-beta1. This release marks a point of quality and stability for
> the 3.0.0 release line, and users of earlier 3.0.0-alpha and -beta releases
> are encouraged to upgrade.
>
> Looking back, 3.0.0 GA is the culmination of over a year of work on the
> 3.0.0 line, starting with 3.0.0-alpha1 which was released in September
> 2016. Altogether, 3.0.0 incorporates 6,242 changes since 2.7.0.
>
> Users are encouraged to read the overview of major changes
> <http://hadoop.apache.org/docs/r3.0.0/index.html> in 3.0.0. The GA release
> notes
> <
> http://hadoop.apache.org/docs/r3.0.0/hadoop-project-dist/hadoop-common/release/3.0.0/RELEASENOTES.3.0.0.html
> >
>  and changelog
> <
> http://hadoop.apache.org/docs/r3.0.0/hadoop-project-dist/hadoop-common/release/3.0.0/CHANGES.3.0.0.html
> >
> detail
> the changes since 3.0.0-beta1.
>
> The ASF press release provides additional color and highlights some of the
> major features:
>
>
> https://globenewswire.com/news-release/2017/12/14/1261879/0/en/The-Apache-Software-Foundation-Announces-Apache-Hadoop-v3-0-0-General-Availability.html
>
> Let me end by thanking the many, many contributors who helped with this
> release line. We've only had three major releases in Hadoop's 10 year
> history, and this is our biggest major release ever. It's an incredible
> accomplishment for our community, and I'm proud to have worked with all of
> you.
>
> Best,
> Andrew
>