Current status

29 views
Skip to first unread message

Ray Miller

unread,
Aug 21, 2014, 8:15:15 AM8/21/14
to clojure-...@googlegroups.com
* Archimedes (humbled-transactions branch)

All tests passing now that I've dropped openjdk6 support.

* Titanium (archimedes-api-change branch)

All tests passing locally, needs a deployment of Ogre 2.5.0.0-SNAPSHOT
to build on Travis.

* Ogre

Tests failing on master and blueprints-2.5.0 branches.

There are breaking API changes in Archimedes and Titanium, which now
require the graph to be passed as an argument to functions rather than
relying on a dynamic var. There is also a breaking API change in
Titanium with removal of clojurewerkz.titanium.types in favour of
clojurewerkz.titanium.schema as I mentioned yesterday. There's another
breaking change in clojurewerkz.titanium.graph/open (caused by a
change in Titan). With 0.4.4, you could pass a bare directory path as
a string, but now it has to be prefixed with the storage backend:

(graph/open "berkeleyje:/some/directory/path")

I've switched all but clojurewerkz.titanium.integration-test to use a
temporary BerkeleyDB-backed graph database fixture, the integration
test still uses Cassandra.

The main thing to do before release is to address the failing tests in
Ogre. Once that's done, we'll have something at least as functional as
the previous release. But the next release should probably still be
flagged as 'alpha' until we've had more time to eat our own dogfood
and smooth out any API oddities. And there is always room for more
unit tests.

Ray.

Michael Klishin

unread,
Aug 21, 2014, 9:49:58 AM8/21/14
to clojure-...@googlegroups.com, Ray Miller
 On 21 August 2014 at 16:15:15, Ray Miller (r...@1729.org.uk) wrote:
> > The main thing to do before release is to address the failing
> tests in
> Ogre. Once that's done, we'll have something at least as functional
> as
> the previous release. But the next release should probably still
> be
> flagged as 'alpha' until we've had more time to eat our own dogfood
> and smooth out any API oddities. And there is always room for more
> unit tests.

Thanks for the update.

Given that we move 2 Titan versions up, it makes sense to not worry too
much about breaking API changes in Ogre (and other projects). The Tinkerpop
ecosystem is still relatively young and this kind of changes are unavoidable
for us.

Also, I think it should be "beta" because it's not extremely raw: Titanium,
etc all had a few API iterations before and we know it's fairly reasonable.
-- 
@michaelklishin, github.com/michaelklishin
Reply all
Reply to author
Forward
0 new messages