Requesting M9 RC2 due to TINKERPOP3-661

[Bryn Cooke <br...@gmail.com>]

Hi,
I have been testing the M9-RC1 release against Titan and TINKERPOP3-661 
causes 90% of the TP test suite to fail.

As this issue has been fixed can a new RC be released so that we can 
proceed with testing M9?

This issue will block all vendors that do not use user supplied IDs.

Many thanks,
Bryn

Re: Requesting M9 RC2 due to TINKERPOP3-661

[Marko Rodriguez <ok...@gmail.com>]

Hello Bryn,

Whoa. Crazy find. Yes, without Neo4j in master/, its hard for us to test the transaction test suite and graph systems that don't support user supplied IDs.

Let me tag an rc2 now. Will reply in a few.

Thanks,
Marko.

http://markorodriguez.com

On May 6, 2015, at 9:23 AM, Bryn Cooke <br...@gmail.com> wrote:

> Hi,
> I have been testing the M9-RC1 release against Titan and TINKERPOP3-661 causes 90% of the TP test suite to fail.
> 
> As this issue has been fixed can a new RC be released so that we can proceed with testing M9?
> 
> This issue will block all vendors that do not use user supplied IDs.
> 
> Many thanks,
> Bryn
> 

Re: Requesting M9 RC2 due to TINKERPOP3-661

[Stephen Mallette <sp...@gmail.com>]

Sorry about that Bryn - so hard to test such things without a Graph that
doesn't support ids.  I created this ticket:

https://issues.apache.org/jira/browse/TINKERPOP3-662

to make TinkerGraph work in that mode.  This issue really wouldn't be
necessary if we could get Neo4j back into the mix in some way.

On Wed, May 6, 2015 at 11:23 AM, Bryn Cooke <br...@gmail.com> wrote:

> Hi,
> I have been testing the M9-RC1 release against Titan and TINKERPOP3-661
> causes 90% of the TP test suite to fail.
>
> As this issue has been fixed can a new RC be released so that we can
> proceed with testing M9?
>
> This issue will block all vendors that do not use user supplied IDs.
>
> Many thanks,
> Bryn
>
>