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

Agreed, that sounds like the best approach. We don't have to fix everything at once if it was already broken in past releases. Am Freitag, 14. Juni 2019 01:34:15 UTC+2 schrieb Oleksandr Porunov:

Hello Chris, Yes, this is the only PR right now for 0.3.2 release. After that I can start a release preparation.My vote is also to move them into an allowed failure group and making necessary issues

Hey All, Some of the extended Cassandra tests are failing on the 0.3 branch. Details can be found in PR 1601. I think the tests have been broken since 0.3.0 was released. Based off the milestone this

I agree that #1513, #734, #1540, and #1541 can be added to any release and do not require a major release. Since I'm pretty sure I'm the one that tagged them in the first place I'll move them to

Hi, now that 0.2.3 is released and 0.3.2 comes closer to a state where it can be released, I want to start the discussion for the 0.4.0 release. It will be a major release with a substantial number of

Announcement sent and I'll add it as a step to the releasing docs. Technically anyone can make an announce thread and the TSC ultimately decides who can add as a release manager. Since the docs

I think it should be the release manager in general to make the announcement. I don't see a reason why only TSC members should be able to do that if a committer can perform the release itself. Am

I may be reading into formality a bit too much with this, but historically releases the releases have been announced on behalf of the technical steering committee. The wording could simply have been

I'm out tomorrow, but I was able to get a PR out for the RELEASING.md updates. I plan to look at it again with fresh eyes next week, but I feel like it's ready for feedback. Also, I think we should

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