I have reviewed and added #1601 into milestone. We should then figure our why those tests are falling. I am not sure if #1406 will be fixed soon. If it is then I would like to get it into the

As an FYI. I found some changes in 0.3 that will make my release notes not entirely accurate for the 0.3.2 and 0.4.0 releases. My plan is to open a PR updating RELEASING.md with my notes. I'll do my

Hi everyone, I am going to make "0.3.2" release PR after conflicts in #1609 is resolved and the PR is merged. After that I am going to finalize artifacts, docs and start a voting process. I am going

This vote is now closed with a total of 6 +1s, no +0s and no -1s. The results are: BINDING VOTES: +1 (3 -- Jason Plurad, Florian Hockmann, Alex Patrikalakis) 0 (0) -1 (0) NON-BINDING VOTES: +1 (3

Binding vote +1. Good job on the docker and stability/quality improvements.

* Imported KEYS file and verified GPG signatures on pre-built distribution files * Downloaded source code archive and built a distribution * Unzipped the pre-built distribution and did manual testing

I just tested to build the docker image for janusgraph and created a PR. The image works perfectly with my changes in PR https://github.com/JanusGraph/janusgraph-docker/pull/17. My VOTE is +1.

We have 3 +1 votes, however we have only 1 +1 votes from a TSC member, which falls short of the 3 required for the release. Chris Hupman Oleksandr Porunov Florian Hockmann * * denotes TSC member Due

I think that we should not remove support for Thrift for 0.4.0 as we only gain full support for the successor CQL in 0.4.0 with the added support for Spark (PR #1436). I think we should first

I was looking into libthrift again and realized I did a bad job keeping up with us. Were most of the issues figured out in PR 1400 and PR 1436? What else is there to do before we can remove libthrift

I have downloaded .tar.zip, extracted it, built jars, included into my personal project with different integration tests. Ran integration tests. All tests have passed except some tests which require

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