Hi All,

Our current developer documentation states that "In general, TinkerPop will
attempt to support the current LTS version for a particular major version
for the lifetime of its minor and patch releases." Given the length of time
that we are currently supporting minor versions of TinkerPop and how
quickly some LTS versions can change (e.g. Go only supports versions for
one year), I would suggest that we loosen this to the following: "In
general, TinkerPop will attempt to support the current LTS version of a
runtime for all currently maintained versions. A deprecation notice will be
applied to the last release of TinkerPop that will support that outdated
runtime and the runtime will be updated in the following release."

This would allow us to more easily change the LTS version of a runtime
during the maintenance window of a TinkerPop minor release. The two
examples that could be used right now to demonstrate this are Node.js and
Go. Currently, 3.5-dev is using Node 10 which hasn't been supported since
April 2021 and Golang 1.17 which hasn't been supported since August 2022.

I propose that we change the wording in our documentation about runtime
support and then go ahead and add a deprecation warning to 3.5.6 about Go
and Node.js and then update them in 3.5.7.

Thanks,
Ken

Reply via email to