You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by Yang Xia <ya...@bitquilltech.com.INVALID> on 2024/03/06 02:08:00 UTC
[DISCUSS] Next set of maintenance releases - 3.6.7/3.7.2
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
Re: [DISCUSS] Next set of maintenance releases - 3.6.7/3.7.2
Posted by Yang Xia <ya...@bitquilltech.com.INVALID>.
Hello all,
The code freeze is now lifted with TinkerPop 3.6.7 and 3.7.2 released.
The release branches are now back in SNAPSHOT mode and development can
recommence on the 3.6-dev and 3.7-dev lines.
We will also be hosting another Contributorcast live stream on this release
next week (stay tuned for the date and time). If you have contributed to
the 3.6.7/3.7.2 release and would like to join us on the stream to chat
about your contributions, feel free to reply in this thread, we'll get in
contact with you!
Cheers,
Yang
On Wed, Mar 20, 2024 at 1:21 PM Cole Greer <Co...@improving.com.invalid>
wrote:
> 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 <ke...@gmail.com>
> Date: Wednesday, March 6, 2024 at 10:20 AM
> To: dev@tinkerpop.apache.org <de...@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.
>
Re: [DISCUSS] Next set of maintenance releases - 3.6.7/3.7.2
Posted by Cole Greer <Co...@improving.com.INVALID>.
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 <ke...@gmail.com>
Date: Wednesday, March 6, 2024 at 10:20 AM
To: dev@tinkerpop.apache.org <de...@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.
Re: [DISCUSS] Next set of maintenance releases - 3.6.7/3.7.2
Posted by Ken Hu <ke...@gmail.com>.
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
>