Hello Abhay, Yes, the version 0.3.2 doesn't support CQL for OLAP queries. The next version (0.4.0) will support it.

This version doesn't support CQL for OLAP queries. Thanks, Abhay

* Verified the release tag is correct * Downloaded source code archive and built a distribution * Imported KEYS file and verified GPG signatures on pre-built distribution files* Unzipped the pre-built

Jason, Thank you for finding this mistake! I've updated the tag to point to a correct commit.

I attempted to build v0.3.2 from source code, but the version on the v0.3.2 release tag is incorrect https://github.com/JanusGraph/janusgraph/blob/v0.3.2/pom.xml#L5 The latest on the 0.3 branch

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

Sorry for that. I missed it when I was editing Jason's post. The correct preview site for documentation is: https://porunov.github.io/docs.janusgraph.org/0.3.2/index.html

The preview site of the docs currently points to a version hosted by Jason. Is that really the right version of the docs for 0.3.2? Am Montag, 17. Juni 2019 17:04:07 UTC+2 schrieb Oleksandr Porunov:

Florian, My "lessons learned" are not yet complete (it will be after the release). But I have created a draft PR so that it would be a little bit easier to proceed with the release:

Hello, We're going to be hosting another JanusGraph online meetup on Wednesday July 24. There was a great turnout for the last one with lots of interactive Q&A from the audience. If you're interested

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