Hi, We currently maintain the JanusGraph Docker images in their own repository: https://github.com/JanusGraph/janusgraph-docker While this comes with some benefits, like making it probably

The JanusGraph Technical Steering Committee is excited to announce JanusGraph 1.0.0-rc2, the second release candidate of the upcoming 1.0.0 release. JanusGraph is an Apache TinkerPop enabled property

We have already a number of features targeting JanusGraph 1.0.0, but we didn't add possibility to select `cql` or `scylla` storage backend implementation yet which forces users to follow a complex and

The JanusGraph Technical Steering Committee is excited to announce the release of JanusGraph 0.6.3. JanusGraph is an Apache TinkerPop enabled property graph database with support for a variety of

I tested: 1. basic SparkGraphComputer traversal 2. Amazon Keyspace interaction LGTM! I should have backported https://github.com/JanusGraph/janusgraph/pull/3396 to the 0.6 branch as well but I somehow

This vote is now closed with a total of 3 +1s, no +0s and no -1s. The results are: BINDING VOTES: +1 (3 -- Oleksandr Porunov, Florian Hockmann, Jan Jansen) 0 (0) -1 (0) NON-BINDING VOTES: +1 (0) 0

Everything looks good to me, we have to create a docker release. VOTE +1

I checked the links, and everything looks good to me. VOTE +1 Von: janusgraph-dev@... <janusgraph-dev@...> Im Auftrag von Oleksandr Porunov Gesendet: Montag, 20. Februar 2023 23:15 An:

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

I propose to start release process for JanusGraph 0.6.3. It already includes a number of good fixes and we didn't had a bugfix release for quite some time now. The only unmerged PR I see which is

Hi, in case you haven’t noticed already: We have recently changed our branching strategy. Instead of letting PRs target a branch like v0.6 and then merge the PR first into v0.6 and afterwards

Thanks, Oleksandr. I saw that PR when I composed the list but thought that #3022 already included the important changes. But sure, then we should also include #3327 for the next announcement.

Thank you Florian for starting this topic. For future announcements: In addition to possibility to remove composite index entries there was added possibility to remove mixed index entries in #3327 So

Related discussion regarding publishing with `org.janusgraph` or `org.janusgraph.commit` groupId: https://github.com/JanusGraph/janusgraph/discussions/3374

The JanusGraph Technical Steering Committee is excited to announce JanusGraph 1.0.0 RC1, the first release candidate of the upcoming 1.0.0 release. JanusGraph is an Apache TinkerPop enabled property

Related PR for reference: https://github.com/JanusGraph/janusgraph/pull/3364

Yes, I like that idea. Let's publish rc1 sooner and release `1.0.0` or `0.7.0` in January depending on what we decide. As for snapshot releases I will go ahead and prepare some PR and we can discuss

Thanks for bumping this thread again in the discussion for the 1.0.0 release, Oleksandr! > Basically, I think it's possible to configure different publishing flows (either to sonatype for official

My intention here is that we try to release from master soon-ish, like in January ideally. We have features on master that were implemented about a year ago already and some dependency updates that

You are right that these breaking changes regarding ElasticSearch side will be affecting only those users who want to switch using ElasticSearch 8. Users On ElasticSearch 6 and 7 won't be