Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of tucu@cloudera.com designates
 209.85.128.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2B5DE8AB-223F-4762-938F-FF9FB104160D@hortonworks.com>
References: 
 <CAJs-t7PXT3mULHCHs4XBR142w70Ohiv9g_HqVix=xeeoZgjdiw@mail.gmail.com>
 <CADdVdVEpAOqz1PZ521Li_DwSbpLi_k+nRaqaxUb07gxNJ8KpMw@mail.gmail.com>
 <CAJs-t7PPx5zh3gYTHPW9nfDN32aiH88SfTdCC1YGGSM69nTLOg@mail.gmail.com>
 <51D34868.6040603@yahoo-inc.com>
 <CAJs-t7P37GAQGGFKZ6Kfy1nSyioPfLZaB6m_TMLobS0CukZ=PA@mail.gmail.com>
 <2B5DE8AB-223F-4762-938F-FF9FB104160D@hortonworks.com>
From: Alejandro Abdelnur <tucu@cloudera.com>
Date: Wed, 10 Jul 2013 10:56:27 -0700
Message-ID: 
 <CAJs-t7NAGRzZZFKA0yCQaKEQynW13ydvn+8pNKW6KuRs1TrLtQ@mail.gmail.com>
Subject: Re: creating 2.2.0 version in JIRA
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=089e0149cda4f82a7004e12c0008

--089e0149cda4f82a7004e12c0008
Content-Type: text/plain; charset=ISO-8859-1

If that is the case, then I'll like to push the following JIRAs that have
been committed to branch-2 to branch-2.1 when the first RC was just out and
we didn't know that many more things would come in.

I'm planning to push these JIRAs mid afternoon PST today. If there is any
that should not make it, please speak up.

Thanks.

----------------
common:

    HADOOP-9661. Allow metrics sources to be extended. (sandyr via tucu)

    HADOOP-9370.  Write FSWrapper class to wrap FileSystem and FileContext
for
    better test coverage.  (Andrew Wang via Colin Patrick McCabe)

    HADOOP-9355.  Abstract symlink tests to use either FileContext or
    FileSystem.  (Andrew Wang via Colin Patrick McCabe)

    HADOOP-9673.  NetworkTopology: when a node can't be added, print out its
    location for diagnostic purposes.  (Colin Patrick McCabe)

    HADOOP-9414.  Refactor out FSLinkResolver and relevant helper methods.
    (Andrew Wang via Colin Patrick McCabe)

    HADOOP-9416.  Add new symlink resolution methods in FileSystem and
    FileSystemLinkResolver.  (Andrew Wang via Colin Patrick McCabe)


hdfs:

    HDFS-4908. Reduce snapshot inode memory usage.  (szetszwo)

yarn:

    YARN-866. Add test for class ResourceWeights. (ywskycn via tucu)

    YARN-736. Add a multi-resource fair sharing metric. (sandyr via tucu)

    YARN-883. Expose Fair Scheduler-specific queue metrics. (sandyr via
tucu)

mapreduce:

    MAPREDUCE-5333. Add test that verifies MRAM works correctly when sending
    requests with non-normalized capabilities. (ywskycn via tucu)

----------------


On Tue, Jul 9, 2013 at 10:54 AM, Arun C Murthy <acm@hortonworks.com> wrote:

>
> On Jul 2, 2013, at 3:54 PM, Alejandro Abdelnur <tucu@cloudera.com> wrote:
>
> > We need clarification on this then.
> >
> > I was under the impression that branch-2 would be 2.2.0.
>
> Sorry, I missed this thread - thanks to Jason for pointing me.
>
> As we discussed, the idea was that we are not adding new features to the
> the beta release (2.1.x-beta) so that we can focus on stabilizing it and
> releasing as hadoop-2.2.0 i.e. GA of hadoop-2. See http://s.apache.org/lZ8
> .
>
> Hence, by default, new features goto branch-2 with fix-version as 2.3.x.
>
> Hope that makes sense. I'll fix branch-2 to set version to 2.3.0-SNAPSHOT
> to ease further confusion.
>
> thanks,
> Arun
>
> >
> > thx
> >
> > On Tue, Jul 2, 2013 at 2:38 PM, Jason Lowe <jlowe@yahoo-inc.com> wrote:
> >
> >> I thought Arun intends for 2.2.0 to be created off of branch-2.1.0-beta
> >> and not off of branch-2.  As I understand it, only critical blockers
> will
> >> be the delta between 2.1.0-beta and 2.2.0 and items checked into
> branch-2
> >> should be marked as  fixed in 2.3.0.
> >>
> >> Part of the confusion is that currently branch-2 builds as
> 2.2.0-SNAPSHOT,
> >> but I believe Arun intended it to be 2.3.0-SNAPSHOT.
> >>
> >> Jason
> >>
> >>
> >> On 06/21/2013 12:05 PM, Alejandro Abdelnur wrote:
> >>
> >>> Thanks Suresh, didn't know that, will do.
> >>>
> >>>
> >>> On Fri, Jun 21, 2013 at 9:48 AM, Suresh Srinivas <
> suresh@hortonworks.com
> >>>> wrote:
> >>>
> >>> I have added in to HDFS, HADOOP, MAPREDUCE projects. Can someone add it
> >>>> for
> >>>> YARN?
> >>>>
> >>>>
> >>>> On Fri, Jun 21, 2013 at 9:35 AM, Alejandro Abdelnur <
> tucu@cloudera.com
> >>>>
> >>>>> wrote:
> >>>>> When Arun created branch-2.1-beta he stated:
> >>>>>
> >>>>> The expectation is that 2.2.0 will be limited to content in
> >>>>>>
> >>>>> branch-2.1-beta
> >>>>>
> >>>>>> and we stick to stabilizing it henceforth (I've deliberately not
> >>>>>>
> >>>>> created
> >>>>
> >>>>> 2.2.0
> >>>>>
> >>>>>> fix-version on jira yet).
> >>>>>>
> >>>>> I working/committing some JIRAs that I'm putting in branch-2
> (testcases
> >>>>>
> >>>> and
> >>>>
> >>>>> improvements) but I don't want to put them in branch-2.1-beta as they
> >>>>> are
> >>>>> not critical and I don't won't add unnecessary noise to the
> >>>>>
> >>>> branch-2.1-beta
> >>>>
> >>>>> release work.
> >>>>>
> >>>>> Currently branch-2 POMs have a version 2.2.0 and the CHANGES.txt
> files
> >>>>> as
> >>>>> well.
> >>>>>
> >>>>> But because we did not create a JIRA version I cannot close those
> JIRAs.
> >>>>>
> >>>>> Can we please create the JIRA versions? later we can rename them.
> >>>>>
> >>>>> Thx
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Alejandro
> >>>>>
> >>>>>
> >>>>
> >>>> --
> >>>> http://hortonworks.com/**download/ <http://hortonworks.com/download/>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >
> >
> > --
> > Alejandro
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>
>


-- 
Alejandro

--089e0149cda4f82a7004e12c0008--