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

I’ll interpret the lack of replies as lazy consensus and proceed with the release process. Von: janusgraph-dev@... <janusgraph-dev@...> Im Auftrag von Florian Hockmann Gesendet: Mittwoch, 11. Mai

Hi, it has been nearly 4 months now since we released 0.6.1 and I just merged the PR to update TinkerPop to 3.5.3 [1]. So, I think that it makes to release 0.6.2 soon. Given that the release

This thread didn’t really see much activity and I’m not sure how to interpret this. Are people here in favour of switching to Discord but don’t have much else to add to the discussion? Or do you

Vote for Discord. Many questions on Gitter are not getting answered likely due to its lack of popularity. I personally haven’t been using Gitter for a long time because I don’t use it for any

Hi, we’re currently using Gitter as our chat system where we have two chat rooms, one mostly for users to ask questions and one to discuss development issues. We already discussed moving to

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

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

I tested the docker image build works fine. Thank you for setting up an automated release process. VOTE + 1 Von: janusgraph-dev@... <janusgraph-dev@...> im Auftrag von Florian Hockmann

I just performed a basic smoke test of both distribution archives, and everything worked as expected. Great to see the first release based on the new release automation happening 😊 VOTE

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

The PR for automatic releases is here: https://github.com/JanusGraph/janusgraph/pull/2941 Best regards, Oleksandr

Hi All, I have a strange behaviour while using the addConnection method for creating JG schema constraints. It seems it creates duplicated connections in some cases. Please see below how to reproduce

Hi Florian, It will definitely help me to try some parts of automation for 0.6.1 release. I will work on it today's evening and tomorrow. If I bump into the problem and can't start a release till

Hi Oleksandr, automating the release process or at least parts of it would definitely be great! Right now, we have all issues and PRs closed that are linked to the milestone for 0.6.1 so we

Hi, I'm in favor of releasing 0.6.1 version. That said, it would make sense to automate the releasing process as Jan mentioned. I'm planning to try to work on automation or partial automation this

Hi I think it would be great to get 0.6.1 out. I would like to checkout https://github.com/JanusGraph/janusgraph/pull/2916. If needed, i want this to be part of 0.6.1 If you want be release manager,

Given that there haven’t been any responses, I assume that there are no major objections to releasing 0.6.1 soon but that there is also no high interest in getting it out as a hotfix release as soon

Hi, we wanted to release patch versions shortly given the CVE in Log4j to mitigate it in the Elasticsearch version we distribute with the pre-packaged distribution:

A critical security vulnerability was reported in Apache Log4j 2 on December 9, 2021: CVE-2021-44228 [1]. JanusGraph itself is not directly affected by this vulnerability as it still uses log4j 1.2