Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: neutral (athena.apache.org: 216.145.54.173 is neither permitted
 nor denied by domain of tgraves@yahoo-inc.com)
From: Thomas Graves <tgraves@yahoo-inc.com>
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>,
        "mattf@apache.org" <mattf@apache.org>
Date: Mon, 30 Apr 2012 16:29:30 -0500
Subject: Re: Hadoop-1.0.3 and 1.1 release / code freeze proposals
Thread-Topic: Hadoop-1.0.3 and 1.1 release / code freeze proposals
Thread-Index: Ac0fWomOfGvSVxSgTIKDgmg+roYWlwHvcodo
Message-ID: <CBC46E6A.2902B%tgraves@yahoo-inc.com>
In-Reply-To: 
 <CA+z3+9FK9qNqCXpkaYF6yQt+bTzFdCQrsp+yGZMpFxBs=irChA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.9.0.110114
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

You might consider pulling in these 4 jira. The are all minor but aid in
debugging: MAPREDUCE-4012, MAPREDUCE-4003,  MAPREDUCE-1238, and
MAPREDUCE-4017.  These are all already in 1.1.0.

Tom


On 4/20/12 8:02 PM, "Matt Foley" <mattf@apache.org> wrote:

> Hi all,
> a couple major bugs have shown up in Hadoop-1.0.2.  I propose to make a
> 1.0.3 release containing fixes for:
>   - MAPREDUCE-4154
> <https://issues.apache.org/jira/browse/MAPREDUCE-4154> streaming
> MR job succeeds even if the streaming command fails
>   - HDFS-119 <https://issues.apache.org/jira/browse/HDFS-119> logSync() m=
ay
> block NameNode forever.
> We will also accept the following bug fixes already committed to branch-1=
.0
> (see
> CHANGES.txt): HADOOP-6924, HADOOP-6941, HADOOP-8188, HDFS-3127,
> MAPREDUCE-3377, HADOOP-5528, HADOOP-6963, HADOOP-8251, HADOOP-8293.
>=20
> If there are other critical bugs you would like to see in 1.0.3, please l=
et
> me know by end of day Monday, 4/23.  I'll start the process of making a
> 1.0.3 RC-1 on Tuesday.
>=20
> Also, it seems that it is time to do a 1.1 release.  Some 80 bug fixes an=
d
> enhancements have accumulated in branch-1.  Hopefully they've all been
> properly reviewed and unit tested!  Let's declare a code freeze for 1.1 a=
t
> the end of this month.  At that time I will make a branch-1.1 and a relea=
se
> candidate for 1.1.0.
>=20
> Thank you,
> --Matt