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 easier for

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

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 merge v0

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. Also, it

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 g

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

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

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

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

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

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

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

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

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

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

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, 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

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

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