Re: [DISCUSS] Consider patch release 3.2.9/3.3.3

2018-04-27 Thread Stephen Mallette
Thanks for taking 3.2.9 Robert. 3.3.3 is still up for grabs if anyone else wants to take that one. We still need to merge these three PRs: https://github.com/apache/tinkerpop/pull/854 - needs a VOTE still before merge https://github.com/apache/tinkerpop/pull/858 and https://github.com/apache/

Re: [DISCUSS] Consider patch release 3.2.9/3.3.3

2018-04-26 Thread Robert Dale
I'll take 3.2.9 Robert Dale On Thu, Apr 26, 2018 at 7:35 AM, Stephen Mallette wrote: > Seems like we're all on board with getting a quick turnaround release out > the door. At this point the groovy fix is now in place and Jorge has both > TINKERPOP-1943/1944 prepared. Unless there are other maj

Re: [DISCUSS] Consider patch release 3.2.9/3.3.3

2018-04-26 Thread Stephen Mallette
Seems like we're all on board with getting a quick turnaround release out the door. At this point the groovy fix is now in place and Jorge has both TINKERPOP-1943/1944 prepared. Unless there are other major issues anyone wants to bring up, we should consider a code freeze starting this friday and p

Re: [DISCUSS] Consider patch release 3.2.9/3.3.3

2018-04-23 Thread Jorge Bay Gondra
sgtm, I'm also +1 on releasing patch releases asap to fix it. Regarding gremlin-javascript, we could include TINKERPOP-1944 (I just submitted a pull request) but I'm not sure we can include TINKERPOP-1943, the implementation is trivial but it will require some changes to make the test suite pass w

Re: [DISCUSS] Consider patch release 3.2.9/3.3.3

2018-04-23 Thread Robert Dale
+1 Robert Dale On Mon, Apr 23, 2018 at 8:44 AM, Stephen Mallette wrote: > Based on: > > https://lists.apache.org/thread.html/de4ec9054fd7a88cbd42163a0b1050 > 19aae52a7e930b09a9bd4c971d@%3Cdev.tinkerpop.apache.org%3E > > We have a pretty serious bug that I can't seem to find a workaround for. >

[DISCUSS] Consider patch release 3.2.9/3.3.3

2018-04-23 Thread Stephen Mallette
Based on: https://lists.apache.org/thread.html/de4ec9054fd7a88cbd42163a0b105019aae52a7e930b09a9bd4c971d@%3Cdev.tinkerpop.apache.org%3E We have a pretty serious bug that I can't seem to find a workaround for. The only workaround I can think of would be to replace this: Lambda.function("it.get()")