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 plan for a release the week of May 7.
Any volunteers to help with release management duties? On Mon, Apr 23, 2018 at 9:19 AM, Jorge Bay Gondra <jorgebaygon...@gmail.com> wrote: > 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 with GraphSON3 (Map instances vs Objects). > > > 2018-04-23 15:00 GMT+02:00 Robert Dale <robd...@gmail.com>: > > > +1 > > > > Robert Dale > > > > On Mon, Apr 23, 2018 at 8:44 AM, Stephen Mallette <spmalle...@gmail.com> > > 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. > > > The only workaround I can think of would be to replace this: > > > > > > Lambda.function("it.get()") > > > > > > with > > > > > > new OneArgLambda("it.get()", "gremlin-groovy") > > > > > > Not great as existing code using Lambda will break and none of the docs > > > make any reference to direct usage of the various "Lambda" > constructors. > > > So, short of someone suggesting one very quickly, I think we need to > > > release a patch. > > > > > > Any concerns with doing that? Also, assuming we proceed with the patch > as > > > quickly as possible, can anyone think of any critical items that need > to > > be > > > done for 3.2.9/3.3.3? > > > > > > As a side note, this is somewhat good for gremlin-javascript as we > sorta > > > flubbed the documentation a bit and missed some odds/ends.....perhaps > > this > > > allows us to get that patched up as well sooner than expected? > > > > > >
