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

Switch to Threaded View
MapReduce, mail # dev - Re-swizzle 2.3


Copy link to this message
-
Re: Re-swizzle 2.3
Sandy Ryza 2014-01-28, 08:11
Going forward with commits because it seems like others have been doing so
On Mon, Jan 27, 2014 at 1:31 PM, Sandy Ryza <[EMAIL PROTECTED]> wrote:

> We should hold off commits until that's done, right?
>
>
> On Mon, Jan 27, 2014 at 1:07 PM, Arun C Murthy <[EMAIL PROTECTED]>wrote:
>
>> Yep, on it as we speak. :)
>>
>>
>> Arun
>>
>> On Jan 27, 2014, at 12:36 PM, Jason Lowe <[EMAIL PROTECTED]> wrote:
>>
>> > Thanks, Arun.  Are there plans to update the Fix Versions and
>> CHANGES.txt accordingly?  There are a lot of JIRAs that are now going to
>> ship in 2.3.0 but the JIRA and CHANGES.txt says they're not fixed until
>> 2.4.0.
>> >
>> > Jason
>> >
>> > On 01/27/2014 08:47 AM, Arun C Murthy wrote:
>> >> Done. I've re-created branch-2.3 from branch-2.
>> >>
>> >> thanks,
>> >> Arun
>> >>
>> >> On Jan 23, 2014, at 2:40 AM, Arun Murthy <[EMAIL PROTECTED]> wrote:
>> >>
>> >>> Based on the discussion at common-dev@, we've decided to target 2.3
>> >>> off the tip of branch-2 based on the 2 major HDFS features which are
>> >>> Heterogenous Storage (HDFS-2832) and HDFS Cache (HDFS-4949).
>> >>>
>> >>> I'll create a new branch-2.3 on (1/24) at 6pm PST.
>> >>>
>> >>> thanks,
>> >>> Arun
>> >> --
>> >> Arun C. Murthy
>> >> Hortonworks Inc.
>> >> http://hortonworks.com/
>> >>
>> >>
>> >>
>> >
>>
>> --
>> 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.
>>
>
>