On Mon 2014-02-03 14:58, Sanne Grinovero wrote:
> On 3 February 2014 13:34, Emmanuel Bernard wrote:
> > On Sat 2014-02-01 18:47, Sanne Grinovero wrote:
> >> On 27 January 2014 10:32, Gunnar Morling wrote:
> >> > Looking at the issues which have been addressed or are work in progress
> >> > since
On 3 February 2014 13:34, Emmanuel Bernard wrote:
> On Sat 2014-02-01 18:47, Sanne Grinovero wrote:
>> On 27 January 2014 10:32, Gunnar Morling wrote:
>> > Looking at the issues which have been addressed or are work in progress
>> > since the last release [1] I don't think we need a tag.
>>
>> +1
On Sat 2014-02-01 18:47, Sanne Grinovero wrote:
> On 27 January 2014 10:32, Gunnar Morling wrote:
> > Looking at the issues which have been addressed or are work in progress
> > since the last release [1] I don't think we need a tag.
>
> +1 especially as I understand JPA 2.1 is backwards compatib
On 27 January 2014 10:32, Gunnar Morling wrote:
> Looking at the issues which have been addressed or are work in progress
> since the last release [1] I don't think we need a tag.
+1 especially as I understand JPA 2.1 is backwards compatible
Sanne
>
> Feature-wise we've primarily been working o
Looking at the issues which have been addressed or are work in progress
since the last release [1] I don't think we need a tag.
Feature-wise we've primarily been working on CouchDB support (that needs
some follow-up issues though and thus is not yet releasable imo), the
option stuff (the first usa
To follow up on the PR migrating OGM to ORM 4.3. I think it is the right
thing to do but I wonder whether we should do a tag / release of
Hibernate OGM before that. So that people still using the JPA 2.0 series
have a final version and a point for fork.
What has happened between the latest OGM ver
