On 27 January 2014 10:32, Gunnar Morling <gun...@hibernate.org> 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 on CouchDB support (that needs > some follow-up issues though and thus is not yet releasable imo), the > option stuff (the first usage of it is CouchDB and associations for MongoDB > where the PR still is pending) and named native queries (which has been > done after the first changes for CouchDB). > > Based on that I'd say Beta4 is the last JPA 2.0 version and can serve as > base for forks should anyone be interested in that. > > --Gunnar > > [1] > https://hibernate.atlassian.net/issues/?jql=project%20%3D%20OGM%20AND%20fixVersion%20%3D%204.0.0.Beta5%20ORDER%20BY%20status%20DESC%2C%20priority%20DESC > > > 2014/1/27 Emmanuel Bernard <emman...@hibernate.org> > >> 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 version and now - aside from a >> long time that is :) >> >> Emmanuel >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
