There have definitely been a lot of good bug fixes and improvements contributed over the past few months. I would agree we are due for another release. One thing to note is I'd like to get the future roadmap sorted and updated so it's published with this release, so I'm looking to have a PR opened for that early next week.
Thanks Cole! On Fri, Oct 4, 2024 at 9:52 AM Ken Hu <kenhu...@gmail.com> wrote: > I agree, it's probably time to get a release out. I remember there were > users asking a little while ago when the next release would happen so I > think there are those in the community that are eager for a release. Thanks > for stepping up to manage this. > > On Thu, Oct 3, 2024 at 6:22 PM Cole Greer <cole.gr...@improving.com > .invalid> > wrote: > > > Hi everyone, > > > > Based on the work that has accumulated in 3.6-dev and 3.7-dev, as well as > > the > > time that has passed since our last release, I’d like to propose that we > > conduct a > > maintenance release in both branches by the end of the month. Both > releases > > would primarily consist of bug and security fixes. > > > > I would like to suggest that we start code freeze in the 3.6 and 3.7 > > branches on > > October 16th, which would set us up to have the release artifacts > published > > around October 28th. > > > > I will be looking into resolving all current open JIRAs with a priority > of > > Blocker > > prior to the start of code freeze (TINKERPOP-3050, TINKERPOP-3051, > > TINKERPOP-3052, TINKERPOP-3053, TINKERPOP-3076, TINKERPOP-3077, > > TINKERPOP-3086, and TINKERPOP-2700). I’m able to step in as release > manager > > as well. > > > > Please reach out here if you are working on any additional changes which > > you > > would like to have included in this release. > > > > Thanks, > > Cole > > >
