Hi Cole, I'd like to mention that I'm working on a PR for TINKERPOP-3013 that I hope will be landing soon. I'd like that fix to go into the 3.7.1 release.
Thanks, Ken On Fri, Nov 10, 2023 at 4:29 PM Cole Greer <cole.gr...@improving.com.invalid> wrote: > Hi everyone, > > As we approach the end of the year, I think it’s time that we get started > on the next set of minor releases for TinkerPop. This would include 3.5.8, > 3.6.6, and 3.7.1. > > There are a couple of open PR’s at the moment which appear to be ready to > merge in the next few days: > > > * Bytecode support for HTTP requests: > https://github.com/apache/tinkerpop/pull/2336 > * TINKERPOP-2988 Add requestId checking to Javascript and Python > drivers: https://github.com/apache/tinkerpop/pull/2329 > * TINKERPOP-2830 Handle User-Agent from HTTP Requests to server: > https://github.com/apache/tinkerpop/pull/2328 > * TINKERPOP-2984 Replace Moq with NSubstitute: > https://github.com/apache/tinkerpop/pull/2319 > > Additionally, there are several smaller PR’s regarding configuration and > dependency tweaks which I believe can be reviewed and voted on in the next > few days as well. > > I propose that we initiate code freeze on 3.5-dev, 3.6-dev, and 3.7-dev > today, with the intent that the PR’s mentioned above, as well as other > small non-breaking fixes can still be merged in the next few days. With > this timing, the VOTE threads could be expected starting November 20, and > the releases would be expected within the first week of December. If there > are any objections to this timeline, or if there are any other desired > changes before the release, please reply to this thread. > > I would additionally like to propose that we plan this to be the final > release in the 3.5.x line, and that we leave 3.5-dev frozen indefinitely. > This could of course be reversed in the future if a critical need arises, > but unless there are any objections, I believe it’s best that we return to > actively working on no more than 3 branches. > > Thanks, > > Cole Greer >
