Hi Matthias, Many of the issues below were completed in April while we were in the M8 hiatus. When we do the 3.0.0.M8-incubating-rc1 tag on Monday, please go over these again and see where Titan is not happy.
Next, instead of giving us Titan tickets, please create and enumerate TinkerPop tickets so we are aware of them and can discuss on TinkerPop JIRA. Also, note that some tickets are blockers and some are not. For instance, (3) below is a "nice to have" but should not hold up releasing M9. Thus, only those issues that you find are blockers for Titan should be considered as a "we are not happy with rcX." Thank you for taking the time on this, Marko. http://markorodriguez.com > 1) Leaving the property(key,value) default up to vendors (#627): > https://github.com/thinkaurelius/titan/issues/1060 > > 2) Groovy test failures due to ID conversion: > https://github.com/thinkaurelius/titan/issues/1044 > > 3) Inability to add custom profiling information: > https://github.com/thinkaurelius/titan/issues/1035 > > 4) Vendor and TP3 strategies don't mix well: > https://github.com/thinkaurelius/titan/issues/1034 > > 5) Errors in Performance test: > https://github.com/thinkaurelius/titan/issues/1007 > > 6) Other groovy related failures: > https://github.com/thinkaurelius/titan/issues/1006 > > 7) TP3 should not use graph related names in its schema (like "edge", > "element", etc) so that graph vendors can have the flexibility to reserve > those for schema management purposes: > https://github.com/thinkaurelius/titan/issues/730 > https://github.com/thinkaurelius/titan/issues/634 > > 8) @BeforeClass semantics isn't fully honored by the Test suite: > https://github.com/thinkaurelius/titan/issues/1061 > > Thank you, > Matthias
