Hi all, The code freeze is now lifted with TinkerPop 3.5.6 and 3.6.3 released.
The release branches are now back in SNAPSHOT mode and development can recommence on the 3.5-dev and 3.6-dev lines. Cheers, Yang On Fri, Apr 21, 2023 at 4:23 PM Yang Xia <ya...@bitquilltech.com> wrote: > Hi all, > > Given there have been no objections for the release dates, I'd like to go > ahead and call the code-freeze today. > > We will be focusing on merging the existing PRs in the code-freeze week: > Deploying multi-arch docker images: > https://github.com/apache/tinkerpop/pull/2007 > Incorrect result caused by has(key, predicate): > https://github.com/apache/tinkerpop/pull/2017 > Fixing a couple mergeV/E issues: > https://github.com/apache/tinkerpop/pull/2036 > > Please let us know if there are other PRs you'd like to be merged. Note > that we would not be considering large feature additions. > > Cheers, > > Yang > > On Fri, Apr 14, 2023 at 2:19 PM Yang Xia <ya...@bitquilltech.com> wrote: > >> Hi all, >> >> I just want to pitch the idea of considering the next maintenance release >> for 3.5.6 and 3.6.3 soon. >> >> We have had a number of changes built up into the two branches since the >> last release in January [1] [2], plus quite a few PRs for different JIRA >> tickets currently in review, which look ready for merging next week. >> >> These changes include some major performance improvements with Groovy and >> the path() traversers, along with upgrades for security vulnerability and >> bug fixes in gremlin-core. There were updates and fixes in the GLVs that >> led to two release candidates for python and .net. We are also looking to >> have an ARM-based Gremlin Server image available for users. So I think we >> should get a release planned sooner rather than later. >> >> In terms of dates, I'd like to propose we begin code-freeze next Friday, >> Apr 21, and aim for the release announcement for Apr 28. >> >> Also to not leave out 3.7.0, while we recently had a large feature >> implemented, Properties on Element, there are still quite a bit of features >> left in the planned section [3], one being Dave's recent proposal on string >> functions. At this point we probably should keep supporting 3.5.x, as most >> if not all providers still have 3.5.x support. I'm thinking we could >> reassess the dates for 3.7.0 as part of the release after this proposed one. >> >> Any thoughts on this? >> >> Cheers, >> >> Yang >> >> [1] https://github.com/apache/tinkerpop/blob/3.5-dev/CHANGELOG.asciidoc >> [2] https://github.com/apache/tinkerpop/blob/3.6-dev/CHANGELOG.asciidoc >> [3] >> https://github.com/apache/tinkerpop/blob/master/docs/src/dev/future/index.asciidoc#37x---target-22q4 >> >> *--* >> *Yang Xia* >> >>
