Ok, If everybody's ok for the release, I'll start the process asap. Can you please review all resolved tickets you opened and close them if it's ok ?
https://issues.apache.org/jira/issues/?jql=project%20%3D%20UNOMI%20AND%20status%20%3D%20Resolved%20AND%20reporter%20in%20(currentUser()) thanks, thomas On Wed, Sep 14, 2016 at 3:29 PM Thomas Draier <tdra...@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 <shu...@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 <tdra...@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 >> >>
