Are we doing a new RC for 2.1.1-beta?

On Mon, Sep 23, 2013 at 9:04 PM, Vinod Kumar Vavilapalli <vino...@apache.org
> wrote:

> Correct me if I am wrong, but FWIU, we already released a beta with the
> same symlink issues. Given 2.1.1 is just another beta, I believe we can go
> ahead with it and resolve the issues in the final GA release. Instead of
> resetting the testing done by everyone.
>
> It's a hard story to sell but beta phase is supposed to be only about
> bug-fixes, but incompatible changes that cannot be avoided, well cannot be
> avoided.
>
>  Thanks,
> +Vinod
>
> On Sep 23, 2013, at 11:42 AM, Andrew Wang wrote:
>
> We still need to resolve some symlink issues; are we planning to spin a new
> RC? Leaving it as-is is not a good option.
>
>
> On Sun, Sep 22, 2013 at 11:23 PM, Roman Shaposhnik <r...@apache.org> wrote:
>
> On Mon, Sep 16, 2013 at 11:38 PM, Arun C Murthy <a...@hortonworks.com>
>
> wrote:
>
> Folks,
>
>
> I've created a release candidate (rc0) for hadoop-2.1.1-beta that I
>
> would like to get
>
> released - this release fixes a number of bugs on top of
>
> hadoop-2.1.0-beta as a result of significant amounts of testing.
>
>
> If things go well, this might be the last of the *beta* releases of
>
> hadoop-2.x.
>
>
> The RC is available at:
>
> http://people.apache.org/~acmurthy/hadoop-2.1.1-beta-rc0
>
> The RC tag in svn is here:
>
> http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.1-beta-rc0
>
>
> The maven artifacts are available via repository.apache.org.
>
>
> Please try the release and vote; the vote will run for the usual 7 days.
>
>
> Short of HDFS-5225 from the Bigtop perspective this RC gets a +1.
>
>
> All tests passed in both secure and unsecure modes in 4 nodes
>
> pseudo distributed cluster with all the members of Hadoop
>
> ecosystem running smoke tests.
>
>
> Thanks,
>
> Roman.
>
>
>
>
> 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.
>



-- 
Alejandro

Reply via email to