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

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

Hi, Upgrade to ElasticSearch 8 will be a breaking change in regarding to Geoshape properties because we won't have Prefix Tree indexing strategy anymore. Users will need to do migration of any indexes

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

That sounds really awesome! Just one thought: Shall we do a RC release (e.g. 1.0.0 RC1) before the official 1.0.0 release? There are quite some breaking and major changes in 1.0.0, and I feel we

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

Hi Florian, Would this release contain the commits in this PR - https://github.com/JanusGraph/janusgraph/pull/2904? v/r Dustin

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

Thanks for starting this thread! Just want to mention there is an open PR for Redis cache integration: https://github.com/JanusGraph/janusgraph/pull/3100

Hello, I would like to start a topic about JanusGraph db-cache we have today and ways to improve it for distributed environments. I want to split this topic on several issues I see with this cache: 1)

Hi Team, Here are the results from the August 2022 license scan of the JanusGraph project. The scan was performed using the Linux Foundation Fossology server. Licenses and copyrights were