Thanks for bringing this up, Jorge. There were a handful of blockers that everyone seemed to agree on that prevented us from going right to GA for 3.2.6/3.3.0. Here were some of the key blockers that I remember:
https://issues.apache.org/jira/browse/TINKERPOP-1731 - docker build needs to work for .NET - pretty crucial https://issues.apache.org/jira/browse/TINKERPOP-1734 - it seems we have a pattern for DSLs - just need to document it https://issues.apache.org/jira/browse/TINKERPOP-1730 - we need everything supporting the latest GraphSON version for full Gremlin support finally - and we don't have a ticket yet that i know of - but we really should figure out how to fully test .NET Gremlin against the test suite. Not sure how that will work - it will need some thought and will need to be generalized so that we can use that same pattern against future GLVs that aren't on the JVM at all. I think we should focus on trying to clear these issues (and others if they exist) for 3.2.7/3.3.1 so that we can go full GA with .NET for those releases. Does that sound like a plan? On Fri, Sep 1, 2017 at 8:48 AM, Jorge Bay Gondra <[email protected]> wrote: > Hi, > I think starting with a release candidate of the Gremlin.Net language > variant package was a good choice for the first official release of the > package after being included in TinkerPop project. > > Now that the release candidate has been individually checked, it would be > nice to move forward and make a GA release of 3.2.6 and 3.3.0, that way it > can be the default download on nuget.org > <https://www.nuget.org/packages/Gremlin.Net> (prereleases are not shown on > dotnet toolchain by default) and we can make it easier for newcomers to use > the GLV. > > Cheers, > Jorge >
