- [PROPOSAL] new repository for .NET driver
Re: [PROPOSAL] new repository for .NET driver
Debasish Kanhar <d.k...@...>
toggle quoted messageShow quoted text
I created a initial PR#2
to merge my codebase into official JanusGraph-Python repo you created. While the PR was successful, I wasn't able to add any reviewers, you or Florian or Misha. I'll need your inputs regarding copyright statements, liscence texts and other legal/similar formalities as well as other comments.
Also, had a query regarding status of merging fix #1060
into 0.2 stream of branched for JanusGraph, and if needed, I can work on it as that is currently only merged into master and 0.3. The discussion
here will need your comments too :-)
On Wednesday, 15 August 2018 04:15:27 UTC+5:30, Jason Plurad wrote:
Apologies for the delay, but I've created
Committers and maintainers should have access to it.
On Sunday, August 5, 2018 at 9:25:48 AM UTC-4, Florian Hockmann wrote:
Looks like we have reached consensus here. I have already created a stand-alone version of the library in its own repo:
I can create a PR to transfer it to JanusGraph as soon as we have a repo ready to target the PR against.
Am Dienstag, 31. Juli 2018 20:47:11 UTC+2 schrieb Misha Brukman:
Makes sense that client libraries should be in a separate repo than the server:
- enables a separate release cadence
- allows for a different set of maintainers, even in the same org
- each client library will be written in a different language
Having said that, this means that we'll have to keep track of version compatibilities between client library versions + server versions. Hopefully, they will be mostly backwards-compatible until a major version change.
Join firstname.lastname@example.org to automatically receive all group messages.