I skimmed over the docs and everything looks as expected. The changelog and the release on GitHub also look good. I also downloaded the zip archive, extracted it, started JanusGraph with

Thanks for catching that. It's been updated.

Hello Chris, Right now a small mistake in https://github.com/JanusGraph/janusgraph/releases/tag/v0.2.3 It says: Version 0.2.2 (October 9, 2018) I assume it should be: Version 0.2.3 (May 21, 2019)

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

I already figured out the fix and submitted a PR, https://github.com/JanusGraph/janusgraph/pull/1596. The tests in .travis.yml.cassandra are all passing and the PR is pretty small. If anyone has time

Chris, thank you for this work! Sure, take as much time as you need!

I will not be able to submit for a vote today. I realized I needed to do additional testing on Cassandra versions, using travis.yml.cassandra, and I got some failures in cql for version 3.11.0. I'm

I'm hoping to submit for a vote on Monday. One piece of advice that I wish I had done is to pick a cutoff date where you'll push everything out to the next release so you don't have to worry about

Notice, that PRs 1547 and 1588 are targeting master branch (which is 0.4.0 release). If you want those PRs to be included into 0.3.2 and 0.4.0 releases you should rebase your PRs and target 0.3

I am planning to release 0.3.2 version just after Chris releases 0.2.3 version (If everything goes smoothly 22 May is the day of starting 0.2.3 release). I think 0.3.2 release will be available either

What is the current timeframe for the next 0.3 release? erinc just submitted 2 PRs that are crucial for our product release slated for June end. Would it be possible to have an early June 0.3.x

We've just submitted two prs which have been approved against the 3.x line. We'd like to make sure they get included in our next product release but we can only target officially released versions of

Hi Chris, Yes, please add me to the thread and I'll take it from there. Thanks, Misha

I reached out to John Mertic from the linux foundation about the CLA automation tool and was told it is now ready for Prime time. He also said he could help get us onboarded. Would it be easiest if I

I looked at all the PRs targeting 0.2 and currently I'm only really optimistic about 1575 making it in for the release. Right now the only thing I would consider delaying for is 1479, the

The problem is just that we recently decided to close branch 0.2 and only make a last release of that branch and then close it for development. Any new pull requests that now target 0.2 could

Hey Pylyp, I'll see if I can do a review on all 4 PRs tomorrow, but it'll require a second approver and all the comments resolved to merge. The size looks reasonable and they all have tests so I think

Thanks Chris, All PR were opened for 0.2 branch. They

We regularly merge commits upstream. You just need to worry about submitting the Pull Request you want to get in. If you want to take care of merging it into all branches here's a comment with an

Hello, My current intention is still to push the 0.2.3 release on May 22nd and I'm actively working on the 2 remaining pull requests to meet that deadline. If there's something you would like to get