Looking back at this thread, I think that since there were no objections to doing "pre-releases" of GLVs I think we can postpone the test suite changes. So, i'm fine with that being off the table.
Looking at my list, I'm also surprised that I didn't include: https://issues.apache.org/jira/browse/TINKERPOP-1592 I think that will be important for providing more flexibility to users to shape results returned from traversals. That, of course, is important for GLV remoting so that users can return only data that matters to them. TINKERPOP-1592 funnels into the GraphSON/Gryo 3.0 stuff mentioned previously as we seek to make improvements there in terms of efficiency/performance/usability. Marko will be taking a look at the 1592 ticket. I think there is a good body of nice-to-have tickets (after going through them all in the last couple of weeks to do some housekeeping) so we'll see what we can get in there and what we can't after those more crucial bits are done. I believe that we could start thinking about release of 3.3.0 in the next 4 weeks or so. If there are any other thoughts for what's going on with 3.3.0 please let them be known. On Thu, Jun 1, 2017 at 2:08 PM, Stephen Mallette <[email protected]> wrote: > I was just thinking about what needs to be done for 3.3.0 to get it ready > for release. I thought I'd send this email to collect any ideas: > > + Dynamically load the MetricManager in Gremlin Server (TINKERPOP-1550) > + Clean up IO - both GraphSON 3.0 and Gryo 3.0 > + Remove more deprecated code > + Test framework improvements (GLVs and in the structure/process suites) > > I suppose these could shift and change between now and when we think it's > ready to release. I have no idea how much time it will take to get this all > done, but let's see if anyone else has any other important things for 3.3.0. > > > >
