Looking forward to the release.  What's the state of the application
history server?  Do we have security, documentation, and are APIs stable?
 If not, do we have a plan for how to make this clear to users?

What about the timeline store?

thanks,
Sandy


On Fri, Mar 14, 2014 at 8:23 PM, Arun C Murthy <a...@hortonworks.com> wrote:

> Update: We are now down to just 8 blockers of which 4 are already PA.
>
> I know it's getting in good shape per our QE gang too. If things go well,
> I plan to create an RC later half of next week.
>
> thanks,
> Arun
>
> On Mar 11, 2014, at 7:11 AM, Arun C Murthy <a...@hortonworks.com> wrote:
>
> > Sorry, the previous link had a bug, the correct one is:
> http://s.apache.org/hadoop-2.4.0-blockers.
> >
> > We are currently down to 12 blockers; with several PA.
> >
> > thanks,
> > Arun
> >
> > On Mar 6, 2014, at 1:40 PM, Arun C Murthy <a...@hortonworks.com> wrote:
> >
> >> Gang,
> >>
> >>  Most of the big-ticket items are already in, awesome!
> >>
> >>  I'm thinking we could roll out a 2.4 RC in the next 2-3 weeks after we
> get through the list of blockers. Here is a handy link:
> http://s.apache.org/hadoop-2.4-blockers
> >>
> >>  If you find more, please set Target Version to 2.4.0 and mark it a
> blocker. I'll try nudging people to start closing these soon, appreciate
> any help!
> >>
> >> thanks,
> >> Arun
> >>
> >>
> >> On Feb 20, 2014, at 3:45 PM, Arun C Murthy <a...@hortonworks.com> wrote:
> >>
> >>> Thanks Azuryy & Suresh. I've updated the roadmap wiki to reflect this.
> >>>
> >>> Arun
> >>>
> >>> On Feb 20, 2014, at 2:01 PM, Suresh Srinivas <sur...@hortonworks.com>
> wrote:
> >>>
> >>>> Arun,
> >>>>
> >>>> Some of the previously 2.4 targeted features were made available in
> 2.3:
> >>>> - Heterogeneous storage support
> >>>> - Datanode cache
> >>>>
> >>>> The following are being targeted for 2.4:
> >>>> - Use protobuf for fsimge (already in)
> >>>> - ACLs (in trunk. In a week or so, this will be merged to branch-2.4)
> >>>> - Rolling upgrades (last bunch of jiras being worked in feature
> branch.
> >>>> Will be in 2.4 in around two weeks. Currently testing is in progress)
> >>>>
> >>>> So HDFS features should be ready in two weeks.
> >>>>
> >>>>
> >>>> On Sat, Feb 15, 2014 at 4:47 PM, Azuryy <azury...@gmail.com> wrote:
> >>>>
> >>>>> Hi,
> >>>>> I think you omit some key pieces in 2.4
> >>>>>
> >>>>> Protobuf fsimage, rolling upgrade are also targeting 2.4
> >>>>>
> >>>>>
> >>>>>
> >>>>> Sent from my iPhone5s
> >>>>>
> >>>>>> On 2014年2月16日, at 6:59, Arun C Murthy <a...@hortonworks.com> wrote:
> >>>>>>
> >>>>>> Folks,
> >>>>>>
> >>>>>> With hadoop-2.3 nearly done, I think it's time to think ahead to
> >>>>> hadoop-2.4. I think it was a good idea to expedite release of 2.3
> while we
> >>>>> finished up pieces that didn't make it in such as HDFS Caching &
> Support
> >>>>> for Heterogenous Storage.
> >>>>>>
> >>>>>> Now, most of the key pieces incl. Resource Manager Automatic
> Failover
> >>>>> (YARN-149), Application History Server (YARN-321) & Application
> Timeline
> >>>>> Server (YARN-1530) are either complete or very close to done, and I
> think
> >>>>> we will benefit with an extended test-cycle for 2.4 - similar to what
> >>>>> happened with 2.2. To provide some context: 2.2 went through nearly
> 6 weeks
> >>>>> of extended testing and it really helped us push out a very stable
> release.
> >>>>>>
> >>>>>> I think it will be good to create a 2.4 branch ASAP and start
> testing.
> >>>>> As such, I plan to cut the branch early next week. With this, we
> should be
> >>>>> good shape sometime to release 2.4 in mid-March.
> >>>>>>
> >>>>>> I've updated https://wiki.apache.org/hadoop/Roadmap to reflect
> this.
> >>>>>>
> >>>>>> Also, we should start thinking ahead to 2.5 and what folks would
> like to
> >>>>> see in it. If we continue our 6-week cycles, we could shoot to get
> that out
> >>>>> in April.
> >>>>>>
> >>>>>> Thoughts?
> >>>>>>
> >>>>>> thanks,
> >>>>>> Arun
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Arun C. Murthy
> >>>>>> Hortonworks Inc.
> >>>>>> http://hortonworks.com/
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> CONFIDENTIALITY NOTICE
> >>>>>> NOTICE: This message is intended for the use of the individual or
> entity
> >>>>> to
> >>>>>> which it is addressed and may contain information that is
> confidential,
> >>>>>> privileged and exempt from disclosure under applicable law. If the
> reader
> >>>>>> of this message is not the intended recipient, you are hereby
> notified
> >>>>> that
> >>>>>> any printing, copying, dissemination, distribution, disclosure or
> >>>>>> forwarding of this communication is strictly prohibited. If you have
> >>>>>> received this communication in error, please contact the sender
> >>>>> immediately
> >>>>>> and delete it from your system. Thank You.
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> http://hortonworks.com/download/
> >>>>
> >>>> --
> >>>> CONFIDENTIALITY NOTICE
> >>>> NOTICE: This message is intended for the use of the individual or
> entity to
> >>>> which it is addressed and may contain information that is
> confidential,
> >>>> privileged and exempt from disclosure under applicable law. If the
> reader
> >>>> of this message is not the intended recipient, you are hereby
> notified that
> >>>> any printing, copying, dissemination, distribution, disclosure or
> >>>> forwarding of this communication is strictly prohibited. If you have
> >>>> received this communication in error, please contact the sender
> immediately
> >>>> and delete it from your system. Thank You.
> >>>
> >>> --
> >>> Arun C. Murthy
> >>> Hortonworks Inc.
> >>> http://hortonworks.com/
> >>>
> >>>
> >>
> >> --
> >> Arun C. Murthy
> >> Hortonworks Inc.
> >> http://hortonworks.com/
> >>
> >>
> >
> > --
> > Arun C. Murthy
> > Hortonworks Inc.
> > http://hortonworks.com/
> >
> >
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to