I just did a quick test of the two distribution archives which just consists of starting JanusGraph Server and connecting to it via the remote console to create a vertex. For the full distribution, I

Thanks for fixing this! I performed the same tests again and now everything looks good. So: VOTE +1 Von: janusgraph-dev@... <janusgraph-dev@...> Im Auftrag

Hi, In case you haven’t seen it already: TinkerPop now has a Discord server, and that Discord has its own channel for implementers which of course includes graph databases like JanusGraph. I think it

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 an

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: https://lists.lfaidata.foundation/g

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 a

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 could in g

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 +1 Von: janusg

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 a differen

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 just

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 process i

I’ll interpret the lack of replies as lazy consensus and proceed with the release process. Von: janusgraph-dev@... <janusgraph-dev@...> Im Auftrag von Flori

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 full bin

Thanks for your feedback, Oleksandr. We now have 3 people here on the dev list in favour of starting a Discord Server and no one against it. Only one user responded on janusgraph-users in the thread y

Hi, I would like to start a discussion about our next release(s) as there were multiple requests from the community already. Our last release (0.6.2) was also already half a year ago (May 31) and our

Hi Dustin, sure, that will be included. I should have mentioned that probably: 0.6.3 will include all issues / PRs tagged with the 0.6.3 milestone: https://github.com/JanusGraph/janusgraph/milestone/2

Yes, a release candidate probably makes sense for the 1.0.0 release. I think we don’t need a formal voting process for a release candidate. So, if there are no objections, I start preparing such a rel

Elasticsearch 8 is of course a good point. But do we need to support that directly in 1.0.0? Elasticsearch 7.17 seems to be still supported roughly until 9.0.0 gets released if I understood their EoL

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 in

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 rel