I can do this. I'm in the process of running tests on the code anyway, so I can 
backport appropriate patches as necessary and get things going.

Here's a high-level jira for what needs to be done: 
https://issues.apache.org/jira/browse/HELIX-402

Kanak

----------------------------------------
> Date: Tue, 11 Mar 2014 10:55:47 -0700
> Subject: Re: [DISCUSS] Do we need 0.6.3 release
> From: [email protected]
> To: [email protected]
>
> We can look at the bug fixes in 0.7.0 and see if any feature/bug fix can be
> back ported to 0.6.3. Any volunteers for driving 0.6.3 ?
>
> thanks,
> Kishore G
>
>
> On Tue, Mar 11, 2014 at 2:08 AM, Matthieu Morel <[email protected]> wrote:
>
>> Yes, please include these changes, considering 0.7 is not ready yet.
>>
>> I also remember wondering why josql... and decreasing the number of
>> dependencies is always a good thing.
>>
>> Note that it's a bit tricky to find out which other changes - if any -
>> could be interesting for 0.6.x since only a few tickets mention the version
>> they affect and the version fix is targeted for.
>>
>> Thanks,
>>
>> Matthieu
>>
>>
>> On Mar 10, 2014, at 20:44 , Kanak Biscuitwala <[email protected]> wrote:
>>
>>>
>>> I think it's important that we do this release. It would include:
>>>
>>> 1. Compatibility fix for property store
>>> 2. Controller pipeline performance improvements
>>> 3. New JMX exposed by the controller
>>>
>>> In addition, I can also port the change that removes the dependency on
>> josql if that is desirable.
>>>
>>> Kanak
>>>
>>> ----------------------------------------
>>>> Date: Mon, 10 Mar 2014 12:38:36 -0700
>>>> Subject: [DISCUSS] Do we need 0.6.3 release
>>>> From: [email protected]
>>>> To: [email protected]
>>>>
>>>> Hi,
>>>>
>>>> While we are working on redefining the new api's in 0.7.0, do we need to
>>>> make 0.6.3 release. Is there any one depending on features/bug fixes.
>>>>
>>>> thanks,
>>>> Kishore G
>>>
>>
>>
                                          

Reply via email to