Hi, I have also thought about this aspect recently since I wanted to drop support for .NET Standard version < 2 for Gremlin.Net for 3.5.0. That would be in line with your suggestion if I understand it correctly as the current recommendation from Microsoft is to only support .NET Standard 2. I am definitely in favour of your suggestion. Users who want to stay on an older runtime version, can stay on a lower TinkerPop version which we usually support for another year or so. That should be enough time to update.
Regards, Florian -----Ursprüngliche Nachricht----- Von: Jorge Bay Gondra <[email protected]> Gesendet: Dienstag, 21. Januar 2020 15:28 An: [email protected] Betreff: [DISCUSS] Node.js runtime support Hi, I wanted to formalize some kind of policy regarding Node.js runtime support. This may apply to other runtimes (I imagine C#). I propose that when a new minor version of TinkerPop is released, the runtime supported for that new branch would be the active LTS <https://github.com/nodejs/Release> at the time. Those runtime versions will be supported for the lifetime of the branch. For example, if we release 3.5.0 tomorrow, the JavaScript GLV will support Node.js 10+, future patch releases of 3.5 will continue supporting the same runtimes. Note that within the TinkerPop project minors versions act like majors in semver <https://github.com/apache/tinkerpop/blob/master/docs/src/dev/developer/contributing.asciidoc#versioning> . Jorge
