Hi everyone, I'd like to announce that code freeze is now lifted in 3.7-dev and 3.8-dev. Both branches have been updated to the latest snapshots, artifacts have been pushed to maven, and the documentation has been published.
Thanks, Cole On 2025/11/13 05:02:23 Cole Greer wrote: > Hi everyone, > > While preparing the release votes, I’ve run into some issues with my > code signing keys which is blocking the release validation. Everything > should be resolved now, but I need to wait for ASF committer keys > directory to update. My apologies for this delay. I will continue with > the vote threads tomorrow, once the keys are refreshed and the > validation can proceed. > > Thanks, > Cole > > From: Cole Greer <[email protected]> > Date: Tuesday, November 4, 2025 at 5:35 PM > To: [email protected] <[email protected]> > Subject: Re: [DISCUSS] 3.8.0/3.7.5 Release > > Hi everyone, > > I’d like to extend code freeze by an additional week if possible (release vote > would post on Nov. 12). This has been one of the more active code freezes > I’ve seen in my time with TinkerPop with folks from several projects getting > involved in reviewing the snapshots. I greatly appreciate everyone who has > been testing out the changes, providing feedback in Discord, and opening > PRs with fixes and improvements. I’ve also had a few folks reach out > privately and ask for a bit more time to review all the changes. > > Given all this activity, I think we would benefit from an extra week for > things to > settle down and ensure that everyone’s feedback can be properly addressed. > > Please feel free to reach out if you have any questions or concerns. > > Thanks, > Cole > > > From: Cole Greer <[email protected]> > Date: Friday, October 31, 2025 at 12:28 PM > To: [email protected] <[email protected]> > Subject: Re: [DISCUSS] 3.8.0/3.7.5 Release > > Hi Stephen, > I’m happy to add a few extra days to code freeze. I haven’t had quite as much > time to work through the documentation as I would’ve liked, so I would > appreciate the short extension as well. I’ll pencil in Wednesday Nov. 5 as the > cutoff for building release artifacts and sending out the vote. Feel free to > reach > out again if you’d like more time beyond that. > > Thanks, > Cole > > From: Stephen Mallette <[email protected]> > Date: Friday, October 31, 2025 at 4:08 AM > To: [email protected] <[email protected]> > Subject: Re: [DISCUSS] 3.8.0/3.7.5 Release > > Normally, I think we'd expect to see release artifacts on Monday after a > code freeze. If it's ok with everyone, it would be helpful to get a few > extra days before building release artifacts. Still testing some things and > could use a bit more time to make sure everything looks good. > > On Wed, Oct 29, 2025 at 1:50 PM Yang Xia <[email protected]> wrote: > > > Thank you Cole and Andrea! > > > > On 2025/10/29 17:01:01 Cole Greer wrote: > > > Hi everyone, > > > > > > I’ve recently deployed the latest java snapshots to the snapshot repo: > > https://repository.apache.org/content/groups/snapshots/org/apache/tinkerpop/ > > , > > > and the upgrade docs have also been published: > > https://tinkerpop.apache.org/docs/3.8.0-SNAPSHOT/upgrade/. I will > > continue to > > > redeploy snapshots and documentation throughout code freeze. Please feel > > free to try it out and get in touch with any feedback. > > > > > > Thanks Andrea for volunteering as an observer, I’d be happy to show you > > the release process. I will sync with you off-list to coordinate this. > > > > > > Thanks, > > > Cole > > > > > > From: Andrea Child <[email protected]> > > > Date: Tuesday, October 28, 2025 at 10:08 AM > > > To: [email protected] <[email protected]> > > > Subject: Re: [DISCUSS] 3.8.0/3.7.5 Release > > > Hi Cole, > > > Thanks for volunteering as release manager for 3.8.0. If possible, I > > would like to participate as an observer to this release so that I can help > > for future releases. Please note that I also merged the prevent inject in > > repeat PR last night: https://github.com/apache/tinkerpop/pull/3253 > > > Thanks, > > > Andrea > > > > > > From: Cole Greer <[email protected]> > > > Date: Monday, October 27, 2025 at 7:16 PM > > > To: [email protected] <[email protected]> > > > Subject: Re: [DISCUSS] 3.8.0/3.7.5 Release > > > > > > Hi Yang, > > > > > > Thanks for driving the code freeze here, I’d be happy to volunteer as > > release manager this time around. > > > > > > Regarding your PR list, I would also include Kirill Stepanishin’s PRs > > cleaning up the gremlin examples > > > as well as Kangwei Zhu’s flaky test fix PR. > > > > > > Thanks, > > > Cole > > > > > > From: Yang Xia <[email protected]> > > > Date: Monday, October 27, 2025 at 6:33 PM > > > To: [email protected] <[email protected]> > > > Subject: [DISCUSS] 3.8.0/3.7.5 Release > > > Hi all, > > > > > > As mentioned in the previous thread on releases, I'd like to initiate > > the code freeze on 3.7-dev and 3.8-dev, for the 3.7.5 maintenance release > > and the 3.8.0 major release. > > > > > > We have a lot of exciting new features coming in 3.8.0, so I'd like to > > invite folks to take the opportunity to try out the SNAPSHOT build. > > > > > > Within this code freeze period, we'll not be considering major PRs or > > new features, but will accept small non-breaking fixes and documentation > > updates, including these few PRs: > > > > > > * Prevent inject in repeat: > > https://github.com/apache/tinkerpop/pull/3253 > > > * Remove GenericArgument from from() and to(): > > https://github.com/apache/tinkerpop/pull/3252 > > > * Fix tail inside repeat: https://github.com/apache/tinkerpop/pull/3248 > > > > > > The VOTE threads could be expected starting November 3rd, and the > > releases would be expected within the same or the following week. > > > > > > If there are any objections to this timeline, or if there are any other > > desired changes before the release, please raise in this thread. > > > > > > In addition, if any committers and PMC members would like to be the > > release manager this time, please also reply to this thread. > > > > > > Cheers, > > > > > > Yang > > > Warning: The sender of this message could not be validated and may not > > be the actual sender. > > > > > > Warning: The sender of this message could not be validated and may not be the > actual sender. >
