I haven't been really following the discussion, so apologies if this has already been mentioned, but I've liked the approach that Ogre and gremlin-scala have taken with respect to TinkerPop - they

I opened up Issue 1285 for the storage incompatibility of upgrade from 0.2.1 to 0.2.2. I will start a new voting thread for 0.2.2 when the release with a fix is ready.

If we agree on using SemVer, then that already tells us how to handle minor and major version. Taken from its summary: The only special case is that we can include breaking changes without having to

and users expect exactly that of a library that has a 0.y.z version. I think that makes sense for us. : I agree with you, after going through your points, it seems that going forward with 0.y.z as

Also, nice catch :)

I ended up replacing that check with the concept of the graph.storage-version when I wrote the upgrade for 0.3.x. Either we can hard code 0.2.2 as allowed or we can back-port the upgrade

I was trying to do some testing: JanusGraph 0.2.2 can not read graph from 0.2.1. org.janusgraph.core.JanusGraphException: StorageBackend version is incompatible with current JanusGraph version:

+1

+1

+1

+1

I just meant any breaking change which could also simply be that a new GraphSON version is used by default. It doesn't have to be a breaking code change in the library itself. That's simply part of

Adding new features (which requires a minor version bump) doesn't hinder users from upgrading in any way. So, I don't see why we would still maintain an older version without this new feature.: This

Hi all, We are working on a decentralized knowledge graph called Weaviate, and JanusGraph plays an important role in our software. We have a few people working on JanusGraph and they have some

I also think that we should keep the number of maintained branches / versions as low as possible, ideally only 1 branch will be actively maintained. Adding new features (which requires a minor version

+1

+1

Reviewed the docs and all looks good. +1

Reviewed the docs and all looks good. +1

Hi, Sarath and Madhan Your analysis makes sense. I did a quick test. From gremlin shell: gremlin> graph.getConfiguration().getLocalConfiguration().getProperty('index.search.solr.zookeeper-url') It