I'd very much like to get an update on this too! The most detailed recent comment I've found is from 10/23/14 in the gremlin-users group: https://groups.google.com/forum/#!searchin/gremlin-users/luca|sort:date/gremlin-users/PNS5DXnleuw/-ADMS-9zFlEJ
Hey guys, > OrientDB wants to support TP3, but we have clients running in production > with our Graph API that is TP2.x, so this would break almost everything. > > In our roadmap we'll provide TP3 binding as external module in 2.1, in > 2.2 it will be part of our default suite and it should be the new reference > API, while TP2.x will be supported for at least 3 further releases, or > maybe more. > > Lvc@ ---- The relevant github issues seem to be: Compliance with TinkerPop Blueprints 3.0 (assiged 14 days ago, lvca modified the milestone: 3.0, 2.1 on Jan 31) https://github.com/orientechnologies/orientdb/issues/2673 (early) tinkerpop3 support https://github.com/orientechnologies/orientdb/issues/2441 "We need to wait until BP 3 is final and we can start to support it as separate module." - lvca ----- According to https://groups.google.com/forum/#!topic/gremlin-users/tYHoyIAQCeo the TP3 roadmap is > We would like to stick to the following timeline: > 1. Coordinate with Apache mentors to get release approval. > 2. *April 5* -- release TP3 M8 (our first Apache TinkerPop release). > 3. Work with vendors to make sure they are completely happy with core/. > 4. *May 5th* -- release TP3 M9 (once released, no more API changes). > 5. Testing, docs, cleanup… > 6. *May 25th* -- release TP3 GA. -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
