Re: AW: [DISCUSS] Next release, code freeze etc.
Hello everyone, now that the 3.5.4 and 3.6.1 release are out we are no longer in code freeze. The release branches are now back in SNAPSHOT mode. Development can recommence on the 3.5-dev and 3.6-dev lines Cheers,Kelvin. On Monday, July 4, 2022 at 03:29:33 AM CDT, Florian Hockmann wrote: Thanks for starting the discussion on this, Kelvin! Our last releases were also 3 months ago which is roughly the release cadence that we aim for and yes, getting an official release of the Go client out alone is already a good reason for a release. If nobody sees any import issues that are still open, then we can start code freeze quite soon from my side. -Ursprüngliche Nachricht- Von: Kelvin Lawrence Gesendet: Freitag, 1. Juli 2022 21:29 An: dev@tinkerpop.apache.org Betreff: [DISCUSS] Next release, code freeze etc. We have some useful (and sizable) contributions now merged into the dev branches for 3.5.x and 3.6.x. These include the "ready for GA" version of the Gremlin Go client, and the work to add Graph Binary support to the Node/Javascript client. It feels like it would be good to cut a release soon to get these two items, as well as other features and fixes out in an official version. I have had a few folks tell me they would like to use the Go client, but that they would like to see it be part of an official release. What do people think? Cheers,Kelvin
RE: [DISCUSS] Next release, code freeze etc.
Thanks Lyndon – may take you up on that, but hopefully everything will just work 😊 Cheers, Kelvin Kelvin R. Lawrence From: Lyndon Bauto Sent: Monday, July 18, 2022 6:48 PM To: dev@tinkerpop.apache.org Subject: Re: [DISCUSS] Next release, code freeze etc. I can make some time to help with the official gremlin-go release if you need any assistance, I think it should be straightforward, but I am happy to help. On Mon, Jul 18, 2022 at 3:43 PM Kelvin Lawrence wrote: > Hi everyone, still learning the ropes a little in terms of how things work > with getting releases done. Having suggested we should cut a release soon, > I'm also happy to help get it done. I realize I should have already, but > did not, send a code freeze email last week. It seems like everyone was > operating like we are frozen though, so I will proceed with release this > week unless anyone objects . I've asked Stephen to help me prepare the > artifacts as I haven't done this before and will need help! > Hopefully we can have a vote thread soon for 3.5.4. > Cheers,Kelvin > > > On Monday, July 4, 2022 at 06:55:05 AM CDT, Roi Martin < > jroi.mar...@gmail.com> wrote: > > On Mon, Jul 04, 2022 at 10:29:29AM +0200, Florian Hockmann wrote: > > Thanks for starting the discussion on this, Kelvin! Our last releases > were also 3 months ago which is roughly the release cadence that we aim for > and yes, getting an official release of the Go client out alone is already > a good reason for a release. > > If nobody sees any import issues that are still open, then we can start > code freeze quite soon from my side. > > Hi, > > I'm a newcomer to this project to have much weight in my opinion. However, > regarding gremlin-go, I think it could be important to close the following > issues first: > > Race condition issues: > - gremlin-go: fix deadlock on (*DriverRemoteConnection).Close > https://github.com/apache/tinkerpop/pull/1734 > - gremlin-go: fix data race on serializers and deserializers initialization > https://github.com/apache/tinkerpop/pull/1744 > - gremlin-go: fix data race on localizer initialization > https://github.com/apache/tinkerpop/pull/1745 > > Usability issues: > - Cast Times serialization to int in Gremlin-Go > https://github.com/apache/tinkerpop/pull/1743 > > Also, regarding gremlin-server, I faced the following issues while using > gremlin-go: > > - gremlin-server does not reply with a timeout response to all timed out > requests > https://issues.apache.org/jira/browse/TINKERPOP-2769 > - Race condition during script creation when using UnifiedChannelizer > https://issues.apache.org/jira/browse/TINKERPOP-2765 > > You might want to give them a look to see if they could be a blocker. > > Thanks! > > Best regards, > Roi > -- *Lyndon Bauto* *Senior Software Engineer* *Aerospike, Inc.* www.aerospike.com lba...@aerospike.com
Re: [DISCUSS] Next release, code freeze etc.
I can make some time to help with the official gremlin-go release if you need any assistance, I think it should be straightforward, but I am happy to help. On Mon, Jul 18, 2022 at 3:43 PM Kelvin Lawrence wrote: > Hi everyone, still learning the ropes a little in terms of how things work > with getting releases done. Having suggested we should cut a release soon, > I'm also happy to help get it done. I realize I should have already, but > did not, send a code freeze email last week. It seems like everyone was > operating like we are frozen though, so I will proceed with release this > week unless anyone objects . I've asked Stephen to help me prepare the > artifacts as I haven't done this before and will need help! > Hopefully we can have a vote thread soon for 3.5.4. > Cheers,Kelvin > > > On Monday, July 4, 2022 at 06:55:05 AM CDT, Roi Martin < > jroi.mar...@gmail.com> wrote: > > On Mon, Jul 04, 2022 at 10:29:29AM +0200, Florian Hockmann wrote: > > Thanks for starting the discussion on this, Kelvin! Our last releases > were also 3 months ago which is roughly the release cadence that we aim for > and yes, getting an official release of the Go client out alone is already > a good reason for a release. > > If nobody sees any import issues that are still open, then we can start > code freeze quite soon from my side. > > Hi, > > I'm a newcomer to this project to have much weight in my opinion. However, > regarding gremlin-go, I think it could be important to close the following > issues first: > > Race condition issues: > - gremlin-go: fix deadlock on (*DriverRemoteConnection).Close > https://github.com/apache/tinkerpop/pull/1734 > - gremlin-go: fix data race on serializers and deserializers initialization > https://github.com/apache/tinkerpop/pull/1744 > - gremlin-go: fix data race on localizer initialization > https://github.com/apache/tinkerpop/pull/1745 > > Usability issues: > - Cast Times serialization to int in Gremlin-Go > https://github.com/apache/tinkerpop/pull/1743 > > Also, regarding gremlin-server, I faced the following issues while using > gremlin-go: > > - gremlin-server does not reply with a timeout response to all timed out > requests > https://issues.apache.org/jira/browse/TINKERPOP-2769 > - Race condition during script creation when using UnifiedChannelizer > https://issues.apache.org/jira/browse/TINKERPOP-2765 > > You might want to give them a look to see if they could be a blocker. > > Thanks! > > Best regards, > Roi > -- *Lyndon Bauto* *Senior Software Engineer* *Aerospike, Inc.* www.aerospike.com lba...@aerospike.com
Re: [DISCUSS] Next release, code freeze etc.
Hi everyone, still learning the ropes a little in terms of how things work with getting releases done. Having suggested we should cut a release soon, I'm also happy to help get it done. I realize I should have already, but did not, send a code freeze email last week. It seems like everyone was operating like we are frozen though, so I will proceed with release this week unless anyone objects . I've asked Stephen to help me prepare the artifacts as I haven't done this before and will need help! Hopefully we can have a vote thread soon for 3.5.4. Cheers,Kelvin On Monday, July 4, 2022 at 06:55:05 AM CDT, Roi Martin wrote: On Mon, Jul 04, 2022 at 10:29:29AM +0200, Florian Hockmann wrote: > Thanks for starting the discussion on this, Kelvin! Our last releases were > also 3 months ago which is roughly the release cadence that we aim for and > yes, getting an official release of the Go client out alone is already a good > reason for a release. > If nobody sees any import issues that are still open, then we can start code > freeze quite soon from my side. Hi, I'm a newcomer to this project to have much weight in my opinion. However, regarding gremlin-go, I think it could be important to close the following issues first: Race condition issues: - gremlin-go: fix deadlock on (*DriverRemoteConnection).Close https://github.com/apache/tinkerpop/pull/1734 - gremlin-go: fix data race on serializers and deserializers initialization https://github.com/apache/tinkerpop/pull/1744 - gremlin-go: fix data race on localizer initialization https://github.com/apache/tinkerpop/pull/1745 Usability issues: - Cast Times serialization to int in Gremlin-Go https://github.com/apache/tinkerpop/pull/1743 Also, regarding gremlin-server, I faced the following issues while using gremlin-go: - gremlin-server does not reply with a timeout response to all timed out requests https://issues.apache.org/jira/browse/TINKERPOP-2769 - Race condition during script creation when using UnifiedChannelizer https://issues.apache.org/jira/browse/TINKERPOP-2765 You might want to give them a look to see if they could be a blocker. Thanks! Best regards, Roi
Re: [DISCUSS] Next release, code freeze etc.
On Mon, Jul 04, 2022 at 10:29:29AM +0200, Florian Hockmann wrote: > Thanks for starting the discussion on this, Kelvin! Our last releases were > also 3 months ago which is roughly the release cadence that we aim for and > yes, getting an official release of the Go client out alone is already a good > reason for a release. > If nobody sees any import issues that are still open, then we can start code > freeze quite soon from my side. Hi, I'm a newcomer to this project to have much weight in my opinion. However, regarding gremlin-go, I think it could be important to close the following issues first: Race condition issues: - gremlin-go: fix deadlock on (*DriverRemoteConnection).Close https://github.com/apache/tinkerpop/pull/1734 - gremlin-go: fix data race on serializers and deserializers initialization https://github.com/apache/tinkerpop/pull/1744 - gremlin-go: fix data race on localizer initialization https://github.com/apache/tinkerpop/pull/1745 Usability issues: - Cast Times serialization to int in Gremlin-Go https://github.com/apache/tinkerpop/pull/1743 Also, regarding gremlin-server, I faced the following issues while using gremlin-go: - gremlin-server does not reply with a timeout response to all timed out requests https://issues.apache.org/jira/browse/TINKERPOP-2769 - Race condition during script creation when using UnifiedChannelizer https://issues.apache.org/jira/browse/TINKERPOP-2765 You might want to give them a look to see if they could be a blocker. Thanks! Best regards, Roi
AW: [DISCUSS] Next release, code freeze etc.
Thanks for starting the discussion on this, Kelvin! Our last releases were also 3 months ago which is roughly the release cadence that we aim for and yes, getting an official release of the Go client out alone is already a good reason for a release. If nobody sees any import issues that are still open, then we can start code freeze quite soon from my side. -Ursprüngliche Nachricht- Von: Kelvin Lawrence Gesendet: Freitag, 1. Juli 2022 21:29 An: dev@tinkerpop.apache.org Betreff: [DISCUSS] Next release, code freeze etc. We have some useful (and sizable) contributions now merged into the dev branches for 3.5.x and 3.6.x. These include the "ready for GA" version of the Gremlin Go client, and the work to add Graph Binary support to the Node/Javascript client. It feels like it would be good to cut a release soon to get these two items, as well as other features and fixes out in an official version. I have had a few folks tell me they would like to use the Go client, but that they would like to see it be part of an official release. What do people think? Cheers,Kelvin
[DISCUSS] Next release, code freeze etc.
We have some useful (and sizable) contributions now merged into the dev branches for 3.5.x and 3.6.x. These include the "ready for GA" version of the Gremlin Go client, and the work to add Graph Binary support to the Node/Javascript client. It feels like it would be good to cut a release soon to get these two items, as well as other features and fixes out in an official version. I have had a few folks tell me they would like to use the Go client, but that they would like to see it be part of an official release. What do people think? Cheers,Kelvin
