Greetings.  With the approval of a public vote on common-dev@, I have
branched Hadoop branch-1 to create branch-1.1.  From this, I will create a
release candidate RC-0 for Hadoop-1.1.0, hopefully to be available shortly
after this weekend.

There are over 80 patches in branch-1, over and above the contents of
hadoop-1.0.3.  So I anticipate that some stabilization will be needed,
before the RC can be approved as a 1.1.0 release.  Your participation in
assuring a stable RC is very important.  When it becomes available, please
download it and work with it to determine whether it is stable enough to
release, and report issues found.  My colleagues and I will do likewise, of
course, but no one company can adequately exercise a new release with this
many new contributions.

There are two outstanding issue that are not yet committed, but I know the
contributors hope to see in 1.1.0:
    MAPREDUCE-4049 <https://issues.apache.org/jira/browse/MAPREDUCE-4049>
    HADOOP-4012 <https://issues.apache.org/jira/browse/HADOOP-4012>
Assuming there is an RC-1, and that these two patches can be committed
during stabilization of RC-0, I will plan to incorporate these additional
items in RC-1.

Best regards,
--Matt
Release Manager

Thanks Matt.  I'd like to get HADOOP-8430 in as well.

(Btw there are 90 issues with target version 1.1.0, perhaps we should move
these to 1.1.1)
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=%22Target+Version%2Fs%22+%3D+%221.1.0%22+and+resolution+%3D+Unresolved

Thanks,
Eli

On Fri, May 25, 2012 at 2:49 PM, Matt Foley <[EMAIL PROTECTED]> wrote:

> Greetings.  With the approval of a public vote on common-dev@, I have
> branched Hadoop branch-1 to create branch-1.1.  From this, I will create a
> release candidate RC-0 for Hadoop-1.1.0, hopefully to be available shortly
> after this weekend.
>
> There are over 80 patches in branch-1, over and above the contents of
> hadoop-1.0.3.  So I anticipate that some stabilization will be needed,
> before the RC can be approved as a 1.1.0 release.  Your participation in
> assuring a stable RC is very important.  When it becomes available, please
> download it and work with it to determine whether it is stable enough to
> release, and report issues found.  My colleagues and I will do likewise, of
> course, but no one company can adequately exercise a new release with this
> many new contributions.
>
> There are two outstanding issue that are not yet committed, but I know the
> contributors hope to see in 1.1.0:
>    MAPREDUCE-4049 <https://issues.apache.org/jira/browse/MAPREDUCE-4049>
>    HADOOP-4012 <https://issues.apache.org/jira/browse/HADOOP-4012>
> Assuming there is an RC-1, and that these two patches can be committed
> during stabilization of RC-0, I will plan to incorporate these additional
> items in RC-1.
>
> Best regards,
> --Matt
> Release Manager
>

It would be nice to get HADOOP-8417 in as well.

On Fri, May 25, 2012 at 2:56 PM, Eli Collins <[EMAIL PROTECTED]> wrote:

> Thanks Matt.  I'd like to get HADOOP-8430 in as well.
>
> (Btw there are 90 issues with target version 1.1.0, perhaps we should move
> these to 1.1.1)
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=%22Target+Version%2Fs%22+%3D+%221.1.0%22+and+resolution+%3D+Unresolved
>
> Thanks,
> Eli
>
> On Fri, May 25, 2012 at 2:49 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
>
> > Greetings.  With the approval of a public vote on common-dev@, I have
> > branched Hadoop branch-1 to create branch-1.1.  From this, I will create
> a
> > release candidate RC-0 for Hadoop-1.1.0, hopefully to be available
> shortly
> > after this weekend.
> >
> > There are over 80 patches in branch-1, over and above the contents of
> > hadoop-1.0.3.  So I anticipate that some stabilization will be needed,
> > before the RC can be approved as a 1.1.0 release.  Your participation in
> > assuring a stable RC is very important.  When it becomes available,
> please
> > download it and work with it to determine whether it is stable enough to
> > release, and report issues found.  My colleagues and I will do likewise,
> of
> > course, but no one company can adequately exercise a new release with
> this
> > many new contributions.
> >
> > There are two outstanding issue that are not yet committed, but I know
> the
> > contributors hope to see in 1.1.0:
> >    MAPREDUCE-4049 <https://issues.apache.org/jira/browse/MAPREDUCE-4049>
> >    HADOOP-4012 <https://issues.apache.org/jira/browse/HADOOP-4012>
> > Assuming there is an RC-1, and that these two patches can be committed
> > during stabilization of RC-0, I will plan to incorporate these additional
> > items in RC-1.
> >
> > Best regards,
> > --Matt
> > Release Manager
> >
>

You might consider pulling in HADOOP-8445.

Tom
On 5/25/12 4:49 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:

> Greetings.  With the approval of a public vote on common-dev@, I have
> branched Hadoop branch-1 to create branch-1.1.  From this, I will create a
> release candidate RC-0 for Hadoop-1.1.0, hopefully to be available shortly
> after this weekend.
>
> There are over 80 patches in branch-1, over and above the contents of
> hadoop-1.0.3.  So I anticipate that some stabilization will be needed,
> before the RC can be approved as a 1.1.0 release.  Your participation in
> assuring a stable RC is very important.  When it becomes available, please
> download it and work with it to determine whether it is stable enough to
> release, and report issues found.  My colleagues and I will do likewise, of
> course, but no one company can adequately exercise a new release with this
> many new contributions.
>
> There are two outstanding issue that are not yet committed, but I know the
> contributors hope to see in 1.1.0:
>     MAPREDUCE-4049 <https://issues.apache.org/jira/browse/MAPREDUCE-4049>
>     HADOOP-4012 <https://issues.apache.org/jira/browse/HADOOP-4012>
> Assuming there is an RC-1, and that these two patches can be committed
> during stabilization of RC-0, I will plan to incorporate these additional
> items in RC-1.
>
> Best regards,
> --Matt
> Release Manager

HDFS-3453 - this makes 1.x and pre-1.x interoperable.
On 5/25/12 4:49 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:

Greetings.  With the approval of a public vote on common-dev@, I have
branched Hadoop branch-1 to create branch-1.1.  From this, I will create a
release candidate RC-0 for Hadoop-1.1.0, hopefully to be available shortly
after this weekend.

There are over 80 patches in branch-1, over and above the contents of
hadoop-1.0.3.  So I anticipate that some stabilization will be needed,
before the RC can be approved as a 1.1.0 release.  Your participation in
assuring a stable RC is very important.  When it becomes available, please
download it and work with it to determine whether it is stable enough to
release, and report issues found.  My colleagues and I will do likewise, of
course, but no one company can adequately exercise a new release with this
many new contributions.

There are two outstanding issue that are not yet committed, but I know the
contributors hope to see in 1.1.0:
    MAPREDUCE-4049 <https://issues.apache.org/jira/browse/MAPREDUCE-4049>
    HADOOP-4012 <https://issues.apache.org/jira/browse/HADOOP-4012>
Assuming there is an RC-1, and that these two patches can be committed
during stabilization of RC-0, I will plan to incorporate these additional
items in RC-1.

Best regards,
--Matt
Release Manager

I'm not sure where this is at but it would be nice to pull in MAPREDUCE-2129
to 1.1.0.

Tom

On 5/25/12 4:49 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:

> Greetings.  With the approval of a public vote on common-dev@, I have
> branched Hadoop branch-1 to create branch-1.1.  From this, I will create a
> release candidate RC-0 for Hadoop-1.1.0, hopefully to be available shortly
> after this weekend.
>
> There are over 80 patches in branch-1, over and above the contents of
> hadoop-1.0.3.  So I anticipate that some stabilization will be needed,
> before the RC can be approved as a 1.1.0 release.  Your participation in
> assuring a stable RC is very important.  When it becomes available, please
> download it and work with it to determine whether it is stable enough to
> release, and report issues found.  My colleagues and I will do likewise, of
> course, but no one company can adequately exercise a new release with this
> many new contributions.
>
> There are two outstanding issue that are not yet committed, but I know the
> contributors hope to see in 1.1.0:
>     MAPREDUCE-4049 <https://issues.apache.org/jira/browse/MAPREDUCE-4049>
>     HADOOP-4012 <https://issues.apache.org/jira/browse/HADOOP-4012>
> Assuming there is an RC-1, and that these two patches can be committed
> during stabilization of RC-0, I will plan to incorporate these additional
> items in RC-1.
>
> Best regards,
> --Matt
> Release Manager