Done, here is the new 0.3 branch: https://github.com/JanusGraph/janusgraph/commits/0.3 and I bumped master to 0.4.0-SNAPSHOT with a CTR

Hey Chris, then I will create the 0.3 branch today. Good idea as some PRs might need to be rebased, but didn't you mean 0.3.2 and 0.4.0 releases? For the 0.2.3 release, I think we should just leave it

Hello, I have a concern about current CLA signing workflow. Currently we need to print a CLA agreement then fill it, then scan it then send it via email and then wait for an unknown amount of time

Clean-up complete. We're down to 290 open issues for now.

Hey @Florian, I merged the junit 5 upgrade PR this morning. I don't think we need a vote thread on creating a 0.3 branch. I know Jason has mentioned in some PRs that it probably should have already

Interesting to see an additional Couchbase backend! Have you considered hosting this backend in its own repo instead of adding it to a fork of the JanusGraph main repo? The DynamoDB backend and the

Thank you for adding a new storage backend for JanusGraph! My small suggestions right now: 1. Create a new branch in your repository, so you could update and rebase from upstream master branch. 2.

Looks like we have a consensus here on creating a 0.3 branch and ending support of the 0.2 branch after the next release. Assuming no objections come in until then, I will create the 0.3 branch after

Hi all, we are implementing Couchbase Storage backend for JanusGraph, we would like to get a feedback from you. Code is available here - https://github.com/malkostya/janusgraph/tree/couchbase_backend.

All tests that are using JUnitBenchmarkProvider need to be replaced. https://github.com/JanusGraph/janusgraph/search?q=JUnitBenchmarkProvider&unscoped_q=JUnitBenchmarkProvider Am Freitag, 1. Februar

Relevant to this topic: https://github.com/JanusGraph/janusgraph/issues/1395 I see that some benchmark tests are removed in that PR. Should we log them somewhere? I think we can provide links in that

Chris, thanks a lot for this report! Awesome work. I like the blurb for issues closing.

For upgrade of Cassandra, Cassandra support of 2.1 is downgrade to only patch critical things https://cassandra.apache.org/download/. There are currently multipledifferent backend which have support

There were 366 issues initially, 3 of which I already closed. I'm proposing that we can we close out an additional 88 issues shown below. I'll do the actual cleanup early next week. Here's the blurb

Hi everyone, Barring additional reviews I plan to merge the PR to upgrade junit to 5 next Wednesday once it hits lazy consensus. I don't think there's much in the pipeline that would affect it, but

+1 on EOL on 0.2 soon and branch off 0.3 from master. Jerry

I think that it will be too much pain to support more than 2 branches right now. I also think that 0.2.3 release should be the last one in the 0.2 branch and then we can support 0.3 and 0.4 versions.

There are currently two issues that we probably want to include in a release soon: Upgrade to TinkerPop 3.4.0 (#1364) Upgrade Cassandra to 2.2 (#1398) These two issues are too big in my opinion to be

+1 As someone who sometimes forgets to sign his commits I fully support bot checking.

I think we should deprecate Thrift soon and then remove it in the next minor version of JanusGraph after that, but we probably need to offer the same functionality for CQL as for Thrift before we can