You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2017/04/25 13:52:06 UTC
Jena 3.3.0 roadmap
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.
Re: Jena 3.3.0 roadmap
Posted by oc...@gmail.com.
+1 to the plan, and sorry to have been out of touch for several days. It turns out that Osma and I are at the same workshop but have only had a few minutes to talk!
I think we will want to include some notes for the release about how to configure Fuseki2 to use ES. Or perhaps that should just go in the ES module?
I agree that exclusions are much harder to reason about than keeping a kind of "partial order" in dependency.
ajs6f
Andy Seaborne wrote on 4/25/17 6:52 AM:
> 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.
>
>
>
>
>
>
Re: Jena 3.3.0 roadmap
Posted by Chris Dollin <ch...@epimorphics.com>.
On 25 April 2017 at 14:52, Andy Seaborne <an...@apache.org> wrote:
> How does this sound as the route to 3.3.0?
> Please +1, or comment otherwise, and if it seems like a plan, I'll go
> ahead and do these items.
>
+1 & many thanks, Andy.
Chris
--
"What I don't understand is this ..." Trevor Chaplin, /The Beiderbeck
Affair/
Epimorphics Ltd, http://www.epimorphics.com
Registered address: Court Lodge, 105 High Street, Portishead, Bristol BS20
6PT
Epimorphics Ltd. is a limited company registered in England (number 7016688)
Re: Jena 3.3.0 roadmap
Posted by Claude Warren <cl...@xenei.com>.
+1 Looks like a good plan. Thx to everyone who worked on this release.
Claude
On Wed, Apr 26, 2017 at 3:48 PM, Osma Suominen <os...@helsinki.fi>
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.
>
> +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.
>>
>>
>>
>>
>>
>>
>>
>
> --
> Osma Suominen
> D.Sc. (Tech), Information Systems Specialist
> National Library of Finland
> P.O. Box 26 (Kaikukatu 4)
> 00014 HELSINGIN YLIOPISTO
> Tel. +358 50 3199529
> osma.suominen@helsinki.fi
> http://www.nationallibrary.fi
>
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Jena 3.3.0 roadmap
Posted by aj...@apache.org.
It's not the worst thing ever, and as you say, it's not a frequent bother.
If it (it = the 0.0.1 suggested step) is coming from upstream (meaning the plugin) perhaps we can raise a ticket there for a Maven config parameter to adjust.
It's not going to be a super-priority for them, I wouldn't think, but it might be a real easy thing for them and we might get it as a present in a future
release. Otherwise, looks like people do some interesting tinkering with Groovy scripts (!) to get around it:
http://stackoverflow.com/questions/15479851/maven-release-next-development-version-in-batch-mode#15500663
I'm not going to suggest that.
---
A. Soroka
Andy Seaborne wrote on 5/2/17 3:46 PM:
>
>
> On 02/05/17 20:40, sorokaaj@gmail.com wrote:
>> Oh, glory!
>>
>> You know better than I how annoying it is to keep typing the version. We
>> could lock all the versions to be the same and use the properties, but
>> that has its own problems...
>
> Nope - that doesn't seem to work. I thought it would but it will still ask and then make a mess of the POMs because it writes in the given version, not the
> property.
>
> If all the same version and configure the release-plugin with
> <autoVersionSubmodules>true</autoVersionSubmodules>
> then it seems to work.
>
> What we need is examples of other builds that do this - it's a bit of a faff to play with this as it only happens at release time.
>
> Andy
>
>>
>> ---
>> A. Soroka
>>
>> Andy Seaborne wrote on 5/2/17 3:38 PM:
>>> Yes - 3.4.0-SNAPSHOT
>>>
>>> It does not come from the POM - it's the maven release plugin
>>> suggesting 3.3.1-SNAPSHOT. It suggests a.b.(c+1)
>>>
>>> BTW I think I have found a way to do away with (nearly) all those
>>> questions.
>>>
>>> Andy
>>>
>>> On 02/05/17 15:13, ajs6f@apache.org wrote:
>>>> I am starting the work now.
>>>>
>>>> The release setup is offering to go to 3.3.1-SNAPSHOT, but didn't we
>>>> decide to go directly to 3.4.0? I admit, I've gotten mixed around in the
>>>> discussion and doing this while physically cleaning out twenty years of
>>>> accumulated stuff in my office is not clarifying my memory. :grin:
>>>>
>>>> ---
>>>> A. Soroka
>>>>
>>>> Andy Seaborne wrote on 5/1/17 11:35 AM:
>>>>> On 01/05/17 14:16, sorokaaj@gmail.com wrote:
>>>>>> 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
>>>>>
>>>>> That would be great - if it turns out that life/new-$job gets in the
>>>>> way, then I can do it. (The dry run looked OK.)
>>>>>
>>>>> Andy
>>>>>
>>>>> I have already drafted an email:
>>>>> (look for the @@ for things to complete)
>>>>>
>>>>> ------------------------------------------------
>>>>> Subject: [VOTE] Release vote : Apache Jena 3.3.0
>>>>>
>>>>> Hi,
>>>>>
>>>>> Here is a vote on a release of Jena 3.3.0
>>>>> (with Fuseki 2.6.0)
>>>>>
>>>>> This is the first proposed candidate for this release.
>>>>>
>>>>> == Dependency changes:
>>>>>
>>>>> jena-text: Lucene v6.4.1
>>>>>
>>>>> New module:
>>>>> jena-text-es
>>>>> Elasticsearch: v5.2.2 License : AL2
>>>>> https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt
>>>>> [*] Full list of recursive dependencies at the end
>>>>>
>>>>> == Updates:
>>>>> guava (shaded) to version 21.
>>>>>
>>>>> == Key features of the release:
>>>>>
>>>>> * Drop support for solr4j, add support for Elastic Search
>>>>> JENA-1301 - Drop Solr
>>>>> JENA-1305 - Elastic Search support
>>>>> Contributions from Anuj Kumar
>>>>>
>>>>> * Add VCARD4 (JENA-1205)
>>>>> Contribution from Bart Hanssens
>>>>>
>>>>> * RDFParser (JENA-1306)
>>>>> New low level, detailed setup of parsers for special cases.
>>>>> RDFDataMgr is still the main way to read data (it now uses
>>>>> RDFParser).
>>>>>
>>>>> * RDFWriter (JENA-1323)
>>>>>
>>>>> * Bad URIs in RDF/XML are now warnings (model.read) inline with RDF
>>>>> 1.1.
>>>>> (JENA-1324)
>>>>>
>>>>>
>>>>> ~39 JIRA
>>>>> See https://s.apache.org/jena-3.3.0-jira
>>>>>
>>>>> == Release
>>>>>
>>>>> Everyone, not just committers, is invited to test and vote.
>>>>> Please download and test the proposed release.
>>>>>
>>>>> Staging repository:
>>>>> https://repository.apache.org/content/repositories/orgapachejena-@@/
>>>>>
>>>>> Proposed dist/ area:
>>>>> https://dist.apache.org/repos/dist/dev/jena/
>>>>>
>>>>> Keys:
>>>>> https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>>
>>>>> Git commit (browser URL):
>>>>> https://git-wip-us.apache.org/repos/asf/jena/commit/@@
>>>>>
>>>>> Git Commit Hash:
>>>>> @@
>>>>>
>>>>> Git Commit Tag:
>>>>> jena-3.3.0-rc1
>>>>>
>>>>> Please vote to approve this release:
>>>>>
>>>>> [ ] +1 Approve the release
>>>>> [ ] 0 Don't care
>>>>> [ ] -1 Don't release, because ...
>>>>>
>>>>> This vote will be open to at least
>>>>>
>>>>> @@
>>>>>
>>>>> If you expect to check the release but the 72 hour limit does not work
>>>>> for you, please email within the schedule above with an expected time
>>>>> and we can extend the vote period.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> @@
>>>>>
>>>>> Checking needed:
>>>>>
>>>>> + does everything work on Linux?
>>>>> + does everything work on MS Windows?
>>>>> + does everything work on OS X?
>>>>> + are the GPG signatures fine?
>>>>> + are the checksums correct?
>>>>> + is there a source archive?
>>>>> + can the source archive really be built?
>>>>> + is there a correct LICENSE and NOTICE file in each artifact
>>>>> (both source and binary artifacts)?
>>>>> + does the NOTICE file contain all necessary attributions?
>>>>> + have any licenses of dependencies changed due to upgrades?
>>>>> if so have LICENSE and NOTICE been upgraded appropriately?
>>>>> + does the tag/commit in the SCM contain reproducible sources?
>>>>>
>>>>>
>>>>> --------------------------------------------------
>>>>>
>>>>> [*]
>>>>> org.elasticsearch dependencies (recursive) other than org.apache
>>>>> artifacts:
>>>>>
>>>>> org.elasticsearch:elasticsearch:jar:5.2.2
>>>>> net.sf.jopt-simple:jopt-simple:jar:5.0.2
>>>>> com.carrotsearch:hppc:jar:0.7.1
>>>>> joda-time:joda-time:jar:2.9.5
>>>>> org.yaml:snakeyaml:jar:1.15
>>>>> com.tdunning:t-digest:jar:3.0
>>>>> org.hdrhistogram:HdrHistogram:jar
>>>>> net.java.dev.jna:jna:jar:4.2.2
>>>>> io.netty:netty:jar:3.10.6.Final
>>>>> com.github.spullara.mustache.java:compiler:jar:0.9.3
Re: Jena 3.3.0 roadmap
Posted by Andy Seaborne <an...@apache.org>.
On 02/05/17 20:40, sorokaaj@gmail.com wrote:
> Oh, glory!
>
> You know better than I how annoying it is to keep typing the version. We
> could lock all the versions to be the same and use the properties, but
> that has its own problems...
Nope - that doesn't seem to work. I thought it would but it will still
ask and then make a mess of the POMs because it writes in the given
version, not the property.
If all the same version and configure the release-plugin with
<autoVersionSubmodules>true</autoVersionSubmodules>
then it seems to work.
What we need is examples of other builds that do this - it's a bit of a
faff to play with this as it only happens at release time.
Andy
>
> ---
> A. Soroka
>
> Andy Seaborne wrote on 5/2/17 3:38 PM:
>> Yes - 3.4.0-SNAPSHOT
>>
>> It does not come from the POM - it's the maven release plugin
>> suggesting 3.3.1-SNAPSHOT. It suggests a.b.(c+1)
>>
>> BTW I think I have found a way to do away with (nearly) all those
>> questions.
>>
>> Andy
>>
>> On 02/05/17 15:13, ajs6f@apache.org wrote:
>>> I am starting the work now.
>>>
>>> The release setup is offering to go to 3.3.1-SNAPSHOT, but didn't we
>>> decide to go directly to 3.4.0? I admit, I've gotten mixed around in the
>>> discussion and doing this while physically cleaning out twenty years of
>>> accumulated stuff in my office is not clarifying my memory. :grin:
>>>
>>> ---
>>> A. Soroka
>>>
>>> Andy Seaborne wrote on 5/1/17 11:35 AM:
>>>> On 01/05/17 14:16, sorokaaj@gmail.com wrote:
>>>>> 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
>>>>
>>>> That would be great - if it turns out that life/new-$job gets in the
>>>> way, then I can do it. (The dry run looked OK.)
>>>>
>>>> Andy
>>>>
>>>> I have already drafted an email:
>>>> (look for the @@ for things to complete)
>>>>
>>>> ------------------------------------------------
>>>> Subject: [VOTE] Release vote : Apache Jena 3.3.0
>>>>
>>>> Hi,
>>>>
>>>> Here is a vote on a release of Jena 3.3.0
>>>> (with Fuseki 2.6.0)
>>>>
>>>> This is the first proposed candidate for this release.
>>>>
>>>> == Dependency changes:
>>>>
>>>> jena-text: Lucene v6.4.1
>>>>
>>>> New module:
>>>> jena-text-es
>>>> Elasticsearch: v5.2.2 License : AL2
>>>> https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt
>>>> [*] Full list of recursive dependencies at the end
>>>>
>>>> == Updates:
>>>> guava (shaded) to version 21.
>>>>
>>>> == Key features of the release:
>>>>
>>>> * Drop support for solr4j, add support for Elastic Search
>>>> JENA-1301 - Drop Solr
>>>> JENA-1305 - Elastic Search support
>>>> Contributions from Anuj Kumar
>>>>
>>>> * Add VCARD4 (JENA-1205)
>>>> Contribution from Bart Hanssens
>>>>
>>>> * RDFParser (JENA-1306)
>>>> New low level, detailed setup of parsers for special cases.
>>>> RDFDataMgr is still the main way to read data (it now uses
>>>> RDFParser).
>>>>
>>>> * RDFWriter (JENA-1323)
>>>>
>>>> * Bad URIs in RDF/XML are now warnings (model.read) inline with RDF
>>>> 1.1.
>>>> (JENA-1324)
>>>>
>>>>
>>>> ~39 JIRA
>>>> See https://s.apache.org/jena-3.3.0-jira
>>>>
>>>> == Release
>>>>
>>>> Everyone, not just committers, is invited to test and vote.
>>>> Please download and test the proposed release.
>>>>
>>>> Staging repository:
>>>> https://repository.apache.org/content/repositories/orgapachejena-@@/
>>>>
>>>> Proposed dist/ area:
>>>> https://dist.apache.org/repos/dist/dev/jena/
>>>>
>>>> Keys:
>>>> https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>
>>>> Git commit (browser URL):
>>>> https://git-wip-us.apache.org/repos/asf/jena/commit/@@
>>>>
>>>> Git Commit Hash:
>>>> @@
>>>>
>>>> Git Commit Tag:
>>>> jena-3.3.0-rc1
>>>>
>>>> Please vote to approve this release:
>>>>
>>>> [ ] +1 Approve the release
>>>> [ ] 0 Don't care
>>>> [ ] -1 Don't release, because ...
>>>>
>>>> This vote will be open to at least
>>>>
>>>> @@
>>>>
>>>> If you expect to check the release but the 72 hour limit does not work
>>>> for you, please email within the schedule above with an expected time
>>>> and we can extend the vote period.
>>>>
>>>> Thanks,
>>>>
>>>> @@
>>>>
>>>> Checking needed:
>>>>
>>>> + does everything work on Linux?
>>>> + does everything work on MS Windows?
>>>> + does everything work on OS X?
>>>> + are the GPG signatures fine?
>>>> + are the checksums correct?
>>>> + is there a source archive?
>>>> + can the source archive really be built?
>>>> + is there a correct LICENSE and NOTICE file in each artifact
>>>> (both source and binary artifacts)?
>>>> + does the NOTICE file contain all necessary attributions?
>>>> + have any licenses of dependencies changed due to upgrades?
>>>> if so have LICENSE and NOTICE been upgraded appropriately?
>>>> + does the tag/commit in the SCM contain reproducible sources?
>>>>
>>>>
>>>> --------------------------------------------------
>>>>
>>>> [*]
>>>> org.elasticsearch dependencies (recursive) other than org.apache
>>>> artifacts:
>>>>
>>>> org.elasticsearch:elasticsearch:jar:5.2.2
>>>> net.sf.jopt-simple:jopt-simple:jar:5.0.2
>>>> com.carrotsearch:hppc:jar:0.7.1
>>>> joda-time:joda-time:jar:2.9.5
>>>> org.yaml:snakeyaml:jar:1.15
>>>> com.tdunning:t-digest:jar:3.0
>>>> org.hdrhistogram:HdrHistogram:jar
>>>> net.java.dev.jna:jna:jar:4.2.2
>>>> io.netty:netty:jar:3.10.6.Final
>>>> com.github.spullara.mustache.java:compiler:jar:0.9.3
Re: Jena 3.3.0 roadmap
Posted by so...@gmail.com.
Oh, glory!
You know better than I how annoying it is to keep typing the version. We could lock all the versions to be the same and use the properties, but that has its own
problems...
---
A. Soroka
Andy Seaborne wrote on 5/2/17 3:38 PM:
> Yes - 3.4.0-SNAPSHOT
>
> It does not come from the POM - it's the maven release plugin suggesting 3.3.1-SNAPSHOT. It suggests a.b.(c+1)
>
> BTW I think I have found a way to do away with (nearly) all those questions.
>
> Andy
>
> On 02/05/17 15:13, ajs6f@apache.org wrote:
>> I am starting the work now.
>>
>> The release setup is offering to go to 3.3.1-SNAPSHOT, but didn't we
>> decide to go directly to 3.4.0? I admit, I've gotten mixed around in the
>> discussion and doing this while physically cleaning out twenty years of
>> accumulated stuff in my office is not clarifying my memory. :grin:
>>
>> ---
>> A. Soroka
>>
>> Andy Seaborne wrote on 5/1/17 11:35 AM:
>>> On 01/05/17 14:16, sorokaaj@gmail.com wrote:
>>>> 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
>>>
>>> That would be great - if it turns out that life/new-$job gets in the
>>> way, then I can do it. (The dry run looked OK.)
>>>
>>> Andy
>>>
>>> I have already drafted an email:
>>> (look for the @@ for things to complete)
>>>
>>> ------------------------------------------------
>>> Subject: [VOTE] Release vote : Apache Jena 3.3.0
>>>
>>> Hi,
>>>
>>> Here is a vote on a release of Jena 3.3.0
>>> (with Fuseki 2.6.0)
>>>
>>> This is the first proposed candidate for this release.
>>>
>>> == Dependency changes:
>>>
>>> jena-text: Lucene v6.4.1
>>>
>>> New module:
>>> jena-text-es
>>> Elasticsearch: v5.2.2 License : AL2
>>> https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt
>>> [*] Full list of recursive dependencies at the end
>>>
>>> == Updates:
>>> guava (shaded) to version 21.
>>>
>>> == Key features of the release:
>>>
>>> * Drop support for solr4j, add support for Elastic Search
>>> JENA-1301 - Drop Solr
>>> JENA-1305 - Elastic Search support
>>> Contributions from Anuj Kumar
>>>
>>> * Add VCARD4 (JENA-1205)
>>> Contribution from Bart Hanssens
>>>
>>> * RDFParser (JENA-1306)
>>> New low level, detailed setup of parsers for special cases.
>>> RDFDataMgr is still the main way to read data (it now uses RDFParser).
>>>
>>> * RDFWriter (JENA-1323)
>>>
>>> * Bad URIs in RDF/XML are now warnings (model.read) inline with RDF 1.1.
>>> (JENA-1324)
>>>
>>>
>>> ~39 JIRA
>>> See https://s.apache.org/jena-3.3.0-jira
>>>
>>> == Release
>>>
>>> Everyone, not just committers, is invited to test and vote.
>>> Please download and test the proposed release.
>>>
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapachejena-@@/
>>>
>>> Proposed dist/ area:
>>> https://dist.apache.org/repos/dist/dev/jena/
>>>
>>> Keys:
>>> https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>
>>> Git commit (browser URL):
>>> https://git-wip-us.apache.org/repos/asf/jena/commit/@@
>>>
>>> Git Commit Hash:
>>> @@
>>>
>>> Git Commit Tag:
>>> jena-3.3.0-rc1
>>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] 0 Don't care
>>> [ ] -1 Don't release, because ...
>>>
>>> This vote will be open to at least
>>>
>>> @@
>>>
>>> If you expect to check the release but the 72 hour limit does not work
>>> for you, please email within the schedule above with an expected time
>>> and we can extend the vote period.
>>>
>>> Thanks,
>>>
>>> @@
>>>
>>> Checking needed:
>>>
>>> + does everything work on Linux?
>>> + does everything work on MS Windows?
>>> + does everything work on OS X?
>>> + are the GPG signatures fine?
>>> + are the checksums correct?
>>> + is there a source archive?
>>> + can the source archive really be built?
>>> + is there a correct LICENSE and NOTICE file in each artifact
>>> (both source and binary artifacts)?
>>> + does the NOTICE file contain all necessary attributions?
>>> + have any licenses of dependencies changed due to upgrades?
>>> if so have LICENSE and NOTICE been upgraded appropriately?
>>> + does the tag/commit in the SCM contain reproducible sources?
>>>
>>>
>>> --------------------------------------------------
>>>
>>> [*]
>>> org.elasticsearch dependencies (recursive) other than org.apache
>>> artifacts:
>>>
>>> org.elasticsearch:elasticsearch:jar:5.2.2
>>> net.sf.jopt-simple:jopt-simple:jar:5.0.2
>>> com.carrotsearch:hppc:jar:0.7.1
>>> joda-time:joda-time:jar:2.9.5
>>> org.yaml:snakeyaml:jar:1.15
>>> com.tdunning:t-digest:jar:3.0
>>> org.hdrhistogram:HdrHistogram:jar
>>> net.java.dev.jna:jna:jar:4.2.2
>>> io.netty:netty:jar:3.10.6.Final
>>> com.github.spullara.mustache.java:compiler:jar:0.9.3
Re: Jena 3.3.0 roadmap
Posted by Andy Seaborne <an...@apache.org>.
Yes - 3.4.0-SNAPSHOT
It does not come from the POM - it's the maven release plugin suggesting
3.3.1-SNAPSHOT. It suggests a.b.(c+1)
BTW I think I have found a way to do away with (nearly) all those questions.
Andy
On 02/05/17 15:13, ajs6f@apache.org wrote:
> I am starting the work now.
>
> The release setup is offering to go to 3.3.1-SNAPSHOT, but didn't we
> decide to go directly to 3.4.0? I admit, I've gotten mixed around in the
> discussion and doing this while physically cleaning out twenty years of
> accumulated stuff in my office is not clarifying my memory. :grin:
>
> ---
> A. Soroka
>
> Andy Seaborne wrote on 5/1/17 11:35 AM:
>> On 01/05/17 14:16, sorokaaj@gmail.com wrote:
>>> 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
>>
>> That would be great - if it turns out that life/new-$job gets in the
>> way, then I can do it. (The dry run looked OK.)
>>
>> Andy
>>
>> I have already drafted an email:
>> (look for the @@ for things to complete)
>>
>> ------------------------------------------------
>> Subject: [VOTE] Release vote : Apache Jena 3.3.0
>>
>> Hi,
>>
>> Here is a vote on a release of Jena 3.3.0
>> (with Fuseki 2.6.0)
>>
>> This is the first proposed candidate for this release.
>>
>> == Dependency changes:
>>
>> jena-text: Lucene v6.4.1
>>
>> New module:
>> jena-text-es
>> Elasticsearch: v5.2.2 License : AL2
>> https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt
>> [*] Full list of recursive dependencies at the end
>>
>> == Updates:
>> guava (shaded) to version 21.
>>
>> == Key features of the release:
>>
>> * Drop support for solr4j, add support for Elastic Search
>> JENA-1301 - Drop Solr
>> JENA-1305 - Elastic Search support
>> Contributions from Anuj Kumar
>>
>> * Add VCARD4 (JENA-1205)
>> Contribution from Bart Hanssens
>>
>> * RDFParser (JENA-1306)
>> New low level, detailed setup of parsers for special cases.
>> RDFDataMgr is still the main way to read data (it now uses RDFParser).
>>
>> * RDFWriter (JENA-1323)
>>
>> * Bad URIs in RDF/XML are now warnings (model.read) inline with RDF 1.1.
>> (JENA-1324)
>>
>>
>> ~39 JIRA
>> See https://s.apache.org/jena-3.3.0-jira
>>
>> == Release
>>
>> Everyone, not just committers, is invited to test and vote.
>> Please download and test the proposed release.
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachejena-@@/
>>
>> Proposed dist/ area:
>> https://dist.apache.org/repos/dist/dev/jena/
>>
>> Keys:
>> https://svn.apache.org/repos/asf/jena/dist/KEYS
>>
>> Git commit (browser URL):
>> https://git-wip-us.apache.org/repos/asf/jena/commit/@@
>>
>> Git Commit Hash:
>> @@
>>
>> Git Commit Tag:
>> jena-3.3.0-rc1
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] 0 Don't care
>> [ ] -1 Don't release, because ...
>>
>> This vote will be open to at least
>>
>> @@
>>
>> If you expect to check the release but the 72 hour limit does not work
>> for you, please email within the schedule above with an expected time
>> and we can extend the vote period.
>>
>> Thanks,
>>
>> @@
>>
>> Checking needed:
>>
>> + does everything work on Linux?
>> + does everything work on MS Windows?
>> + does everything work on OS X?
>> + are the GPG signatures fine?
>> + are the checksums correct?
>> + is there a source archive?
>> + can the source archive really be built?
>> + is there a correct LICENSE and NOTICE file in each artifact
>> (both source and binary artifacts)?
>> + does the NOTICE file contain all necessary attributions?
>> + have any licenses of dependencies changed due to upgrades?
>> if so have LICENSE and NOTICE been upgraded appropriately?
>> + does the tag/commit in the SCM contain reproducible sources?
>>
>>
>> --------------------------------------------------
>>
>> [*]
>> org.elasticsearch dependencies (recursive) other than org.apache
>> artifacts:
>>
>> org.elasticsearch:elasticsearch:jar:5.2.2
>> net.sf.jopt-simple:jopt-simple:jar:5.0.2
>> com.carrotsearch:hppc:jar:0.7.1
>> joda-time:joda-time:jar:2.9.5
>> org.yaml:snakeyaml:jar:1.15
>> com.tdunning:t-digest:jar:3.0
>> org.hdrhistogram:HdrHistogram:jar
>> net.java.dev.jna:jna:jar:4.2.2
>> io.netty:netty:jar:3.10.6.Final
>> com.github.spullara.mustache.java:compiler:jar:0.9.3
Re: Jena 3.3.0 roadmap
Posted by aj...@apache.org.
I am starting the work now.
The release setup is offering to go to 3.3.1-SNAPSHOT, but didn't we decide to go directly to 3.4.0? I admit, I've gotten mixed around in the discussion and
doing this while physically cleaning out twenty years of accumulated stuff in my office is not clarifying my memory. :grin:
---
A. Soroka
Andy Seaborne wrote on 5/1/17 11:35 AM:
> On 01/05/17 14:16, sorokaaj@gmail.com wrote:
>> 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
>
> That would be great - if it turns out that life/new-$job gets in the way, then I can do it. (The dry run looked OK.)
>
> Andy
>
> I have already drafted an email:
> (look for the @@ for things to complete)
>
> ------------------------------------------------
> Subject: [VOTE] Release vote : Apache Jena 3.3.0
>
> Hi,
>
> Here is a vote on a release of Jena 3.3.0
> (with Fuseki 2.6.0)
>
> This is the first proposed candidate for this release.
>
> == Dependency changes:
>
> jena-text: Lucene v6.4.1
>
> New module:
> jena-text-es
> Elasticsearch: v5.2.2 License : AL2
> https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt
> [*] Full list of recursive dependencies at the end
>
> == Updates:
> guava (shaded) to version 21.
>
> == Key features of the release:
>
> * Drop support for solr4j, add support for Elastic Search
> JENA-1301 - Drop Solr
> JENA-1305 - Elastic Search support
> Contributions from Anuj Kumar
>
> * Add VCARD4 (JENA-1205)
> Contribution from Bart Hanssens
>
> * RDFParser (JENA-1306)
> New low level, detailed setup of parsers for special cases.
> RDFDataMgr is still the main way to read data (it now uses RDFParser).
>
> * RDFWriter (JENA-1323)
>
> * Bad URIs in RDF/XML are now warnings (model.read) inline with RDF 1.1.
> (JENA-1324)
>
>
> ~39 JIRA
> See https://s.apache.org/jena-3.3.0-jira
>
> == Release
>
> Everyone, not just committers, is invited to test and vote.
> Please download and test the proposed release.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachejena-@@/
>
> Proposed dist/ area:
> https://dist.apache.org/repos/dist/dev/jena/
>
> Keys:
> https://svn.apache.org/repos/asf/jena/dist/KEYS
>
> Git commit (browser URL):
> https://git-wip-us.apache.org/repos/asf/jena/commit/@@
>
> Git Commit Hash:
> @@
>
> Git Commit Tag:
> jena-3.3.0-rc1
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
>
> This vote will be open to at least
>
> @@
>
> If you expect to check the release but the 72 hour limit does not work
> for you, please email within the schedule above with an expected time
> and we can extend the vote period.
>
> Thanks,
>
> @@
>
> Checking needed:
>
> + does everything work on Linux?
> + does everything work on MS Windows?
> + does everything work on OS X?
> + are the GPG signatures fine?
> + are the checksums correct?
> + is there a source archive?
> + can the source archive really be built?
> + is there a correct LICENSE and NOTICE file in each artifact
> (both source and binary artifacts)?
> + does the NOTICE file contain all necessary attributions?
> + have any licenses of dependencies changed due to upgrades?
> if so have LICENSE and NOTICE been upgraded appropriately?
> + does the tag/commit in the SCM contain reproducible sources?
>
>
> --------------------------------------------------
>
> [*]
> org.elasticsearch dependencies (recursive) other than org.apache artifacts:
>
> org.elasticsearch:elasticsearch:jar:5.2.2
> net.sf.jopt-simple:jopt-simple:jar:5.0.2
> com.carrotsearch:hppc:jar:0.7.1
> joda-time:joda-time:jar:2.9.5
> org.yaml:snakeyaml:jar:1.15
> com.tdunning:t-digest:jar:3.0
> org.hdrhistogram:HdrHistogram:jar
> net.java.dev.jna:jna:jar:4.2.2
> io.netty:netty:jar:3.10.6.Final
> com.github.spullara.mustache.java:compiler:jar:0.9.3
Re: Jena 3.3.0 roadmap
Posted by Andy Seaborne <an...@apache.org>.
On 01/05/17 14:16, sorokaaj@gmail.com wrote:
> 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
That would be great - if it turns out that life/new-$job gets in the
way, then I can do it. (The dry run looked OK.)
Andy
I have already drafted an email:
(look for the @@ for things to complete)
------------------------------------------------
Subject: [VOTE] Release vote : Apache Jena 3.3.0
Hi,
Here is a vote on a release of Jena 3.3.0
(with Fuseki 2.6.0)
This is the first proposed candidate for this release.
== Dependency changes:
jena-text: Lucene v6.4.1
New module:
jena-text-es
Elasticsearch: v5.2.2 License : AL2
https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt
[*] Full list of recursive dependencies at the end
== Updates:
guava (shaded) to version 21.
== Key features of the release:
* Drop support for solr4j, add support for Elastic Search
JENA-1301 - Drop Solr
JENA-1305 - Elastic Search support
Contributions from Anuj Kumar
* Add VCARD4 (JENA-1205)
Contribution from Bart Hanssens
* RDFParser (JENA-1306)
New low level, detailed setup of parsers for special cases.
RDFDataMgr is still the main way to read data (it now uses RDFParser).
* RDFWriter (JENA-1323)
* Bad URIs in RDF/XML are now warnings (model.read) inline with RDF 1.1.
(JENA-1324)
~39 JIRA
See https://s.apache.org/jena-3.3.0-jira
== Release
Everyone, not just committers, is invited to test and vote.
Please download and test the proposed release.
Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-@@/
Proposed dist/ area:
https://dist.apache.org/repos/dist/dev/jena/
Keys:
https://svn.apache.org/repos/asf/jena/dist/KEYS
Git commit (browser URL):
https://git-wip-us.apache.org/repos/asf/jena/commit/@@
Git Commit Hash:
@@
Git Commit Tag:
jena-3.3.0-rc1
Please vote to approve this release:
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This vote will be open to at least
@@
If you expect to check the release but the 72 hour limit does not work
for you, please email within the schedule above with an expected time
and we can extend the vote period.
Thanks,
@@
Checking needed:
+ does everything work on Linux?
+ does everything work on MS Windows?
+ does everything work on OS X?
+ are the GPG signatures fine?
+ are the checksums correct?
+ is there a source archive?
+ can the source archive really be built?
+ is there a correct LICENSE and NOTICE file in each artifact
(both source and binary artifacts)?
+ does the NOTICE file contain all necessary attributions?
+ have any licenses of dependencies changed due to upgrades?
if so have LICENSE and NOTICE been upgraded appropriately?
+ does the tag/commit in the SCM contain reproducible sources?
--------------------------------------------------
[*]
org.elasticsearch dependencies (recursive) other than org.apache artifacts:
org.elasticsearch:elasticsearch:jar:5.2.2
net.sf.jopt-simple:jopt-simple:jar:5.0.2
com.carrotsearch:hppc:jar:0.7.1
joda-time:joda-time:jar:2.9.5
org.yaml:snakeyaml:jar:1.15
com.tdunning:t-digest:jar:3.0
org.hdrhistogram:HdrHistogram:jar
net.java.dev.jna:jna:jar:4.2.2
io.netty:netty:jar:3.10.6.Final
com.github.spullara.mustache.java:compiler:jar:0.9.3
Re: Jena 3.3.0 roadmap
Posted by so...@gmail.com.
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.
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
Re: Jena 3.3.0 roadmap
Posted by Andy Seaborne <an...@apache.org>.
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.
>>
>>
>>
>>
>>
>>
>
>
Re: Jena 3.3.0 roadmap
Posted by Osma Suominen <os...@helsinki.fi>.
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.
+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.
>
>
>
>
>
>
--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
osma.suominen@helsinki.fi
http://www.nationallibrary.fi
Re: Jena 3.3.0 roadmap
Posted by Dave Reynolds <da...@gmail.com>.
+1 thanks Andy.
Dave
On 25/04/17 14:52, Andy Seaborne wrote:
> 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.
>
>
>
>
>
>