One of the benefit of rewriting our Hibernate website is that we made our roadmaps more prominent. And in case of Hibernate OGM, we had to write it :)
Hibernate OGM, in a nutshell, is JPA for NoSQL backends (more here).
Gunnar and Davide have made significant forays into the feature set we wanted for our first stable version. This has made writing the roadmap much easier. You can get all the (up to date) details on Hibernate OGM's roadmap page. Here I will sum up what is between us and our first final version.
Option system: offer ability to define per property, per association, per entity or global options. Offered via annotations and via a programmatic API. This system will enable declarative denormalization, specific backend optimization settings and so on.
CouchDB support: offer CRUD support for CouchDB
Performance check: we keep a eye on them but a dedicated round of optimization will happen.
Better navigation with Neo4J: our initial mapping works but we know we can access associations in a faster way.
Batch changes: use the backend batching capability if it exists.
query support for known backends: add our current query support for Neo4J and CouchDB as much as possible.
cache query plans: it's all in the title :) Hibernate ORM already does that, we need to catch up.
I'm sure we will have to chop off a few additional tasks here and there but our goal is to stay focused on these as much as we can.