I just went through and fixed up the HDFS and Common CHANGES.txt for 2.5.0.

As a friendly reminder, please try to put things under the correct section
:) We have subsections for the xattr changes in HDFS-2006 and HADOOP-10514,
and there were some unrelated JIRAs appended to the end.

I'd also encourage committers to be more liberal with their use of the NEW
FEATURES section. I'm helping Karthik write up the 2.5 release notes, and
I'm using NEW FEATURES to fill it out. When looking through the JIRA list
though, I decided to promote things like the SNN/DN/JN webUI improvements,
the HCFS specification work, and OIV read-only WebHDFS access to new
features. One rule-of-thumb, if a feature required an umbrella JIRA, put
the umbrella under NEW FEATURES when it's resolved.

Thanks,
Andrew


On Wed, Jul 16, 2014 at 7:59 PM, Wangda Tan <wheele...@gmail.com> wrote:

> Thanks Tsuyoshi for pointing me this,
>
> Wangda
>
>
> On Thu, Jul 17, 2014 at 10:30 AM, Tsuyoshi OZAWA <ozawa.tsuyo...@gmail.com
> >
> wrote:
>
> > Hi Wangda,
> >
> > The following link is same link as Karthik mentioned:
> >
> >
> >
> https://issues.apache.org/jira/browse/YARN-2247?jql=project%20in%20(Hadoop%2C%20HDFS%2C%20YARN%2C%20%22Hadoop%20Map%2FReduce%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20%22Target%20Version%2Fs%22%20%3D%202.5.0%20AND%20priority%20in%20(Blocker)
> >
> > Or, please access to http://goo.gl/FX3iWp
> >
> > Thanks,
> > - Tsuyoshi
> >
> > On Thu, Jul 17, 2014 at 10:55 AM, Zhijie Shen <zs...@hortonworks.com>
> > wrote:
> > > I raised YARN-2247 as the blocker of 2.5.0.
> > >
> > >
> > > On Thu, Jul 17, 2014 at 9:42 AM, Wangda Tan <wheele...@gmail.com>
> wrote:
> > >
> > >> Hi Karthik,
> > >> I found I cannot access the filter: http://s.apache.org/vJg. Could
> you
> > >> please check its permission? I'd like to know if there's any related
> > issues
> > >> to me. :)
> > >>
> > >> Thanks,
> > >> Wangda
> > >>
> > >>
> > >> On Thu, Jul 17, 2014 at 5:54 AM, Karthik Kambatla <ka...@cloudera.com
> >
> > >> wrote:
> > >>
> > >> > We are down to 4 blockers and looks like they are all actively being
> > >> worked
> > >> > on. Please reconsider marking new JIRAs as blockers.
> > >> >
> > >> > Thanks
> > >> > Karthik
> > >> >
> > >> > PS: I moved out a couple of JIRAs that didn't seem like true
> blockers
> > to
> > >> > 2.6.
> > >> >
> > >> >
> > >> > On Wed, Jul 9, 2014 at 11:43 AM, Karthik Kambatla <
> ka...@cloudera.com
> > >
> > >> > wrote:
> > >> >
> > >> > > Folks,
> > >> > >
> > >> > > We have 10 blockers for 2.5. Can the people working on them
> revisit
> > and
> > >> > > see if they are really blockers. If they are, can we try to get
> > them in
> > >> > > soon? It would be nice to get an RC out the end of this week or at
> > >> least
> > >> > > early next week?
> > >> > >
> > >> > > Thanks
> > >> > > Karthik
> > >> > >
> > >> > >
> > >> > > On Wed, Jul 2, 2014 at 11:32 PM, Karthik Kambatla <
> > ka...@cloudera.com>
> > >> > > wrote:
> > >> > >
> > >> > >> I just
> > >> > >> 1. moved non-blocker 2.5 JIRAs to 2.6.
> > >> > >> 2. created branch-2.5 and added sections for 2.6.0 in all
> > CHANGES.txt
> > >> in
> > >> > >> trunk and branch-2.
> > >> > >> 3. Will create branch-2.5.0 when we are ready to create an RC
> > >> > >>
> > >> > >> There are 11 pending blockers for 2.5.0: http://s.apache.org/vJg
> > >> > >>
> > >> > >> Committers - please exercise caution when merging to branch-2.5
> and
> > >> > >> target non-blockers preferably to 2.6
> > >> > >>
> > >> > >>
> > >> > >> On Wed, Jul 2, 2014 at 10:24 PM, Karthik Kambatla <
> > ka...@cloudera.com
> > >> >
> > >> > >> wrote:
> > >> > >>
> > >> > >>> Committers,
> > >> > >>>
> > >> > >>> I am working on branching 2.5. Will send an update as soon as I
> am
> > >> done
> > >> > >>> branching.
> > >> > >>>
> > >> > >>>
> > >> > >>>
> > >> > >>
> > >> > >
> > >> >
> > >>
> > >
> > >
> > >
> > > --
> > > Zhijie Shen
> > > 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.
> >
> >
> >
> > --
> > - Tsuyoshi
> >
>

Reply via email to