Hi everyone, With the 4.0.0-beta.3 release underway, and a good amount of bug fixes and improvements landing in 3.7-dev and 3.8-dev over the last few days, I think now is a good time to call code freeze for the 3.7.7 and 3.8.2 releases. As long as there are no objections raised, both branches should be closed to major changes until the release is complete. As usual, minor docs tweaks and test updates may still permitted during this time. This will be a typical 7 day code freeze, and the VOTE threads for 3.7.7 and 3.8.2 should be expected on July 30. Please take this time to test the builds and review the documentation. I will be re-deploying the snapshot docs in both branches throughout the week.
Thanks, Cole On 2026/07/15 01:54:48 Cole Greer wrote: > Hi everyone, > > We've had a pretty high count of outstanding PRs over the last few weeks, but > as of today that's mostly resolved, and all of the big changes have landed. > With this, I think that now is a good time to call code freeze on the master > branch for the 4.0.0-beta.3 release. > > Considering this is a beta release, I'd like to suggest we run a slightly > abridged code freeze starting today, and ending on Monday July 20. Please let > me know if you have any concerns over lack of testing capacity within that > timeline. > > It should be fine for the remaining handful of small PRs to merge in the next > few days, as well as minor fixes and docs tweaks. These include: > > Fix doFinalReduction to remove keys #3501 > TINKERPOP-3259 Added proxy tests #3506 > Rename evaluationTimeout to timeoutMs #3508 > Added coverage for gremlin-console and gremlin-language #3512 > > During this time, the master branch will be closed to major changes. > > I still think we are about ready for the 3.7.7 and 3.8.2 releases as well, > however I'd like to suggest we delay those by a week or two and focus on > 4.0.0-beta.3 first. This is partially to ease the burden of managing 3 > releases at once, but as I'd like a bit more time to tinker with some more > dependency bumps and minor tweaks for these releases. > > Please let me know your thoughts regarding this plan. If there are no > dissenting opinions, I will proceed with the release process for 4.0.0-beta.3. > > Regards, > Cole > > On 2026/06/08 19:08:09 Cole Greer via dev wrote: > > Hi everyone, > > > > It's been a little while since our last release cycle, and I think it's > > time we prepare for another release. The master branch has made quite a bit > > of progress since beta.2, > > with the addition of graph binary streaming in all GLVs, improved type > > parity across drivers, and the new groovy-free server initialization > > system. There's a few other big > > items in review such as match(GQL) support and transactions in all GLVs > > which are expected to land soon. I think this set of features makes beta.3 > > a very compelling > > release on its own. > > > > 3.7.7 and 3.8.2 are looking pretty light at the moment, as most development > > effort has gone towards TP4 recently, but there are a few useful bug fixes > > in there, and these > > release lines would benefit with some dependency upgrades as well. > > > > I'm thinking of a rough release target of the end of June (with code freeze > > ideally starting next week). > > > > Please let me know if you have any thoughts on releases this month, as well > > as you if you have any in progress work you'd like to see included in the > > next set of releases. > > > > Thanks, > > Cole > > >
