On May 4, 2011, at 6:31 AM, Owen O'Malley wrote:
>
> On May 3, 2011, at 9:35 AM, Eli Collins wrote:
>
>> Do all changes for 0.20.2xx release go through branch-0.20-security,
>> then get merged to a particular -2xx branch?
>
> I've discussed this before on the lists, but here goes:
>
> branch
On May 3, 2011, at 9:58 AM, Arun C Murthy wrote:
>>
>> Owen, Suresh and I have committed everything on this list except
>> HADOOP-6386 and HADOOP-6428. Not sure which of the two are relevant/
>> necessary, I'll check with Cos. Other than that hadoop-0.20.203 now a
>> superset of hadoop-0.20.2.
On Jan 8, 2011, at 4:44 AM, Owen O'Malley wrote:
>
> To prevent future race conditions, let me formally be the RM for 0.20.3.
> Please check with me before any commits to the 0.20 branch.
>
Great news..
Thanks Owen.
> -- Owen
Is 20.3 a 'dead' release ?
I haven't seen any discussion of this on the apache lists about creating a 20.3
release, and kind of goes against all the discussion that we recently had with
StAck about creating a 'append' release on 0.20.
I'm not against 20.3, but I would like to see some discussi
Hong Tang wrote:
I have talked with a few folks in the community who are interested in
using TFile (HADOOP-3315) in their projects that are currently
dependent on Hadoop 0.20, and it would significantly simplify the
release process as well as their lives if we could back port TFile to
Hadoop 0
