I'd like to suggest closing the loop on removing neo4j-gremlin from master as was discussed here some years ago: https://lists.apache.org/thread/lxn4s9fs8rzggm0jlnffnphfpqnpn3h8
i think it's time to remove that code. We didn't even include it as an artifact in the first 4.0.0 beta release and the dependencies are starting to really get stale. We'd not want those to become a security issue. I can do the removal and associated documentation before code freeze is up. Please let me know if there are any concerns. On Mon, Mar 23, 2026 at 8:30 PM Yang Xia <[email protected]> wrote: > Hi all, > > As mentioned in the previous thread on the beta and maintenance releases ( > https://lists.apache.org/thread/3v6v34o3n1j1ds9gr0fk60qf6nooyhv8), I'd > like to initiate the code freeze on master, 3.8-dev, and 3.7-dev branches. > > Within this code freeze period, we don't plan to consider any new major > PRs or features, but will accept non-breaking fixes and documentation > updates. The current open PRs we are reviewing for consideration: > > * Optimize no-GValue fast path in P.setValue(): > https://github.com/apache/tinkerpop/pull/3339 > * Add Request Interceptors for Javascript: > https://github.com/apache/tinkerpop/pull/3337 > * JS Translator and gremlin-mcp improvements: > https://github.com/apache/tinkerpop/pull/3336 > * TINKERPOP-3237 Add custom type serializer API for gremlin-go: > https://github.com/apache/tinkerpop/pull/3335 > > The VOTE threads are expected starting March 30th, and the releases fall > in the following week. > > If there are any objections to this timeline, or if there are any other > desired changes before the release, please raise in this thread. > > Cheers, > > Yang >
