Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop, mail # dev - Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha


Copy link to this message
-
Re: [VOTE] Release Apache Hadoop 2.0.5-alpha
Arun C Murthy 2013-06-02, 22:04
I record the 'release date' as the one on which the build is created. Not sure what Matt actually does on branch-1. Matt?

hth,
Arun

On Jun 2, 2013, at 12:33 PM, Konstantin Boudnik wrote:

> This is my first Hadoop release, so I am all ears ;) I looked at how Arun was
> cutting the previous 2.0.x and followed the example.
>
> Thanks for your input and help Alejandro!
>
> Regards,
>  Cos
>
> On Sun, Jun 02, 2013 at 09:01AM, Alejandro Abdelnur wrote:
>> I know we had this issue before. But and easy way to solve it it would be
>> using as release date the date the vote ends. Anyway, not a big deal if we
>> are not cutting a new rc for other reason
>>
>> +1 on rc1
>>
>> Thx
>>
>> On Jun 2, 2013, at 12:04 AM, Konstantin Boudnik <[EMAIL PROTECTED]> wrote:
>>
>>> Alejandro,
>>>
>>> I believe this is chicken and egg problem: I can't put release date into
>>> unreleased tarball. Looking into 2.0.4-alpha source tarball I see the same
>>> situation:
>>>
>>> Release 2.0.4-alpha - UNRELEASED
>>>
>>> But in the trunk and branch-2 the release data is in place. I don't think this
>>> is an issue. But I would be happy to fix it if this seems to be a problem.
>>>
>>> Thanks,
>>> Cos
>>>
>>> On Sat, Jun 01, 2013 at 08:04PM, Alejandro Abdelnur wrote:
>>>> On RC1, verified MD5 & signature, built, configured pseudo cluster, run a
>>>> couple of sample jobs, tested HTTPFS.
>>>>
>>>> CHANGES.txt files contents are correct now. Still, a minor NIT, they have
>>>> 2.0.5 as UNRELEASED, shouldn't they have a date (I would assume the date
>>>> the vote ends).
>>>>
>>>> Thanks
>>>>
>>>>
>>>> On Fri, May 31, 2013 at 9:39 PM, J. Rottinghuis <[EMAIL PROTECTED]>wrote:
>>>>
>>>>> Thanks for fixing Cos.
>>>>> http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc1/
>>>>> looks good to me.
>>>>> +1 (non-binding)
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Joep
>>>>>
>>>>>
>>>>> On Fri, May 31, 2013 at 8:25 PM, Konstantin Boudnik <[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>
>>>>>> Ok, WRT HDFS-4646 - it is all legit and the code is in branch-2.0.4-alpha
>>>>>> and
>>>>>> later. It has been committed as
>>>>>> r1465124
>>>>>> The reason it isn't normally visible because of the weird commit message:
>>>>>>
>>>>>>       svn merge -c1465121 from trunk
>>>>>>
>>>>>> So, we good. I am done with the CHANGES.txt fixed that you guys have
>>>>> noted
>>>>>> earlier and will be re-spinning RC1 in a few.
>>>>>>
>>>>>> Cos
>>>>>>
>>>>>> On Fri, May 31, 2013 at 08:07PM, Konstantin Boudnik wrote:
>>>>>>> Alejandro,
>>>>>>>
>>>>>>> thanks for looking into this. Indeed - I missed the 2.0.5-alpha section
>>>>>> in
>>>>>>> YARN CHANGES.txt. Added now. As for HDFS-4646: apparently I didn't get
>>>>>> into
>>>>>>> to branch-2.0.4-alpha back then, although I distinctively remember
>>>>> doing
>>>>>> this.
>>>>>>> Let me pull it into 2.0.5-alpha and update CHANGES.txt to reflect it.
>>>>>> Also, I
>>>>>>> will do JIRA in a moment.
>>>>>>>
>>>>>>> Joep, appreciate the thorough examination. I have fixed the dates for
>>>>> the
>>>>>>> releases 2.0.4-alpha. As for the top-level readme file - sorry I wasn't
>>>>>> aware
>>>>>>> about them. As for the binary: I am pretty sure we are only releasing
>>>>>> source
>>>>>>> code, but I will put binaries into the rc1 respin.
>>>>>>>
>>>>>>> I will respin rc1 shortly. Appreciate the feedback!
>>>>>>> Cos
>>>>>>>
>>>>>>> On Fri, May 31, 2013 at 05:27PM, Alejandro Abdelnur wrote:
>>>>>>>> Verified MD5 & signature, built, configured pseudo cluster, run a
>>>>>> couple of
>>>>>>>> sample jobs, tested HTTPFS.
>>>>>>>>
>>>>>>>> Still, something seems odd.
>>>>>>>>
>>>>>>>> The HDFS CHANGES.txt has the following entry under 2.0.5-alpha:
>>>>>>>>
>>>>>>>> HDFS-4646. createNNProxyWithClientProtocol ignores configured
>>>>> timeout
>>>>>>>> value  (Jagane Sundar via cos)
>>>>>>>>
>>>>>>>> but I don't see that in the branch.
>>>>>>>>
>>>>>>>> And, the YARN CHANGES.txt does not have the 2.0.5-alpha section (it
>>>>>> should
>>>>>>>> be there empty).

Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/