I like this approach. I see that jitpack updated to java8u45, so it should be possible to depend on the git tags through their infrastructure which would avoid the local building that makes it a little painful for community projects like Titan.
On Fri, May 1, 2015 at 9:55 AM Marko Rodriguez <[email protected]> wrote: > Hi, > > Here is the plan for M9 (as recommend by David Nalley). > > We will tag release candidates in the TinkerPop Git repository. These will > look like: > > 3.0.0.M9-incubating-rc1 > 3.0.0.M9-incubating-rc2 > etc. > > These are NOT in Apache Central. You will have to pull these tags, build, > and test your products against them. Once all the vendors are happy with > rcX, we will go through the [VOTE] process to release 3.0.0.M9-incubating. > > I think this will be easier than people working of master/ SNAPSHOT as > that is a shifty place and it will be good to know from you all: > > "Vendor XXX is happy with rc3. If the other vendors are as well, > please work to get our M9." > > If everyone is happy with that, I can do an 3.0.0.M9-incubating-rc1 tag on > Monday. > > Good?, > Marko. > > http://markorodriguez.com > > On May 1, 2015, at 4:12 AM, pieter-gmail <[email protected]> wrote: > > > Hi, > > > > During the M8 release process I raised a few bugs, mostly around the > test cases, they were fixed but somehow never made it into the M8 branch. > > Somewhere along the line I misunderstood what was being released as I > was testing against master and not the M8 branch. > > Looking forward to M9. > > > > Cheers > > Pieter > > > > On 01/05/2015 07:54, Matthias Broecheler wrote: > >> Hi guys, > >> > >> it's great that we got an M8 officially released. We have been > developing > >> Titan against it and run into a couple of issues that either lead to > >> passing test cases or require hacks in Titan to make work. > >> As such, we cannot release an updated milestone release of Titan until > >> those issues are fixed in TP3 M9. > >> > >> Specifically, these are the issues. Those tickets reference the TP3 > ticket > >> if available. Some of these issues have already been fixed in SNAPSHOT > and > >> no ticket exists. > >> > >> 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 > >> > > > >
