Hi, I performed the following tests and it worked for me. +1 - Built the source code - Used built jars for Bulk Loader and Bulk Traversal using SparkGraphComputer and it worked for me. - Ran Gremlin

I built our application using v0.5.3 source code and ran it through our test suites. All tests passed. I also did some simple traversals and it worked fine. +1. Btw

Also, executed all TP tests for 0.5.3 with "mvn clean install -Dtest.skip.tp=false -DskipTests=true". All tests passed.

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

JanusGraph Discussions are set here: https://github.com/JanusGraph/janusgraph/discussions Right now it has default 4 categories: General, Ideas, Q&A, Show and tell. We may need to think about useful

Also, we can convert issues to discussions instead of closing them. I think, it might me useful often times. My vote is +1 I will go ahead and create base Discussions. In case anyone have any opposite

Absolutely agree. Users might not be very happy when they see their questions get closed on GitHub, and some of them are reluctant to use a mailing list for communication (not to mention Google Groups

Hi Yeah, it would like have such a feature for a long time. I see often issues the issue with google groups that just reactions is not possible and also including code snippets would be great. What i

Yeah that will be very helpful.

Hi, GitHub adds a new feature - "GitHub Discussions" which could be a handy place for user's collaboration. We often see that users open GitHub Issues to ask some question / etc. instead of going to

FYI, I've been poking around at this, and it won't work right now due to limitations within's AWS's Cassandra implementation. Upsetting indeed, as the MCS pricing (especially for smaller dev

OK, looks like we have a consensus on moving to GitHub Actions. Then we can start with the migration now. > I created an example for GitHub Actions by converting the foundation db travis ci to github

I created an example for GitHub Actions by converting the foundation db travis ci to github actions. I also add two extra workflow to check a editorconfig and check for license header which can be

Currently, we have 6 repos with CI pipeline. So we have to convert all of the repos with a CI pipeline. I already checkout how do you convert a dotnet project. I think will be helpful to do a step by

What would be required in terms of development in order to move to GitHub actions?

Hi, If that's the case, as for me it's obvious way to go. +1 for moving to GitHub Actions Best regards, Oleksandr

Hi I’m pretty sure about our limitations, which are just 20 concurrent runner at the same time for all public repos. The 2000 minutes are just for private repos (no build time limit for public

Hi, Moving to GitHub actions seems to be a good idea but we need to understand our limitations. This link says that GitHub actions gives us 2000 minutes per

Just noticed this one. Congrats, Jun Li and Hieu Nguyen It is great to see the hard work done inside eBay can be shared with the community! - Henry

Hi I did a small evaluation of GitHub Actions in February. GitHub Actions didn't allowed to run to open source project unlimited time at this time. This changed in April. Old results can be found