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 Ga
+1 on my side for both release and committers.
> On 14 Sep 2016, at 14:53, Thomas Draier 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, ..),
+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 mo
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 wrote:
> +1 for release
>
> +1 for Abde
Hi,
1/ for the release, no problem.
2/ regarding the committers, such kind of discussion should stand on
private mailing list (dev is a public mailing list). So, please, start
the discussion (or even a formal vote) there.
Regards
JB
On 09/14/2016 02:53 PM, Thomas Draier wrote:
Hi there,
W
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,
Done from my side.
cheers,
Serge…
> On 20 sept. 2016, at 10:29, Thomas Draier wrote:
>
> 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/
Done as well.
Regards,
Q
On Tue, Sep 20, 2016 at 11:15 AM, Serge Huber wrote:
> Done from my side.
>
> cheers,
> Serge…
>
> > On 20 sept. 2016, at 10:29, Thomas Draier wrote:
> >
> > Ok,
> >
> > If everybody's ok for the release, I'll start the process asap. Can you
> > please review all reso
Done as well, only kept documentation one as we probably need to update the
documentation with all the recent changes.
Cheers,
Chris
> On 20 Sep 2016, at 11:41, Quentin Lamerand wrote:
>
> Done as well.
> Regards,
> Q
>
> On Tue, Sep 20, 2016 at 11:15 AM, Serge Huber wrote:
>
>> Done from m
Hi all,
I submit Unomi 1.1.0-incubating release to your vote.
Staging Repository:
https://repository.apache.org/content/repositories/orgapacheunomi-1005/
Git tag:
unomi-root-1.1.0-incubating
Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12335442&styleName=&projec
In case you’re wondering you can find the package tarballs (source+binaries)
here :
https://repository.apache.org/content/repositories/orgapacheunomi-1005/org/apache/unomi/unomi/1.1.0-incubating/
I’ll try to do some basic verifications but I guess we need some mentors to
help us out with the r
Ok sorry but it’s a -1 for me because :
1. We generated binaries in the staging repository, we should instead add a
profile to seperate the binary distribution release so that we can put it
elsewhere
2. We need to cleanup the package/LICENSE file that has some obsolete
information.
cheers,
Ok,
I'm preparing a new release without the GPL license (I cannot actually find
any reference in transitive dependency that references it), and without the
binary package (which can now be disabled by activating the src profile)
thanks,
thomas
On Tue, Sep 20, 2016 at 5:54 PM Serge Huber wrote
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 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
> On 14 Sep 2016, at 15:30, Serge Huber 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 /
Kar
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 wrote:
>
>
>> On 14 Sep 2016, at 15:30, Serge Huber wrote:
>>
>> I’m
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
> On 14 Sep 2016, at 17:00, Serge Huber 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
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 wrote:
>
>
>> On 1
19 matches
Mail list logo
