I've created 2.1.2-beta release version. Please use that for any *critical* 
commits on branch-2.1-beta branch. Please be careful, let's keep #commits here 
very small.

thanks,
Arun

On Sep 24, 2013, at 2:07 PM, Andrew Wang <andrew.w...@cloudera.com> wrote:

> Hey Arun,
> 
> That plan sounds good to me, thanks for being on top of things. What's the
> new fix version we should be using (2.1.2 or 2.2.0)? Would be good to get
> the same clarification regarding which branches should be receiving
> commits. I think a 2.1.2 would be nice to get the symlinks changes in a
> beta release pre-GA.
> 
> I'd also like to add HADOOP-9761 to tucu's list of JIRAs, a symlink+viewfs
> regression that's mistakenly only in branch-2.
> 
> Thanks,
> Andrew
> 
> 
> On Tue, Sep 24, 2013 at 1:39 PM, Arun C Murthy <a...@hortonworks.com> wrote:
> 
>> Rather than spin another RC, let's get this out and follow up with the
>> next release - especially since it's not clear how long it will take for
>> the symlink stuff to sort itself out.
>> 
>> Getting this out will help downstream projects, even if it does so in
>> small way.
>> 
>> Arun
>> 
>> On Sep 23, 2013, at 5:36 PM, Alejandro Abdelnur <t...@cloudera.com> wrote:
>> 
>>> Vote for the 2.1.1-beta release is closing tonight, while we had quite a
>>> few +1s, it seems we need to address the following before doing a
>> release:
>>> 
>>> symlink discussion: get a concrete and explicit understanding on what we
>>> will do and  in what release(s).
>>> 
>>> Also, the following JIRAs seem nasty enough to require a new RC:
>>> 
>>> https://issues.apache.org/jira/browse/HDFS-5225 (no patch avail)
>>> https://issues.apache.org/jira/browse/HDFS-5228 (patch avail)
>>> https://issues.apache.org/jira/browse/YARN-1089 (patch avail)
>>> https://issues.apache.org/jira/browse/MAPREDUCE-5529 (patch avail)
>>> 
>>> I won't -1 the release but I'm un-casting my vote as I think we should
>>> address these things before.
>>> 
>>> Thanks.
>>> 
>>> Alejandro
>>> 
>>> 
>>> On Tue, Sep 24, 2013 at 1:49 AM, Suresh Srinivas <sur...@hortonworks.com
>>> wrote:
>>> 
>>>> +1 (binding)
>>>> 
>>>> 
>>>> Verified the signatures and hashes for both src and binary tars. Built
>> from
>>>> the source, the binary distribution and the documentation. Started a
>> single
>>>> node cluster and tested the following:
>>>> 
>>>> # Started HDFS cluster, verified the hdfs CLI commands such ls, copying
>>>> data back and forth, verified namenode webUI etc.
>>>> 
>>>> # Ran some tests such as sleep job, TestDFSIO, NNBench etc.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 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.
>>>>> 
>>>>> thanks,
>>>>> Arun
>>>>> 
>>>>> 
>>>>> --
>>>>> Arun C. Murthy
>>>>> 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.
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> http://hortonworks.com/download/
>>>> 
>>>> --
>>>> 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
>> 
>> --
>> Arun C. Murthy
>> 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.
>> 

--
Arun C. Murthy
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.

Reply via email to