Andy-- I know I volunteered for this, so I'm happy to do it starting with a vote call tomorrow morning. I haven't been very on top of things (traveling most of last week and preparing for new $job) but I'm back now and can pick it up.

---
A. Soroka

Andy Seaborne wrote on 5/1/17 6:51 AM:
All the PR's are done.

I should be able to find some time to execute the release process this week.

    Andy

On 26/04/17 15:48, Osma Suominen wrote:
Hi Andy!

+0 to PR#245. I feel a little sad for having to leave the ES support out
of the official Fuseki build, but I understand the concerns here. I wish
there was more time (by Anuj perhaps?) to work on solutions that reduced
the size of the ES dependencies, but I don't have that myself, getting
out the release is far more important anyway, and being cautious with
new features is a good strategy.

Yes - what's more, I don't understand quite why everything is getting in 
because some things don't show up in the compile dependencies of jena-text-es.  
So
there are possibilities for next time.

+1 to everything else.

-Osma


25.04.2017, 16:52, Andy Seaborne kirjoitti:
How does this sound as the route to 3.3.0?


Merge these PRs (which I think are all ready to go):

PR#245 :: Maven module for ElasticSearch, not in Fuseki2 in 3.3.0

PR#243 :: JENA-1324: Check for spaces in URIs (if RDF 1.1)

PR#242 :: JENA-1323: RDFWriter

PR#244 :: Open iterators when cancelling a query during sorting

and close PR#240, an alternative to PR#241 which is in the code now.


Please +1, or comment otherwise, and if it seems like a plan, I'll go
ahead and do these items.

    Andy

PR#245 - stops the Fuseki server going from 25M to 70M. We can decide
later if we want ES in Fuseki - it's easier to add later, then ship now
then remove.

There are other ways to not end up with the ES dependencies such as
exclusions.  I prefer a module structure to using exclusions to pick and
choose what goes into Fuseki.








Reply via email to