Hi all, In my opinion, TINKERPOP-3056 (https://issues.apache.org/jira/browse/TINKERPOP-3056) is a significant issue and should be considered a blocker for this release. I believe the current behaviour of mid-traversal mergeE() quite unexpected and can lead to unintended corruption of data. It does not look like it will be solved prior to the proposed end of March code freeze. I would suggest that we delay the release by a few weeks to ensure a resolution can be included in the release. Additionally there are currently competing PR’s aiming to resolve the TINKERPOP-3063/TINKERPOP-3061 authentication issues, I believe the extra time would help everyone settle on a single solution and include it in the release.
Thanks, Cole From: Ken Hu <kenhu...@gmail.com> Date: Wednesday, March 6, 2024 at 10:20 AM To: dev@tinkerpop.apache.org <dev@tinkerpop.apache.org> Subject: Re: [DISCUSS] Next set of maintenance releases - 3.6.7/3.7.2 Hi Yang, This sounds good to me. It matches our recent release cadence so I'm guessing that it's what users will expect as well. Regards, Ken On Tue, Mar 5, 2024 at 6:08 PM Yang Xia <ya...@bitquilltech.com.invalid> wrote: > Hi all, > > It has been a few months since our last release, and we've seen a fair > amount of bug fixes landing during this period[1], as well as new > contributions in review [2]. > > As we head into March, I think it's a good time to start thinking > about releasing these changes with the next set of maintenance releases for > TinkerPop 3.6.7 and 3.7.2. > > I'd like to suggest for us to target code freeze at the end of March, i.e. > the week of March 25, with a release in early April. > > Any thoughts on this? > > Cheers, > > Yang > > [1] > > https://github.com/apache/tinkerpop/blob/3.6-dev/CHANGELOG.asciidoc#tinkerpop-367-not-officially-released-yet > [2] https://github.com/apache/tinkerpop/pull/2506 > Warning: The sender of this message could not be validated and may not be the actual sender.
