In the worst case, if there were things we wanted added to 3.6.0 that weren't quite ready for code freeze we could release 3.5.2 and hold the freeze on its branch while 3.6.0 finished. I just wouldn't want a 3.6.0 to force a few commits into a fast turnaround release of 3.5.3. That might give some buffer if we wanted, but it would be nice if it could all just land at once.
On Mon, Dec 13, 2021 at 3:07 PM Kelvin Lawrence <[email protected]> wrote: > The work for adding a regex TextP is sitting on the TINKERPOP-2652 branch. > I still need to write the docs and add one last Java test but otherwise > it's close to PR ready. I would like to try and get that into 3.6 which I > think I should be able to do before the cutoff. > In general capturing what we have now into a set of releases makes sense > to start the year with a pretty clean mainline branch that we can iterate > on. > Kelvin > > On Monday, December 13, 2021, 06:44:46 AM CST, Stephen Mallette < > [email protected]> wrote: > > I'd like to propose we do a release for the new year, with code freeze > starting conveniently on Friday December 31. > > I think we should also consider making this the last release of 3.4.x. > > It occurred to me that 3.6.x doesn't have a name yet. Working in reverse > (never done it this way before), I have a Victorian/Steampunk sorta Gremlin > image that could be used for a logo, and searching around for related music > came across a whole genre of Steampunk Music. First artist group I clicked > on, Deus Ex Vapore Machina, has a song called "Tinkerheart" - sorta just > fits I'd say. >
