hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arun Suresh <asur...@cloudera.com>
Subject Re: 2.7 status
Date Thu, 09 Apr 2015 18:41:14 GMT
Hey Vinod,

I was wondering if you can include
https://issues.apache.org/jira/browse/HDFS-8091 too.. Without it, i kinda
makes https://issues.apache.org/jira/browse/HDFS-6826 incomplete..

Cheers
-Arun Suresh

On Thu, Apr 9, 2015 at 11:37 AM, Vinod Kumar Vavilapalli <
vinodkv@hortonworks.com> wrote:

> A couple of weeks late, but we are here.
>
> There is one last blocker that I am about to commit in a little while.
>
> I am starting the release process.
>
> +Vinod
>
> On Mar 25, 2015, at 9:53 AM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
>
> > Progress has been really slow, but now we are down to four blockers
> across the board.
> >
> > I plan to roll an RC this weekend.
> >
> > Thanks,
> > +Vinod
> >
> > On Mar 8, 2015, at 8:40 PM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
> >
> >> 2.7 branch created and branch-2 updated to point to 2.8-SNAPSHOT.
> >>
> >> Committers, please exercise caution on the content going into
> branch-2.7. I'd take help everyone's help in pushing through the remaining
> set of blockers targeted for 2.7.
> >>
> >> Thanks,
> >> +Vinod
> >>
> >> On Mar 8, 2015, at 8:21 PM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
> >>
> >>> Branching 2.7 now. Request holding off commits to branch-2 to avoid
> commit race. Will send an all-clear in the next 30 mins once I am done.
> >>>
> >>> Thanks
> >>> +Vinod
> >>>
> >>> On Mar 5, 2015, at 1:56 PM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
> >>>
> >>>>
> >>>> The 2.7 blocker JIRA went down and going back up again, we will need
> to converge.
> >>>>
> >>>> Unless I see objections, I plan to cut a branch this weekend and
> selectively filter stuff in after that in the interest of convergence.
> >>>>
> >>>> Thoughts welcome!
> >>>>
> >>>> Thanks,
> >>>> +Vinod
> >>>>
> >>>> On Mar 1, 2015, at 11:58 AM, Arun Murthy <acm@hortonworks.com>
wrote:
> >>>>
> >>>>> Sounds good, thanks for the help Vinod!
> >>>>>
> >>>>> Arun
> >>>>>
> >>>>> ________________________________________
> >>>>> From: Vinod Kumar Vavilapalli
> >>>>> Sent: Sunday, March 01, 2015 11:43 AM
> >>>>> To: Hadoop Common; Jason Lowe; Arun Murthy
> >>>>> Subject: Re: 2.7 status
> >>>>>
> >>>>> Agreed. How about we roll an RC end of this week? As a Java 7+
> release with features, patches that already got in?
> >>>>>
> >>>>> Here's a filter tracking blocker tickets -
> https://issues.apache.org/jira/issues/?filter=12330598. Nine open now.
> >>>>>
> >>>>> +Arun
> >>>>> Arun, I'd like to help get 2.7 out without further delay. Do you
> mind me taking over release duties?
> >>>>>
> >>>>> Thanks,
> >>>>> +Vinod
> >>>>> ________________________________________
> >>>>> From: Jason Lowe <jlowe@yahoo-inc.com.INVALID>
> >>>>> Sent: Friday, February 13, 2015 8:11 AM
> >>>>> To: common-dev@hadoop.apache.org
> >>>>> Subject: Re: 2.7 status
> >>>>>
> >>>>> I'd like to see a 2.7 release sooner than later.  It has been almost
> 3 months since Hadoop 2.6 was released, and there have already been 634
> JIRAs committed to 2.7.  That's a lot of changes waiting for an official
> release.
> >>>>>
> https://issues.apache.org/jira/issues/?jql=project%20in%20%28hadoop%2Chdfs%2Cyarn%2Cmapreduce%29%20AND%20fixversion%3D2.7.0%20AND%20resolution%3DFixed
> >>>>> Jason
> >>>>>
> >>>>>  From: Sangjin Lee <sjlee@apache.org>
> >>>>> To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
> >>>>> Sent: Tuesday, February 10, 2015 1:30 PM
> >>>>> Subject: 2.7 status
> >>>>>
> >>>>> Folks,
> >>>>>
> >>>>> What is the current status of the 2.7 release? I know initially
it
> started
> >>>>> out as a "java-7" only release, but looking at the JIRAs that is
> very much
> >>>>> not the case.
> >>>>>
> >>>>> Do we have a certain timeframe for 2.7 or is it time to discuss
it?
> >>>>>
> >>>>> Thanks,
> >>>>> Sangjin
> >>>>>
> >>>>
> >>>
> >>
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message