+1

+1

+1

+1

Hello, We are happy to announce that JanusGraph 0.3.1 is ready for release. The release artifacts can be found at this location: https://github.com/JanusGraph/janusgraph/releases/tag/v0.3.1 A

Hello, We are happy to announce that JanusGraph 0.2.2 is ready for release. The release artifacts can be found at this location: https://github.com/JanusGraph/janusgraph/releases/tag/v0.2.2 A

> I'm still concerned about the number of releases which will need to be actively maintained as that keeps on increasing. I would think as long as the drivers are largely backwards compatible, you'd

Nice work, thanks for getting that done!

I meant it in following sense. We go forward with releasing first version which will be tagged as 1.0.0 Now, this would be our current set of features, and as and when bugs are found out, a new patch

JanusGraph is translated to Russian and Ukrainian languages: https://ru.wikipedia.org/wiki/JanusGraph https://uk.wikipedia.org/wiki/JanusGraph

I don't get what you mean with this. How can the latest minor version be 1.1.1? Minor version just means the second element of the version number which would be '2' in the version 1.2.3. My proposal

Hi Florian, Okay, thanks for pointing that out, and I do see few issues with my idea, as in inde[endently bumping major and minor versions of clients by itself without upgrade to JanusGraph is

I think JanusGraph 0.2.2 can be released for voting already. I think that PR 1273 has to go into 0.3.1 also.

Update: Added JanusGraph into the list of notable graph databases: https://en.wikipedia.org/wiki/Graph_database

+1 on using the bot for these checks. Am Sonntag, 23. September 2018 03:47:44 UTC+2 schrieb Misha Brukman:

Thanks for getting the discussion on this topic started! One disadvantage I see with your proposal is that those version numbers imply semantic versioning but they prevent the libraries from making

Update:JanusGraph article was created in the main space. The link is the next now: https://en.wikipedia.org/wiki/JanusGraph

HBase is strong consistency (as compared to eventual consistency). I agree the chapter is confusing. What it says is that because the backends lack multiple row transaction consistency (for both

Hi All, A few days back, Florian had started a Discuss thread regarding how should we version the upcoming GLV libraries for Python and DotNet. After discussions and lazy consensus it felt like we

Agree with you. I also think that PR 1230 is a good enhancement for 0.3.1.