On 01/08/12 17:45, Rob Vesse wrote:
Ok, I will get back to you on when would be a good time for me to attempt
a release
Ack
It will most likely be Friday at the earliest if not next week, the
instructions look fairly followable. There are a couple of bits that look
a little iffy so if you are able to be online for some of the time to
answer questions that'd be great.
On the point of running RAT on the codebase what version of RAT are you
using and what command exactly are you running to do that? (I've played
with RAT previously and it seems to have a lot of options and be very slow)
Are there? I haven't bothered and I just run
java --jar ratjar . > ../R
a few seconds.
and look in R (which must be outside the tree :-)
No jars have changed IIRC so all that needs checking is java files, and
a quick whiz over tests to make manifests have not lost their license.
Small test files are not licensed directly (losst are copies of W3C ones
anyway). There should be N&L in the testing area.
Andy
Rob
On 8/1/12 9:15 AM, "Stephen Allen" <[email protected]> wrote:
+1 on release.
On Wed, Aug 1, 2012 at 5:46 AM, Andy Seaborne <[email protected]> wrote:
Do we want to release after removing (or merely switching off) the
NodeCache? TripleCache?
As the system seems slightly faster without, I'm minded to switch them
off.
The Node cache might give a space advantage. But there is another cache
(which does make a difference) in RIOT for IRI resolution, and so the
string
for the IRI is shared for the same IRI input when using RIOT.
Integrating RIOT properly into jena-core is ready-to-go but I'm not
comfortable doing that juts before a release.
Yep I agree with that, presumably we probably want to do a slightly bigger
version bump for that I.e. move to Jena 2.8.0 since that's a fairly
substantial change
Without presuming the decision on the Node cache for this release, I've
made
minimal changes (Node, Triple) to run without caches. My expectation is
that no-one will, or even can, notice the difference from outside. The
Node
cache can be turned on explicitly.
I'd say totally remove both the Node and Triple caches. Just
switching off the cache in Node still leaves the create() method
synchronized, and unnecessary checks into the empty cache on node
creation.
-Stephen
