You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by Cole Greer <Co...@improving.com.INVALID> on 2023/11/11 00:29:40 UTC
[DISCUSS] Start of Code Freeze
Hi everyone,
As we approach the end of the year, I think it’s time that we get started on the next set of minor releases for TinkerPop. This would include 3.5.8, 3.6.6, and 3.7.1.
There are a couple of open PR’s at the moment which appear to be ready to merge in the next few days:
* Bytecode support for HTTP requests: https://github.com/apache/tinkerpop/pull/2336
* TINKERPOP-2988 Add requestId checking to Javascript and Python drivers: https://github.com/apache/tinkerpop/pull/2329
* TINKERPOP-2830 Handle User-Agent from HTTP Requests to server: https://github.com/apache/tinkerpop/pull/2328
* TINKERPOP-2984 Replace Moq with NSubstitute: https://github.com/apache/tinkerpop/pull/2319
Additionally, there are several smaller PR’s regarding configuration and dependency tweaks which I believe can be reviewed and voted on in the next few days as well.
I propose that we initiate code freeze on 3.5-dev, 3.6-dev, and 3.7-dev today, with the intent that the PR’s mentioned above, as well as other small non-breaking fixes can still be merged in the next few days. With this timing, the VOTE threads could be expected starting November 20, and the releases would be expected within the first week of December. If there are any objections to this timeline, or if there are any other desired changes before the release, please reply to this thread.
I would additionally like to propose that we plan this to be the final release in the 3.5.x line, and that we leave 3.5-dev frozen indefinitely. This could of course be reversed in the future if a critical need arises, but unless there are any objections, I believe it’s best that we return to actively working on no more than 3 branches.
Thanks,
Cole Greer
Re: [DISCUSS] Start of Code Freeze
Posted by Willem Ning Jiang <ni...@apache.org>.
It took a while for us to get three binding +1.
Please ping around with the PMC members when we have a release plan; it may speed up the voting process in this way.
Willem
On 2023/11/28 22:52:15 Yang Xia wrote:
> Hi everyone,
>
> Just a quick follow up on the release process. We currently have 2 binding
> votes, and are waiting for a final one for the go ahead. A couple of folks
> who usually vote on the releases are away on vacation, so we are keeping
> the VOTE threads open until people become available to review everything
> and give the final vote.
>
> Cheers,
>
> Yang
>
> On Sat, Nov 11, 2023 at 12:29 PM Ken Hu <ke...@bitquilltech.com.invalid>
> wrote:
>
> > Hi Cole,
> >
> > I'd like to mention that I'm working on a PR for TINKERPOP-3013 that I hope
> > will be landing soon. I'd like that fix to go into the 3.7.1 release.
> >
> > Thanks,
> > Ken
> >
> >
> > On Fri, Nov 10, 2023 at 4:29 PM Cole Greer <Cole.Greer@improving.com
> > .invalid>
> > wrote:
> >
> > > Hi everyone,
> > >
> > > As we approach the end of the year, I think it’s time that we get started
> > > on the next set of minor releases for TinkerPop. This would include
> > 3.5.8,
> > > 3.6.6, and 3.7.1.
> > >
> > > There are a couple of open PR’s at the moment which appear to be ready to
> > > merge in the next few days:
> > >
> > >
> > > * Bytecode support for HTTP requests:
> > > https://github.com/apache/tinkerpop/pull/2336
> > > * TINKERPOP-2988 Add requestId checking to Javascript and Python
> > > drivers: https://github.com/apache/tinkerpop/pull/2329
> > > * TINKERPOP-2830 Handle User-Agent from HTTP Requests to server:
> > > https://github.com/apache/tinkerpop/pull/2328
> > > * TINKERPOP-2984 Replace Moq with NSubstitute:
> > > https://github.com/apache/tinkerpop/pull/2319
> > >
> > > Additionally, there are several smaller PR’s regarding configuration and
> > > dependency tweaks which I believe can be reviewed and voted on in the
> > next
> > > few days as well.
> > >
> > > I propose that we initiate code freeze on 3.5-dev, 3.6-dev, and 3.7-dev
> > > today, with the intent that the PR’s mentioned above, as well as other
> > > small non-breaking fixes can still be merged in the next few days. With
> > > this timing, the VOTE threads could be expected starting November 20, and
> > > the releases would be expected within the first week of December. If
> > there
> > > are any objections to this timeline, or if there are any other desired
> > > changes before the release, please reply to this thread.
> > >
> > > I would additionally like to propose that we plan this to be the final
> > > release in the 3.5.x line, and that we leave 3.5-dev frozen indefinitely.
> > > This could of course be reversed in the future if a critical need arises,
> > > but unless there are any objections, I believe it’s best that we return
> > to
> > > actively working on no more than 3 branches.
> > >
> > > Thanks,
> > >
> > > Cole Greer
> > >
> >
>
Re: [DISCUSS] Start of Code Freeze
Posted by Ken Hu <ke...@bitquilltech.com.INVALID>.
Hi Yang,
I would like to join the Contributorcast to discuss list functions.
Thanks,
Ken
On Tue, Dec 5, 2023 at 12:24 PM Yang Xia <ya...@bitquilltech.com.invalid>
wrote:
> Hello everyone,
>
> The code freeze is now lifted with TinkerPop 3.5.8, 3.6.6, and 3.7.1
> releases.
>
> Both 3.6-dev and 3.7-dev are now back in SNAPSHOT mode and development can
> resume on those branches. Please note that 3.5.8 was the last release of
> the 3.5.x line and the branch will not be opened for development.
>
> We are also looking to host another Contributorcast Twitch stream on these
> new releases next Thursday, 11 am PDT (UTC-7). Again, this will be a casual
> conversation around all the new features and updates that were included. If
> you have contributed to TinkerPop 3.5.8/3.6.6/3.7.2, and you would like to
> join us on the stream to chat about your contribution or anything around
> these releases, feel free to reply and we'll get in contact with you!
>
> Cheers,
>
> Yang
>
>
> On Tue, Nov 28, 2023 at 2:52 PM Yang Xia <ya...@bitquilltech.com> wrote:
>
> > Hi everyone,
> >
> > Just a quick follow up on the release process. We currently have 2
> binding
> > votes, and are waiting for a final one for the go ahead. A couple of
> folks
> > who usually vote on the releases are away on vacation, so we are keeping
> > the VOTE threads open until people become available to review everything
> > and give the final vote.
> >
> > Cheers,
> >
> > Yang
> >
> > On Sat, Nov 11, 2023 at 12:29 PM Ken Hu <ke...@bitquilltech.com.invalid>
> > wrote:
> >
> >> Hi Cole,
> >>
> >> I'd like to mention that I'm working on a PR for TINKERPOP-3013 that I
> >> hope
> >> will be landing soon. I'd like that fix to go into the 3.7.1 release.
> >>
> >> Thanks,
> >> Ken
> >>
> >>
> >> On Fri, Nov 10, 2023 at 4:29 PM Cole Greer <Cole.Greer@improving.com
> >> .invalid>
> >> wrote:
> >>
> >> > Hi everyone,
> >> >
> >> > As we approach the end of the year, I think it’s time that we get
> >> started
> >> > on the next set of minor releases for TinkerPop. This would include
> >> 3.5.8,
> >> > 3.6.6, and 3.7.1.
> >> >
> >> > There are a couple of open PR’s at the moment which appear to be ready
> >> to
> >> > merge in the next few days:
> >> >
> >> >
> >> > * Bytecode support for HTTP requests:
> >> > https://github.com/apache/tinkerpop/pull/2336
> >> > * TINKERPOP-2988 Add requestId checking to Javascript and Python
> >> > drivers: https://github.com/apache/tinkerpop/pull/2329
> >> > * TINKERPOP-2830 Handle User-Agent from HTTP Requests to server:
> >> > https://github.com/apache/tinkerpop/pull/2328
> >> > * TINKERPOP-2984 Replace Moq with NSubstitute:
> >> > https://github.com/apache/tinkerpop/pull/2319
> >> >
> >> > Additionally, there are several smaller PR’s regarding configuration
> and
> >> > dependency tweaks which I believe can be reviewed and voted on in the
> >> next
> >> > few days as well.
> >> >
> >> > I propose that we initiate code freeze on 3.5-dev, 3.6-dev, and
> 3.7-dev
> >> > today, with the intent that the PR’s mentioned above, as well as other
> >> > small non-breaking fixes can still be merged in the next few days.
> With
> >> > this timing, the VOTE threads could be expected starting November 20,
> >> and
> >> > the releases would be expected within the first week of December. If
> >> there
> >> > are any objections to this timeline, or if there are any other desired
> >> > changes before the release, please reply to this thread.
> >> >
> >> > I would additionally like to propose that we plan this to be the final
> >> > release in the 3.5.x line, and that we leave 3.5-dev frozen
> >> indefinitely.
> >> > This could of course be reversed in the future if a critical need
> >> arises,
> >> > but unless there are any objections, I believe it’s best that we
> return
> >> to
> >> > actively working on no more than 3 branches.
> >> >
> >> > Thanks,
> >> >
> >> > Cole Greer
> >> >
> >>
> >
>
Re: [DISCUSS] Start of Code Freeze
Posted by Yang Xia <ya...@bitquilltech.com.INVALID>.
Hello everyone,
The code freeze is now lifted with TinkerPop 3.5.8, 3.6.6, and 3.7.1
releases.
Both 3.6-dev and 3.7-dev are now back in SNAPSHOT mode and development can
resume on those branches. Please note that 3.5.8 was the last release of
the 3.5.x line and the branch will not be opened for development.
We are also looking to host another Contributorcast Twitch stream on these
new releases next Thursday, 11 am PDT (UTC-7). Again, this will be a casual
conversation around all the new features and updates that were included. If
you have contributed to TinkerPop 3.5.8/3.6.6/3.7.2, and you would like to
join us on the stream to chat about your contribution or anything around
these releases, feel free to reply and we'll get in contact with you!
Cheers,
Yang
On Tue, Nov 28, 2023 at 2:52 PM Yang Xia <ya...@bitquilltech.com> wrote:
> Hi everyone,
>
> Just a quick follow up on the release process. We currently have 2 binding
> votes, and are waiting for a final one for the go ahead. A couple of folks
> who usually vote on the releases are away on vacation, so we are keeping
> the VOTE threads open until people become available to review everything
> and give the final vote.
>
> Cheers,
>
> Yang
>
> On Sat, Nov 11, 2023 at 12:29 PM Ken Hu <ke...@bitquilltech.com.invalid>
> wrote:
>
>> Hi Cole,
>>
>> I'd like to mention that I'm working on a PR for TINKERPOP-3013 that I
>> hope
>> will be landing soon. I'd like that fix to go into the 3.7.1 release.
>>
>> Thanks,
>> Ken
>>
>>
>> On Fri, Nov 10, 2023 at 4:29 PM Cole Greer <Cole.Greer@improving.com
>> .invalid>
>> wrote:
>>
>> > Hi everyone,
>> >
>> > As we approach the end of the year, I think it’s time that we get
>> started
>> > on the next set of minor releases for TinkerPop. This would include
>> 3.5.8,
>> > 3.6.6, and 3.7.1.
>> >
>> > There are a couple of open PR’s at the moment which appear to be ready
>> to
>> > merge in the next few days:
>> >
>> >
>> > * Bytecode support for HTTP requests:
>> > https://github.com/apache/tinkerpop/pull/2336
>> > * TINKERPOP-2988 Add requestId checking to Javascript and Python
>> > drivers: https://github.com/apache/tinkerpop/pull/2329
>> > * TINKERPOP-2830 Handle User-Agent from HTTP Requests to server:
>> > https://github.com/apache/tinkerpop/pull/2328
>> > * TINKERPOP-2984 Replace Moq with NSubstitute:
>> > https://github.com/apache/tinkerpop/pull/2319
>> >
>> > Additionally, there are several smaller PR’s regarding configuration and
>> > dependency tweaks which I believe can be reviewed and voted on in the
>> next
>> > few days as well.
>> >
>> > I propose that we initiate code freeze on 3.5-dev, 3.6-dev, and 3.7-dev
>> > today, with the intent that the PR’s mentioned above, as well as other
>> > small non-breaking fixes can still be merged in the next few days. With
>> > this timing, the VOTE threads could be expected starting November 20,
>> and
>> > the releases would be expected within the first week of December. If
>> there
>> > are any objections to this timeline, or if there are any other desired
>> > changes before the release, please reply to this thread.
>> >
>> > I would additionally like to propose that we plan this to be the final
>> > release in the 3.5.x line, and that we leave 3.5-dev frozen
>> indefinitely.
>> > This could of course be reversed in the future if a critical need
>> arises,
>> > but unless there are any objections, I believe it’s best that we return
>> to
>> > actively working on no more than 3 branches.
>> >
>> > Thanks,
>> >
>> > Cole Greer
>> >
>>
>
Re: [DISCUSS] Start of Code Freeze
Posted by Yang Xia <ya...@bitquilltech.com.INVALID>.
Hi everyone,
Just a quick follow up on the release process. We currently have 2 binding
votes, and are waiting for a final one for the go ahead. A couple of folks
who usually vote on the releases are away on vacation, so we are keeping
the VOTE threads open until people become available to review everything
and give the final vote.
Cheers,
Yang
On Sat, Nov 11, 2023 at 12:29 PM Ken Hu <ke...@bitquilltech.com.invalid>
wrote:
> Hi Cole,
>
> I'd like to mention that I'm working on a PR for TINKERPOP-3013 that I hope
> will be landing soon. I'd like that fix to go into the 3.7.1 release.
>
> Thanks,
> Ken
>
>
> On Fri, Nov 10, 2023 at 4:29 PM Cole Greer <Cole.Greer@improving.com
> .invalid>
> wrote:
>
> > Hi everyone,
> >
> > As we approach the end of the year, I think it’s time that we get started
> > on the next set of minor releases for TinkerPop. This would include
> 3.5.8,
> > 3.6.6, and 3.7.1.
> >
> > There are a couple of open PR’s at the moment which appear to be ready to
> > merge in the next few days:
> >
> >
> > * Bytecode support for HTTP requests:
> > https://github.com/apache/tinkerpop/pull/2336
> > * TINKERPOP-2988 Add requestId checking to Javascript and Python
> > drivers: https://github.com/apache/tinkerpop/pull/2329
> > * TINKERPOP-2830 Handle User-Agent from HTTP Requests to server:
> > https://github.com/apache/tinkerpop/pull/2328
> > * TINKERPOP-2984 Replace Moq with NSubstitute:
> > https://github.com/apache/tinkerpop/pull/2319
> >
> > Additionally, there are several smaller PR’s regarding configuration and
> > dependency tweaks which I believe can be reviewed and voted on in the
> next
> > few days as well.
> >
> > I propose that we initiate code freeze on 3.5-dev, 3.6-dev, and 3.7-dev
> > today, with the intent that the PR’s mentioned above, as well as other
> > small non-breaking fixes can still be merged in the next few days. With
> > this timing, the VOTE threads could be expected starting November 20, and
> > the releases would be expected within the first week of December. If
> there
> > are any objections to this timeline, or if there are any other desired
> > changes before the release, please reply to this thread.
> >
> > I would additionally like to propose that we plan this to be the final
> > release in the 3.5.x line, and that we leave 3.5-dev frozen indefinitely.
> > This could of course be reversed in the future if a critical need arises,
> > but unless there are any objections, I believe it’s best that we return
> to
> > actively working on no more than 3 branches.
> >
> > Thanks,
> >
> > Cole Greer
> >
>
Re: [DISCUSS] Start of Code Freeze
Posted by Ken Hu <ke...@bitquilltech.com.INVALID>.
Hi Cole,
I'd like to mention that I'm working on a PR for TINKERPOP-3013 that I hope
will be landing soon. I'd like that fix to go into the 3.7.1 release.
Thanks,
Ken
On Fri, Nov 10, 2023 at 4:29 PM Cole Greer <Co...@improving.com.invalid>
wrote:
> Hi everyone,
>
> As we approach the end of the year, I think it’s time that we get started
> on the next set of minor releases for TinkerPop. This would include 3.5.8,
> 3.6.6, and 3.7.1.
>
> There are a couple of open PR’s at the moment which appear to be ready to
> merge in the next few days:
>
>
> * Bytecode support for HTTP requests:
> https://github.com/apache/tinkerpop/pull/2336
> * TINKERPOP-2988 Add requestId checking to Javascript and Python
> drivers: https://github.com/apache/tinkerpop/pull/2329
> * TINKERPOP-2830 Handle User-Agent from HTTP Requests to server:
> https://github.com/apache/tinkerpop/pull/2328
> * TINKERPOP-2984 Replace Moq with NSubstitute:
> https://github.com/apache/tinkerpop/pull/2319
>
> Additionally, there are several smaller PR’s regarding configuration and
> dependency tweaks which I believe can be reviewed and voted on in the next
> few days as well.
>
> I propose that we initiate code freeze on 3.5-dev, 3.6-dev, and 3.7-dev
> today, with the intent that the PR’s mentioned above, as well as other
> small non-breaking fixes can still be merged in the next few days. With
> this timing, the VOTE threads could be expected starting November 20, and
> the releases would be expected within the first week of December. If there
> are any objections to this timeline, or if there are any other desired
> changes before the release, please reply to this thread.
>
> I would additionally like to propose that we plan this to be the final
> release in the 3.5.x line, and that we leave 3.5-dev frozen indefinitely.
> This could of course be reversed in the future if a critical need arises,
> but unless there are any objections, I believe it’s best that we return to
> actively working on no more than 3 branches.
>
> Thanks,
>
> Cole Greer
>