Alexandr Porunov <alexand...@...>
toggle quoted messageShow quoted text
Jason has opened a voting for 0.3.0 release here: https://groups.google.com/forum/#!topic/janusgraph-dev/9evIOVkGPRo
If everything will be OK, then I assume the release will be after August 3, 2018, 3:40 PM EDT.
On Tuesday, July 31, 2018 at 10:25:06 PM UTC+3, Sarath Kumar wrote:
Do you have a rough timeline on when you plan to release 0.3.0?
On Tuesday, July 17, 2018 at 2:30:42 PM UTC-7, Jason Plurad wrote:
v0.3.0 release updates:
* The solution for Issue 1159 has been identified. It requires an extra configuration property in the properties file. Debashish Kanhar
has volunteered to improve the documentation in the OLAP chapter for this.
* PR 1161 needs another committer review/approval. It contains fix rollups from the 0.2 branch.
Once these have both cleared, I'll prepare the 0.3.0 artifacts for vote and release.
On Monday, July 9, 2018 at 3:55:32 PM UTC-4, Jason Plurad wrote:
PR 998 is now merged. Thank you!
I opened Issue 1159
today regarding Guava errors with Spark clusters. Spark and OLAP works with spark.master=local[*] since it only uses jars from the JanusGraph distribution. Only when running on a standalone Spark cluster is the issue demonstrated because of Guava jar conflicts between the Spark distribution and JanusGraph. I believe this issue needs to be resolved for 0.3.0.
Any other concerns or input from the committers or community? Thanks.
On Thursday, June 28, 2018 at 5:35:14 PM UTC-4, Jason Plurad wrote:
We need another committer review and approval on https://github.com/JanusGraph/janusgraph/pull/998. Many thanks to community member Alexandr Porunov who has helped review the PR also. Because of the storage format changes coming with the new schema constraints, I don't think we can defer this PR from v0.3.0.
The other PR currently tagged for the milestone is waiting on updates from the author so it can be deferred.
Any other concerns or input from the committers or community?
On Tue, May 22, 2018 at 9:37 AM Florian Hockmann wrote:
Thanks a lot, Jason! I only remembered that there were release candidates for the 0.1.0 release, but I guess that was a special case being the very first JanusGraph release.
Anyway, next time we'll just take the suggested approach and build it on our own. I didn't realize when I asked for a release candidate that it really only requires a
mvn clean install -Pjanusgraph-release -Dgpg.skip=true -DskipTests=true
Am Montag, 21. Mai 2018 18:42:41 UTC+2 schrieb Jason Plurad:
Thanks for the suggestion, Florian. I don't think we published release candidates in the past, instead encouraged developers to build the release from source code. Getting more feedback on the 0.3.0 release would be fantastic though.
Releases on the GitHub releases page are tied to a specific tag in git, so I'm not sure how to publish a candidate release there right now. In the meantime, I uploaded the latest here:https://ibm.box.com/v/janusgraph-release-candidates
On Friday, May 18, 2018 at 2:37:14 PM UTC-4, Florian Hockmann wrote:
Would it be possible (without requiring too much effort) to publish a release candidate of 0.3.0? Then we could deploy that in our staging environment and give feedback, especially for the new strict schema support.
Am Montag, 2. April 2018 18:48:47 UTC+2 schrieb Jason Plurad:
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/be87d666-5bd6-460e-8b7e-f873f18494cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.