You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by Serge Huber <sh...@jahia.com> on 2016/09/14 13:30:42 UTC
Unomi 2 roadmap (was Re: release & commiters)
I’m hoping we can use Karaf Cellar for direct clustering of Apache Unomi nodes :)
cheers,
Serge…
> On 14 sept. 2016, at 15:29, Thomas Draier <td...@jahia.com> wrote:
>
> We could probably go for a 2.0 when we upgrade ES and karaf . And yes, a
> possibility to use a non-embedded ES would be nice, but then we'll have to
> handle the cluster by ourself (which should not be a big deal).
>
>
> On Wed, Sep 14, 2016 at 3:20 PM Serge Huber <sh...@jahia.com> wrote:
>
>> +1 for release
>>
>> +1 for Abdelkader
>>
>> +1 for Damien
>>
>> After the release it would be great if we could merge my pull request to
>> upgrade to ElasticSearch 2.4.0. I’ve been testing it more and more and it
>> seems functional from my side. We should also upgrade to Karaf 4 once JB
>> has time to send us his modifications :)
>>
>> After that there are more things I’d like to improve (such as making it
>> possible to use a non-embedded ElasticSearch) but I think that’s a topic
>> for another mail :)
>>
>> cheers,
>> Serge…
>>
>>> On 14 sept. 2016, at 14:53, Thomas Draier <td...@jahia.com> wrote:
>>>
>>> Hi there,
>>>
>>> What would you think of starting a release 1.1.0 ? There have been a lot
>> of
>>> bug fixes, and some improvements on the API (privacy, user profile,
>> ability
>>> to post conditions, ..), and also a long time since the last release.
>>>
>>> And also, I would like to propose Abdelkader Midani and Damien Gaillard
>> as
>>> committers . Abdelakader already did a lot of fixes, and Damien started
>> to
>>> contribute just one month ago but already did some interesting patches
>> too.
>>>
>>> Regards
>>>
>>> thomas
>>
>>
Re: Unomi 2 roadmap (was Re: release & commiters)
Posted by Serge Huber <sh...@jahia.com>.
Yes thanks for catching that Chris I will need to test to see if I can integrate this feature. It would make the transition to ES 2.x a lot smoother as we already have some usage of Unomi that use dot characters.
cheers,
Serge…
> On 15 sept. 2016, at 10:55, Chris Laprun <cl...@jahia.com> wrote:
>
>
>> On 14 Sep 2016, at 17:00, Serge Huber <sh...@jahia.com> wrote:
>>
>> Well on the ES 2 branch there is one problem I had was that ES 2.x does not allow “.” (dot) characters in property names, which might be seen as an API change ?
>
> Indeed, however, 2.4.0 sees the return of dot in field names (which we might or might not want to allow for diverse reasons).
>
>>
>> cheers,
>> Serge…
>>
>>> On 14 sept. 2016, at 16:31, Chris Laprun <cl...@jahia.com> wrote:
>>>
>>>
>>>> On 14 Sep 2016, at 15:30, Serge Huber <sh...@jahia.com> wrote:
>>>>
>>>> I’m hoping we can use Karaf Cellar for direct clustering of Apache Unomi nodes :)
>>>
>>> I would argue that we should use semantic versioning for Unomi and unless, we have API-breaking changes, we probably should stick with v1.x for the ES / Karaf upgrade. 2.x should probably be reserved for when we finally have a CXS spec to implement.
>>>
>>>
>>>> cheers,
>>>> Serge…
>>>>
>>>>> On 14 sept. 2016, at 15:29, Thomas Draier <td...@jahia.com> wrote:
>>>>>
>>>>> We could probably go for a 2.0 when we upgrade ES and karaf . And yes, a
>>>>> possibility to use a non-embedded ES would be nice, but then we'll have to
>>>>> handle the cluster by ourself (which should not be a big deal).
>>>>>
>>>>>
>>>>> On Wed, Sep 14, 2016 at 3:20 PM Serge Huber <sh...@jahia.com> wrote:
>>>>>
>>>>>> +1 for release
>>>>>>
>>>>>> +1 for Abdelkader
>>>>>>
>>>>>> +1 for Damien
>>>>>>
>>>>>> After the release it would be great if we could merge my pull request to
>>>>>> upgrade to ElasticSearch 2.4.0. I’ve been testing it more and more and it
>>>>>> seems functional from my side. We should also upgrade to Karaf 4 once JB
>>>>>> has time to send us his modifications :)
>>>>>>
>>>>>> After that there are more things I’d like to improve (such as making it
>>>>>> possible to use a non-embedded ElasticSearch) but I think that’s a topic
>>>>>> for another mail :)
>>>>>>
>>>>>> cheers,
>>>>>> Serge…
>>>>>>
>>>>>>> On 14 sept. 2016, at 14:53, Thomas Draier <td...@jahia.com> wrote:
>>>>>>>
>>>>>>> Hi there,
>>>>>>>
>>>>>>> What would you think of starting a release 1.1.0 ? There have been a lot
>>>>>> of
>>>>>>> bug fixes, and some improvements on the API (privacy, user profile,
>>>>>> ability
>>>>>>> to post conditions, ..), and also a long time since the last release.
>>>>>>>
>>>>>>> And also, I would like to propose Abdelkader Midani and Damien Gaillard
>>>>>> as
>>>>>>> committers . Abdelakader already did a lot of fixes, and Damien started
>>>>>> to
>>>>>>> contribute just one month ago but already did some interesting patches
>>>>>> too.
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> thomas
>>>>>>
>>>>>>
>>>>
>>>
>>
>
Re: Unomi 2 roadmap (was Re: release & commiters)
Posted by Chris Laprun <cl...@jahia.com>.
> On 14 Sep 2016, at 17:00, Serge Huber <sh...@jahia.com> wrote:
>
> Well on the ES 2 branch there is one problem I had was that ES 2.x does not allow “.” (dot) characters in property names, which might be seen as an API change ?
Indeed, however, 2.4.0 sees the return of dot in field names (which we might or might not want to allow for diverse reasons).
>
> cheers,
> Serge…
>
>> On 14 sept. 2016, at 16:31, Chris Laprun <cl...@jahia.com> wrote:
>>
>>
>>> On 14 Sep 2016, at 15:30, Serge Huber <sh...@jahia.com> wrote:
>>>
>>> I’m hoping we can use Karaf Cellar for direct clustering of Apache Unomi nodes :)
>>
>> I would argue that we should use semantic versioning for Unomi and unless, we have API-breaking changes, we probably should stick with v1.x for the ES / Karaf upgrade. 2.x should probably be reserved for when we finally have a CXS spec to implement.
>>
>>
>>> cheers,
>>> Serge…
>>>
>>>> On 14 sept. 2016, at 15:29, Thomas Draier <td...@jahia.com> wrote:
>>>>
>>>> We could probably go for a 2.0 when we upgrade ES and karaf . And yes, a
>>>> possibility to use a non-embedded ES would be nice, but then we'll have to
>>>> handle the cluster by ourself (which should not be a big deal).
>>>>
>>>>
>>>> On Wed, Sep 14, 2016 at 3:20 PM Serge Huber <sh...@jahia.com> wrote:
>>>>
>>>>> +1 for release
>>>>>
>>>>> +1 for Abdelkader
>>>>>
>>>>> +1 for Damien
>>>>>
>>>>> After the release it would be great if we could merge my pull request to
>>>>> upgrade to ElasticSearch 2.4.0. I’ve been testing it more and more and it
>>>>> seems functional from my side. We should also upgrade to Karaf 4 once JB
>>>>> has time to send us his modifications :)
>>>>>
>>>>> After that there are more things I’d like to improve (such as making it
>>>>> possible to use a non-embedded ElasticSearch) but I think that’s a topic
>>>>> for another mail :)
>>>>>
>>>>> cheers,
>>>>> Serge…
>>>>>
>>>>>> On 14 sept. 2016, at 14:53, Thomas Draier <td...@jahia.com> wrote:
>>>>>>
>>>>>> Hi there,
>>>>>>
>>>>>> What would you think of starting a release 1.1.0 ? There have been a lot
>>>>> of
>>>>>> bug fixes, and some improvements on the API (privacy, user profile,
>>>>> ability
>>>>>> to post conditions, ..), and also a long time since the last release.
>>>>>>
>>>>>> And also, I would like to propose Abdelkader Midani and Damien Gaillard
>>>>> as
>>>>>> committers . Abdelakader already did a lot of fixes, and Damien started
>>>>> to
>>>>>> contribute just one month ago but already did some interesting patches
>>>>> too.
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> thomas
>>>>>
>>>>>
>>>
>>
>
Re: Unomi 2 roadmap (was Re: release & commiters)
Posted by Serge Huber <sh...@jahia.com>.
Well on the ES 2 branch there is one problem I had was that ES 2.x does not allow “.” (dot) characters in property names, which might be seen as an API change ?
cheers,
Serge…
> On 14 sept. 2016, at 16:31, Chris Laprun <cl...@jahia.com> wrote:
>
>
>> On 14 Sep 2016, at 15:30, Serge Huber <sh...@jahia.com> wrote:
>>
>> I’m hoping we can use Karaf Cellar for direct clustering of Apache Unomi nodes :)
>
> I would argue that we should use semantic versioning for Unomi and unless, we have API-breaking changes, we probably should stick with v1.x for the ES / Karaf upgrade. 2.x should probably be reserved for when we finally have a CXS spec to implement.
>
>
>> cheers,
>> Serge…
>>
>>> On 14 sept. 2016, at 15:29, Thomas Draier <td...@jahia.com> wrote:
>>>
>>> We could probably go for a 2.0 when we upgrade ES and karaf . And yes, a
>>> possibility to use a non-embedded ES would be nice, but then we'll have to
>>> handle the cluster by ourself (which should not be a big deal).
>>>
>>>
>>> On Wed, Sep 14, 2016 at 3:20 PM Serge Huber <sh...@jahia.com> wrote:
>>>
>>>> +1 for release
>>>>
>>>> +1 for Abdelkader
>>>>
>>>> +1 for Damien
>>>>
>>>> After the release it would be great if we could merge my pull request to
>>>> upgrade to ElasticSearch 2.4.0. I’ve been testing it more and more and it
>>>> seems functional from my side. We should also upgrade to Karaf 4 once JB
>>>> has time to send us his modifications :)
>>>>
>>>> After that there are more things I’d like to improve (such as making it
>>>> possible to use a non-embedded ElasticSearch) but I think that’s a topic
>>>> for another mail :)
>>>>
>>>> cheers,
>>>> Serge…
>>>>
>>>>> On 14 sept. 2016, at 14:53, Thomas Draier <td...@jahia.com> wrote:
>>>>>
>>>>> Hi there,
>>>>>
>>>>> What would you think of starting a release 1.1.0 ? There have been a lot
>>>> of
>>>>> bug fixes, and some improvements on the API (privacy, user profile,
>>>> ability
>>>>> to post conditions, ..), and also a long time since the last release.
>>>>>
>>>>> And also, I would like to propose Abdelkader Midani and Damien Gaillard
>>>> as
>>>>> committers . Abdelakader already did a lot of fixes, and Damien started
>>>> to
>>>>> contribute just one month ago but already did some interesting patches
>>>> too.
>>>>>
>>>>> Regards
>>>>>
>>>>> thomas
>>>>
>>>>
>>
>
Re: Unomi 2 roadmap (was Re: release & commiters)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
by the way, we have a Maven plugin (we are using in Karaf and Pax Web
for instance) to check the semantic versioning and API change.
Agree with Chris: API breaking changes should result to a new major
branch/version. I would argue the same for important dependency upgrades.
We are using the same approach in Karaf.
Regards
JB
On 09/14/2016 04:31 PM, Chris Laprun wrote:
>
>> On 14 Sep 2016, at 15:30, Serge Huber <sh...@jahia.com> wrote:
>>
>> I\u2019m hoping we can use Karaf Cellar for direct clustering of Apache Unomi nodes :)
>
> I would argue that we should use semantic versioning for Unomi and unless, we have API-breaking changes, we probably should stick with v1.x for the ES / Karaf upgrade. 2.x should probably be reserved for when we finally have a CXS spec to implement.
>
>
>> cheers,
>> Serge\u2026
>>
>>> On 14 sept. 2016, at 15:29, Thomas Draier <td...@jahia.com> wrote:
>>>
>>> We could probably go for a 2.0 when we upgrade ES and karaf . And yes, a
>>> possibility to use a non-embedded ES would be nice, but then we'll have to
>>> handle the cluster by ourself (which should not be a big deal).
>>>
>>>
>>> On Wed, Sep 14, 2016 at 3:20 PM Serge Huber <sh...@jahia.com> wrote:
>>>
>>>> +1 for release
>>>>
>>>> +1 for Abdelkader
>>>>
>>>> +1 for Damien
>>>>
>>>> After the release it would be great if we could merge my pull request to
>>>> upgrade to ElasticSearch 2.4.0. I\u2019ve been testing it more and more and it
>>>> seems functional from my side. We should also upgrade to Karaf 4 once JB
>>>> has time to send us his modifications :)
>>>>
>>>> After that there are more things I\u2019d like to improve (such as making it
>>>> possible to use a non-embedded ElasticSearch) but I think that\u2019s a topic
>>>> for another mail :)
>>>>
>>>> cheers,
>>>> Serge\u2026
>>>>
>>>>> On 14 sept. 2016, at 14:53, Thomas Draier <td...@jahia.com> wrote:
>>>>>
>>>>> Hi there,
>>>>>
>>>>> What would you think of starting a release 1.1.0 ? There have been a lot
>>>> of
>>>>> bug fixes, and some improvements on the API (privacy, user profile,
>>>> ability
>>>>> to post conditions, ..), and also a long time since the last release.
>>>>>
>>>>> And also, I would like to propose Abdelkader Midani and Damien Gaillard
>>>> as
>>>>> committers . Abdelakader already did a lot of fixes, and Damien started
>>>> to
>>>>> contribute just one month ago but already did some interesting patches
>>>> too.
>>>>>
>>>>> Regards
>>>>>
>>>>> thomas
>>>>
>>>>
>>
>
--
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Unomi 2 roadmap (was Re: release & commiters)
Posted by Chris Laprun <cl...@jahia.com>.
> On 14 Sep 2016, at 15:30, Serge Huber <sh...@jahia.com> wrote:
>
> I’m hoping we can use Karaf Cellar for direct clustering of Apache Unomi nodes :)
I would argue that we should use semantic versioning for Unomi and unless, we have API-breaking changes, we probably should stick with v1.x for the ES / Karaf upgrade. 2.x should probably be reserved for when we finally have a CXS spec to implement.
> cheers,
> Serge…
>
>> On 14 sept. 2016, at 15:29, Thomas Draier <td...@jahia.com> wrote:
>>
>> We could probably go for a 2.0 when we upgrade ES and karaf . And yes, a
>> possibility to use a non-embedded ES would be nice, but then we'll have to
>> handle the cluster by ourself (which should not be a big deal).
>>
>>
>> On Wed, Sep 14, 2016 at 3:20 PM Serge Huber <sh...@jahia.com> wrote:
>>
>>> +1 for release
>>>
>>> +1 for Abdelkader
>>>
>>> +1 for Damien
>>>
>>> After the release it would be great if we could merge my pull request to
>>> upgrade to ElasticSearch 2.4.0. I’ve been testing it more and more and it
>>> seems functional from my side. We should also upgrade to Karaf 4 once JB
>>> has time to send us his modifications :)
>>>
>>> After that there are more things I’d like to improve (such as making it
>>> possible to use a non-embedded ElasticSearch) but I think that’s a topic
>>> for another mail :)
>>>
>>> cheers,
>>> Serge…
>>>
>>>> On 14 sept. 2016, at 14:53, Thomas Draier <td...@jahia.com> wrote:
>>>>
>>>> Hi there,
>>>>
>>>> What would you think of starting a release 1.1.0 ? There have been a lot
>>> of
>>>> bug fixes, and some improvements on the API (privacy, user profile,
>>> ability
>>>> to post conditions, ..), and also a long time since the last release.
>>>>
>>>> And also, I would like to propose Abdelkader Midani and Damien Gaillard
>>> as
>>>> committers . Abdelakader already did a lot of fixes, and Damien started
>>> to
>>>> contribute just one month ago but already did some interesting patches
>>> too.
>>>>
>>>> Regards
>>>>
>>>> thomas
>>>
>>>
>