On Mon, Jul 04, 2022 at 10:29:29AM +0200, Florian Hockmann wrote: > Thanks for starting the discussion on this, Kelvin! Our last releases were > also 3 months ago which is roughly the release cadence that we aim for and > yes, getting an official release of the Go client out alone is already a good > reason for a release. > If nobody sees any import issues that are still open, then we can start code > freeze quite soon from my side.
Hi, I'm a newcomer to this project to have much weight in my opinion. However, regarding gremlin-go, I think it could be important to close the following issues first: Race condition issues: - gremlin-go: fix deadlock on (*DriverRemoteConnection).Close https://github.com/apache/tinkerpop/pull/1734 - gremlin-go: fix data race on serializers and deserializers initialization https://github.com/apache/tinkerpop/pull/1744 - gremlin-go: fix data race on localizer initialization https://github.com/apache/tinkerpop/pull/1745 Usability issues: - Cast Times serialization to int in Gremlin-Go https://github.com/apache/tinkerpop/pull/1743 Also, regarding gremlin-server, I faced the following issues while using gremlin-go: - gremlin-server does not reply with a timeout response to all timed out requests https://issues.apache.org/jira/browse/TINKERPOP-2769 - Race condition during script creation when using UnifiedChannelizer https://issues.apache.org/jira/browse/TINKERPOP-2765 You might want to give them a look to see if they could be a blocker. Thanks! Best regards, Roi
