You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@helix.apache.org by Vinayak Borkar <vi...@gmail.com> on 2013/06/11 08:50:45 UTC
Planning Helix Release 0.6.2
Hi Guys,
I would like to start the ball rolling on release 0.6.2 of helix by
starting the discussion of possible features we should aim for.
https://issues.apache.org/jira/browse/HELIX-95 tracks the wishlist of
features/improvements for release 0.6.2.
One of the primary changes in this release will be to clean up the Helix
APIs that applications use. To this end, I would like to separate out
all interfaces/classes that are user-facing into a new Maven project
called helix-api.
Please reply to this mail with any other things that you think we should
include in this release.
Thanks,
Vinayak
Re: Planning Helix Release 0.6.2
Posted by Santiago Perez <sa...@santip.com.ar>.
+1 for separate helix-api package, I think it will be very useful to keep
the apis decoupled from implementation.
all the recipes and examples should strive to rely exclusively on apis from
this package, and we could use the examples to identify the apis that
should be exposed and to identify the pain points and issues with current
apis
On Tue, Jun 11, 2013 at 2:04 PM, Vinayak Borkar <vi...@gmail.com> wrote:
> Hi Kishore,
>
>
> I do agree that backward compatibility has to be maintained. In this
> release I think we should create the helix-api project and make it contain
> new API as the way it should be while keeping the old API intact (maybe
> mark it as deprecated). In a release or two, we can eliminate the older
> APIs.
>
> Thoughts?
>
>
> Vinayak
>
>
>
> On 6/11/13 9:43 AM, kishore g wrote:
>
>> Thanks Vinayak for taking this up. Adding a separate helix-api package
>> makes sense. The challenge here would be to keep backward compatibility.
>> What we should probably do is have additional user facing classes that
>> make
>> it easy to use Helix features.
>>
>> What do you think ?
>>
>> thanks,
>> Kishore G
>>
>>
>>
>> On Mon, Jun 10, 2013 at 11:50 PM, Vinayak Borkar <vi...@gmail.com>
>> wrote:
>>
>> Hi Guys,
>>>
>>>
>>> I would like to start the ball rolling on release 0.6.2 of helix by
>>> starting the discussion of possible features we should aim for.
>>>
>>> https://issues.apache.org/****jira/browse/HELIX-95<https://issues.apache.org/**jira/browse/HELIX-95>
>>> <https://**issues.apache.org/jira/browse/**HELIX-95<https://issues.apache.org/jira/browse/HELIX-95>>tracks
>>> the wishlist of features/improvements for release 0.6.2.
>>>
>>> One of the primary changes in this release will be to clean up the Helix
>>> APIs that applications use. To this end, I would like to separate out all
>>> interfaces/classes that are user-facing into a new Maven project called
>>> helix-api.
>>>
>>> Please reply to this mail with any other things that you think we should
>>> include in this release.
>>>
>>>
>>> Thanks,
>>> Vinayak
>>>
>>>
>>
>
Re: Planning Helix Release 0.6.2
Posted by Vinayak Borkar <vi...@gmail.com>.
Hi Kishore,
I do agree that backward compatibility has to be maintained. In this
release I think we should create the helix-api project and make it
contain new API as the way it should be while keeping the old API intact
(maybe mark it as deprecated). In a release or two, we can eliminate the
older APIs.
Thoughts?
Vinayak
On 6/11/13 9:43 AM, kishore g wrote:
> Thanks Vinayak for taking this up. Adding a separate helix-api package
> makes sense. The challenge here would be to keep backward compatibility.
> What we should probably do is have additional user facing classes that make
> it easy to use Helix features.
>
> What do you think ?
>
> thanks,
> Kishore G
>
>
>
> On Mon, Jun 10, 2013 at 11:50 PM, Vinayak Borkar <vi...@gmail.com> wrote:
>
>> Hi Guys,
>>
>>
>> I would like to start the ball rolling on release 0.6.2 of helix by
>> starting the discussion of possible features we should aim for.
>>
>> https://issues.apache.org/**jira/browse/HELIX-95<https://issues.apache.org/jira/browse/HELIX-95>tracks the wishlist of features/improvements for release 0.6.2.
>>
>> One of the primary changes in this release will be to clean up the Helix
>> APIs that applications use. To this end, I would like to separate out all
>> interfaces/classes that are user-facing into a new Maven project called
>> helix-api.
>>
>> Please reply to this mail with any other things that you think we should
>> include in this release.
>>
>>
>> Thanks,
>> Vinayak
>>
>
Re: Planning Helix Release 0.6.2
Posted by kishore g <g....@gmail.com>.
Thanks Vinayak for taking this up. Adding a separate helix-api package
makes sense. The challenge here would be to keep backward compatibility.
What we should probably do is have additional user facing classes that make
it easy to use Helix features.
What do you think ?
thanks,
Kishore G
On Mon, Jun 10, 2013 at 11:50 PM, Vinayak Borkar <vi...@gmail.com> wrote:
> Hi Guys,
>
>
> I would like to start the ball rolling on release 0.6.2 of helix by
> starting the discussion of possible features we should aim for.
>
> https://issues.apache.org/**jira/browse/HELIX-95<https://issues.apache.org/jira/browse/HELIX-95>tracks the wishlist of features/improvements for release 0.6.2.
>
> One of the primary changes in this release will be to clean up the Helix
> APIs that applications use. To this end, I would like to separate out all
> interfaces/classes that are user-facing into a new Maven project called
> helix-api.
>
> Please reply to this mail with any other things that you think we should
> include in this release.
>
>
> Thanks,
> Vinayak
>
Re: Planning Helix Release 0.6.2
Posted by kishore g <g....@gmail.com>.
Thanks Vinayak for taking this up. Adding a separate helix-api package
makes sense. The challenge here would be to keep backward compatibility.
What we should probably do is have additional user facing classes that make
it easy to use Helix features.
What do you think ?
thanks,
Kishore G
On Mon, Jun 10, 2013 at 11:50 PM, Vinayak Borkar <vi...@gmail.com> wrote:
> Hi Guys,
>
>
> I would like to start the ball rolling on release 0.6.2 of helix by
> starting the discussion of possible features we should aim for.
>
> https://issues.apache.org/**jira/browse/HELIX-95<https://issues.apache.org/jira/browse/HELIX-95>tracks the wishlist of features/improvements for release 0.6.2.
>
> One of the primary changes in this release will be to clean up the Helix
> APIs that applications use. To this end, I would like to separate out all
> interfaces/classes that are user-facing into a new Maven project called
> helix-api.
>
> Please reply to this mail with any other things that you think we should
> include in this release.
>
>
> Thanks,
> Vinayak
>