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 2013/08/23 20:04:34 UTC
Jena 2.11.0 release?
We were discussing a release
http://mail-archives.apache.org/mod_mbox/jena-dev/201307.mbox/%3C51F8EEE7.4040109%40apache.org%3E
and then things seem to have got rather busy.
I think we should try for a release even if everything isn't done, then
release again if necessary. There are some great new things already in
the pipeline.
We have a number of things and I think this is worth bumping to 2.11.
* New website
* jena-text
* jena-jdbc
I'm assuming that these are not in download, they are in trunk though,
so released via maven and it all forms part of one release vote.
jena-text drags in Lucene which might be considered a bit big to put
into the distribution (not something that worries me that much).
jena-jdbc:
Is there documentation?
(at least something an announcment can point to :-)
And also:
* jena-client
Include if ready, not blocking.
* jena-security
Not sure the roadmap is here. Claude - thoughts?
It can be anything from in trunk, so part of the formal release if the
legals are done, to advertising and keeping as a SNAPSHOT for now but
version-fixed to 2.11.0.
(ps you want to depend on apache-jena-libs, not apache-jena)
Andy
Re: Jena 2.11.0 release?
Posted by Andy Seaborne <an...@apache.org>.
To move it to trunk, use "svn mv" and edit the top level build POM. Let
dev@ know. We can finetune the build due to this (and the other
changes) when "in trunk".
Switching on and off is as simple as commenting in or out the <module>
entry (as as jena-jdbc current does).
Minor comment:
In NOTICE
"Apache Jena" -> "Apache Jena - Security module"
(a better than than "security" if you prefer)
just to be clear what it refers to this module.
Andy
On 25/08/13 21:11, Claude Warren wrote:
> Andy,
>
> Is there a recommended process for moving from experimental to trunk?
>
> I think the pom is ready,-- other than changing the version number to match
> the Jena version and setting the relaive parent path in the pom .
>
> Claude
>
>
> On Sat, Aug 24, 2013 at 4:42 PM, Andy Seaborne <an...@apache.org> wrote:
>
>> On 24/08/13 15:03, Claude Warren wrote:
>>
>>> I would like to include jena-security in the distribution as it is
>>> sensitive to the Jena version. Adding it to the trunk would be my
>>> objective. If there are no issues I would like to do that for the 2.11
>>> release. What legals need to be done? Technically (besides adding the
>>> code to the trunk as opposed to experimental) what needs to be done?
>>>
>>> I will modify the pom to depend on apache-jena-libs.
>>>
>>> Claude
>>>
>>
>> Sounds good. Let's aim to add to trunk if everyone is happy with that.
>>
>> The legal issues come from dependencies that jena-security uses. If it's
>> only built to maven then things are easier because we, the Jena project, as
>> not shipping other project's binaries.
>>
>> There should be a NOTICE and LICENSE in the module for people who checkout
>> just that module.
>>
>> The jar files should also have a NOTICE and LICENSE in META-INF.
>>
>> The build we have will automatically put NOTICE and LICENSE from the
>> top-level directory of the module into the jar, so having module-level
>> NOTICE and LICENSE serves two purposes.
>>
>> jena-arq's is a good starting place as they are quite simple - just
>> referring to copyrights from pre-ASF.
>>
>> If additional dependencies are from an Apache project, that means looking
>> in that project's NOTICE and LICENSE files. If we, jena, are not shipping
>> a dependency as a binary, (i.e. the build is only to maven) then it's
>> unlikely that we need to change anything.
>>
>>
>> Currently, the two things that are complicated for us are the binary
>> distribution and Fuseki. Both reship dependencies and both have their own
>> NOTICE/LICENSE which is different to the usual source.
>>
>> For example, Fuseki is the most complicated because the server jar is an
>> uber-jar so even in maven form, it's shipping every Jena dependency.
>>
>> Fuseki now uses the shade plugin to build the combined jar with License
>> and Notice helpers added. The helpers put in combined NOTICE and LICENSE
>> if required. As this is the first release using the shade plugin, this
>> needs checking.
>>
>> The apache-jena distribution includes special NOTICE and LICENSE for all
>> the included dependencies and these are added to the assembled files.
>>
>> NOTICE is supposed to be short and minimal. However, they also must be
>> the rolled up NOTICE from all reship binaries ... and not everyone's NOTICE
>> is short. Styles have changed over the years; there are principles for what
>> to put in but it's not formulaic.
>>
>> Andy
>>
>>
>
>
Re: Jena 2.11.0 release?
Posted by Claude Warren <cl...@xenei.com>.
Andy,
Is there a recommended process for moving from experimental to trunk?
I think the pom is ready,-- other than changing the version number to match
the Jena version and setting the relaive parent path in the pom .
Claude
On Sat, Aug 24, 2013 at 4:42 PM, Andy Seaborne <an...@apache.org> wrote:
> On 24/08/13 15:03, Claude Warren wrote:
>
>> I would like to include jena-security in the distribution as it is
>> sensitive to the Jena version. Adding it to the trunk would be my
>> objective. If there are no issues I would like to do that for the 2.11
>> release. What legals need to be done? Technically (besides adding the
>> code to the trunk as opposed to experimental) what needs to be done?
>>
>> I will modify the pom to depend on apache-jena-libs.
>>
>> Claude
>>
>
> Sounds good. Let's aim to add to trunk if everyone is happy with that.
>
> The legal issues come from dependencies that jena-security uses. If it's
> only built to maven then things are easier because we, the Jena project, as
> not shipping other project's binaries.
>
> There should be a NOTICE and LICENSE in the module for people who checkout
> just that module.
>
> The jar files should also have a NOTICE and LICENSE in META-INF.
>
> The build we have will automatically put NOTICE and LICENSE from the
> top-level directory of the module into the jar, so having module-level
> NOTICE and LICENSE serves two purposes.
>
> jena-arq's is a good starting place as they are quite simple - just
> referring to copyrights from pre-ASF.
>
> If additional dependencies are from an Apache project, that means looking
> in that project's NOTICE and LICENSE files. If we, jena, are not shipping
> a dependency as a binary, (i.e. the build is only to maven) then it's
> unlikely that we need to change anything.
>
>
> Currently, the two things that are complicated for us are the binary
> distribution and Fuseki. Both reship dependencies and both have their own
> NOTICE/LICENSE which is different to the usual source.
>
> For example, Fuseki is the most complicated because the server jar is an
> uber-jar so even in maven form, it's shipping every Jena dependency.
>
> Fuseki now uses the shade plugin to build the combined jar with License
> and Notice helpers added. The helpers put in combined NOTICE and LICENSE
> if required. As this is the first release using the shade plugin, this
> needs checking.
>
> The apache-jena distribution includes special NOTICE and LICENSE for all
> the included dependencies and these are added to the assembled files.
>
> NOTICE is supposed to be short and minimal. However, they also must be
> the rolled up NOTICE from all reship binaries ... and not everyone's NOTICE
> is short. Styles have changed over the years; there are principles for what
> to put in but it's not formulaic.
>
> Andy
>
>
--
I like: Like Like - The likeliest place on the web<http://like-like.xenei.com>
Identity: https://www.identify.nu/user.php?claude@xenei.com
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Jena 2.11.0 release?
Posted by Andy Seaborne <an...@apache.org>.
On 24/08/13 15:03, Claude Warren wrote:
> I would like to include jena-security in the distribution as it is
> sensitive to the Jena version. Adding it to the trunk would be my
> objective. If there are no issues I would like to do that for the 2.11
> release. What legals need to be done? Technically (besides adding the
> code to the trunk as opposed to experimental) what needs to be done?
>
> I will modify the pom to depend on apache-jena-libs.
>
> Claude
Sounds good. Let's aim to add to trunk if everyone is happy with that.
The legal issues come from dependencies that jena-security uses. If
it's only built to maven then things are easier because we, the Jena
project, as not shipping other project's binaries.
There should be a NOTICE and LICENSE in the module for people who
checkout just that module.
The jar files should also have a NOTICE and LICENSE in META-INF.
The build we have will automatically put NOTICE and LICENSE from the
top-level directory of the module into the jar, so having module-level
NOTICE and LICENSE serves two purposes.
jena-arq's is a good starting place as they are quite simple - just
referring to copyrights from pre-ASF.
If additional dependencies are from an Apache project, that means
looking in that project's NOTICE and LICENSE files. If we, jena, are
not shipping a dependency as a binary, (i.e. the build is only to maven)
then it's unlikely that we need to change anything.
Currently, the two things that are complicated for us are the binary
distribution and Fuseki. Both reship dependencies and both have their
own NOTICE/LICENSE which is different to the usual source.
For example, Fuseki is the most complicated because the server jar is an
uber-jar so even in maven form, it's shipping every Jena dependency.
Fuseki now uses the shade plugin to build the combined jar with License
and Notice helpers added. The helpers put in combined NOTICE and
LICENSE if required. As this is the first release using the shade
plugin, this needs checking.
The apache-jena distribution includes special NOTICE and LICENSE for all
the included dependencies and these are added to the assembled files.
NOTICE is supposed to be short and minimal. However, they also must be
the rolled up NOTICE from all reship binaries ... and not everyone's
NOTICE is short. Styles have changed over the years; there are
principles for what to put in but it's not formulaic.
Andy
Re: Jena 2.11.0 release?
Posted by Claude Warren <cl...@xenei.com>.
I would like to include jena-security in the distribution as it is
sensitive to the Jena version. Adding it to the trunk would be my
objective. If there are no issues I would like to do that for the 2.11
release. What legals need to be done? Technically (besides adding the
code to the trunk as opposed to experimental) what needs to be done?
I will modify the pom to depend on apache-jena-libs.
Claude
On Fri, Aug 23, 2013 at 7:04 PM, Andy Seaborne <an...@apache.org> wrote:
> We were discussing a release
>
> http://mail-archives.apache.**org/mod_mbox/jena-dev/201307.**
> mbox/%3C51F8EEE7.4040109%**40apache.org%3E<http://mail-archives.apache.org/mod_mbox/jena-dev/201307.mbox/%3C51F8EEE7.4040109%40apache.org%3E>
>
> and then things seem to have got rather busy.
>
> I think we should try for a release even if everything isn't done, then
> release again if necessary. There are some great new things already in the
> pipeline.
>
> We have a number of things and I think this is worth bumping to 2.11.
>
> * New website
>
> * jena-text
> * jena-jdbc
>
> I'm assuming that these are not in download, they are in trunk though, so
> released via maven and it all forms part of one release vote.
>
> jena-text drags in Lucene which might be considered a bit big to put into
> the distribution (not something that worries me that much).
>
> jena-jdbc:
> Is there documentation?
> (at least something an announcment can point to :-)
>
> And also:
>
> * jena-client
> Include if ready, not blocking.
>
> * jena-security
>
> Not sure the roadmap is here. Claude - thoughts?
>
> It can be anything from in trunk, so part of the formal release if the
> legals are done, to advertising and keeping as a SNAPSHOT for now but
> version-fixed to 2.11.0.
>
> (ps you want to depend on apache-jena-libs, not apache-jena)
>
> Andy
>
>
>
>
>
>
--
I like: Like Like - The likeliest place on the web<http://like-like.xenei.com>
Identity: https://www.identify.nu/user.php?claude@xenei.com
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Jena 2.11.0 release?
Posted by Rob Vesse <rv...@yarcdata.com>.
I'm happy to move forwards on a release, end of next week is the earliest
I will have any time to review a release as I am on vacation tomorrow
through next Wed.
I think JDBC is in a good state now we've resolved the test hang issues
and the documentation is enough to get people going, it can likely be
improved later but is sufficient for now.
Rob
On 9/3/13 12:11 PM, "Andy Seaborne" <an...@apache.org> wrote:
>On 03/09/13 18:08, Claude Warren wrote:
>> Does the build process add the javadocs to the doc package?
>>
>> Is there a suggested location to place the documentation for modules? I
>> would like to see a process where the module build can update the
>>javadocs
>> (if that is not already done) and where the module documentation can be
>> kept in the module tree (perhaps under site there) and merged into the
>> master site during a build. Has anyone done anything like that? Does
>> anyone have suggestions for how to do this, or objections to doing so?
>>
>> Claude
>
>Claude,
>
>The documentation goes on the website. Pick somewhere like
>content/documentation/security-evaluator and put what you thing suitable
>there. It's your choice - I don't feel it is a blocker on the release
>if you don't.
>
>A copy of the current release javadoc will go in
> content/documentation/javadoc
>on release.
>
>The binaries contain what you need to get a IDE development system up
>and running with jars, source and javadoc.
>
>The build process is described at:
>
>https://cwiki.apache.org/confluence/display/JENA/Release+Process
>
>and the entire structure of POMs, plugins and assemblies.
>
> Andy
>
>>
>>
>> On Tue, Sep 3, 2013 at 1:51 PM, Andy Seaborne <an...@apache.org> wrote:
>>
>>> Let's move forwards to a release, even if it means we will want to do
>>> another release quite soon, otherwise we risk a long wait.
>>>
>>> I'd like to get the 2.11.0 done in the next week or so. It'll take
>>>more
>>> checking than a maintenance release because of the new modules but we
>>>have
>>> already taken a pass over all of them.
>>>
>>>
>>> Going through the new items:
>>>
>>> * New website
>>>
>>> Ready
>>>
>>> * jena-text
>>>
>>> Ready
>>>
>>> * jena-jdbc
>>>
>>> Ready to go? Tests now passing in finite time.
>>> Documentation on the website:
>>>
>>>http://jena.staging.apache.**org/documentation/jdbc/<http://jena.staging
>>>.apache.org/documentation/jdbc/>
>>>
>>> * jena-spatial
>>>
>>> Not yet in the main build, nor in Fuseki.
>>> Outstanding issue with the dependency on JTS.
>>>
>>> * jena-client
>>>
>>> Not sure of the status here. I don't mind how we proceed: I'm happen
>>>to
>>> include it, or to go through a announcement while in Experimental SVN,
>>>or
>>> something else.
>>>
>>> * jena-security
>>>
>>> This is now in the main build.
>>>
>>> There is some documentation at...
>>>
>>>https://github.com/Claudenw/**JenaSecurity/wiki/_pages<https://github.co
>>>m/Claudenw/JenaSecurity/wiki/_pages>
>>>
>>> but nothing for the main Jena website.
>>>
>>> Claude - what about at least a placeholder page for jena.a.o?
>>>
>>> -----
>>>
>>> Anything I've forgotten?
>>>
>>> Andy
>>>
>>>
>>
>>
>
Re: Jena 2.11.0 release?
Posted by Andy Seaborne <an...@apache.org>.
On 03/09/13 18:08, Claude Warren wrote:
> Does the build process add the javadocs to the doc package?
>
> Is there a suggested location to place the documentation for modules? I
> would like to see a process where the module build can update the javadocs
> (if that is not already done) and where the module documentation can be
> kept in the module tree (perhaps under site there) and merged into the
> master site during a build. Has anyone done anything like that? Does
> anyone have suggestions for how to do this, or objections to doing so?
>
> Claude
Claude,
The documentation goes on the website. Pick somewhere like
content/documentation/security-evaluator and put what you thing suitable
there. It's your choice - I don't feel it is a blocker on the release
if you don't.
A copy of the current release javadoc will go in
content/documentation/javadoc
on release.
The binaries contain what you need to get a IDE development system up
and running with jars, source and javadoc.
The build process is described at:
https://cwiki.apache.org/confluence/display/JENA/Release+Process
and the entire structure of POMs, plugins and assemblies.
Andy
>
>
> On Tue, Sep 3, 2013 at 1:51 PM, Andy Seaborne <an...@apache.org> wrote:
>
>> Let's move forwards to a release, even if it means we will want to do
>> another release quite soon, otherwise we risk a long wait.
>>
>> I'd like to get the 2.11.0 done in the next week or so. It'll take more
>> checking than a maintenance release because of the new modules but we have
>> already taken a pass over all of them.
>>
>>
>> Going through the new items:
>>
>> * New website
>>
>> Ready
>>
>> * jena-text
>>
>> Ready
>>
>> * jena-jdbc
>>
>> Ready to go? Tests now passing in finite time.
>> Documentation on the website:
>> http://jena.staging.apache.**org/documentation/jdbc/<http://jena.staging.apache.org/documentation/jdbc/>
>>
>> * jena-spatial
>>
>> Not yet in the main build, nor in Fuseki.
>> Outstanding issue with the dependency on JTS.
>>
>> * jena-client
>>
>> Not sure of the status here. I don't mind how we proceed: I'm happen to
>> include it, or to go through a announcement while in Experimental SVN, or
>> something else.
>>
>> * jena-security
>>
>> This is now in the main build.
>>
>> There is some documentation at...
>> https://github.com/Claudenw/**JenaSecurity/wiki/_pages<https://github.com/Claudenw/JenaSecurity/wiki/_pages>
>>
>> but nothing for the main Jena website.
>>
>> Claude - what about at least a placeholder page for jena.a.o?
>>
>> -----
>>
>> Anything I've forgotten?
>>
>> Andy
>>
>>
>
>
Re: Jena 2.11.0 release?
Posted by Claude Warren <cl...@xenei.com>.
Does the build process add the javadocs to the doc package?
Is there a suggested location to place the documentation for modules? I
would like to see a process where the module build can update the javadocs
(if that is not already done) and where the module documentation can be
kept in the module tree (perhaps under site there) and merged into the
master site during a build. Has anyone done anything like that? Does
anyone have suggestions for how to do this, or objections to doing so?
Claude
On Tue, Sep 3, 2013 at 1:51 PM, Andy Seaborne <an...@apache.org> wrote:
> Let's move forwards to a release, even if it means we will want to do
> another release quite soon, otherwise we risk a long wait.
>
> I'd like to get the 2.11.0 done in the next week or so. It'll take more
> checking than a maintenance release because of the new modules but we have
> already taken a pass over all of them.
>
>
> Going through the new items:
>
> * New website
>
> Ready
>
> * jena-text
>
> Ready
>
> * jena-jdbc
>
> Ready to go? Tests now passing in finite time.
> Documentation on the website:
> http://jena.staging.apache.**org/documentation/jdbc/<http://jena.staging.apache.org/documentation/jdbc/>
>
> * jena-spatial
>
> Not yet in the main build, nor in Fuseki.
> Outstanding issue with the dependency on JTS.
>
> * jena-client
>
> Not sure of the status here. I don't mind how we proceed: I'm happen to
> include it, or to go through a announcement while in Experimental SVN, or
> something else.
>
> * jena-security
>
> This is now in the main build.
>
> There is some documentation at...
> https://github.com/Claudenw/**JenaSecurity/wiki/_pages<https://github.com/Claudenw/JenaSecurity/wiki/_pages>
>
> but nothing for the main Jena website.
>
> Claude - what about at least a placeholder page for jena.a.o?
>
> -----
>
> Anything I've forgotten?
>
> Andy
>
>
--
I like: Like Like - The likeliest place on the web<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Jena 2.11.0 release?
Posted by Andy Seaborne <an...@apache.org>.
Let's move forwards to a release, even if it means we will want to do
another release quite soon, otherwise we risk a long wait.
I'd like to get the 2.11.0 done in the next week or so. It'll take more
checking than a maintenance release because of the new modules but we
have already taken a pass over all of them.
Going through the new items:
* New website
Ready
* jena-text
Ready
* jena-jdbc
Ready to go? Tests now passing in finite time.
Documentation on the website:
http://jena.staging.apache.org/documentation/jdbc/
* jena-spatial
Not yet in the main build, nor in Fuseki.
Outstanding issue with the dependency on JTS.
* jena-client
Not sure of the status here. I don't mind how we proceed: I'm happen to
include it, or to go through a announcement while in Experimental SVN,
or something else.
* jena-security
This is now in the main build.
There is some documentation at...
https://github.com/Claudenw/JenaSecurity/wiki/_pages
but nothing for the main Jena website.
Claude - what about at least a placeholder page for jena.a.o?
-----
Anything I've forgotten?
Andy
Re: Jena 2.11.0 release?
Posted by Andy Seaborne <an...@apache.org>.
On 24/08/13 14:58, Claude Warren wrote:
> JENA-397
> testing files not included in the test jar
>
> Closed as completed.
I closed this - I presume by "resolved" that is what was intended.
Andy
Re: Jena 2.11.0 release?
Posted by Claude Warren <cl...@xenei.com>.
JENA-397
testing files not included in the test jar
Closed as completed.
JENA-396
Request for Info
No responses so this can stay open. Though perhaps it should move to a
documentation category.
JENA-380
Migrate core tests to junit4
Open and will be working on it shortly.
On Fri, Aug 23, 2013 at 7:14 PM, Andy Seaborne <an...@apache.org> wrote:
> I went through JIRA and picked out the items with assigned names.
>
> This is not imply any blockers for a release; it's just here to help get
> an overview. No one should feel guilty.
>
> Please unassign, close, update or whatever if any are no longer
> appropriate.
>
> Feel free to take over any of mine :-)
>
> == Andy
>
> JENA-218
> Fuseki should allow timeouts to be specified on a per-request basis
>
> JENA-427
> Statistics for Fuseki usage.
>
> JENA-291
> NodeTableTrans re-implementation
>
> JENA-478
> Provide graceful server shutdown
>
> JENA-516
> Fuseki should use dataset transactions where available, not parse to an
> intermediate datastructure
>
> JENA-458
> Make model work across transaction boundaries / make model.begin do
> something reasonable.
>
> JENA-46
> Assembler registration improperly located
>
>
> == Chris
>
> JENA-43
> documentation errors on "the Assembler howto"
>
>
> == Claude
>
> JENA-397
> testing files not included in the test jar
>
> JENA-396
> Request for Info
>
> JENA-380
> Migrate core tests to junit4
>
>
> == Damian
>
> JENA-118
> SDB can't concurrently write (duplicate key error)
>
> JENA-28
> Drop Temporary Tables in Postgres (PATCH)
>
>
> == Dave
>
> JENA-61
> Expected result not entailed
>
> JENA-30
> Inconsistency in rdfs8
>
> JENA-168
> Progressive slow down due to unclosed interpreters
>
> JENA-246
> date time support in rules Min/Max operators
>
> JENA-149
> Nodes of type XSD duration don't equate-by-value forms with different
> lexical forms for the same duration.
>
> JENA-75
> Document assembler URIs for reasoners
>
> JENA-68
> Embedded new lines in Rule string literals
>
> JENA-410
> Reinstate or deprecate user-defined types
>
>
> == Ian
>
> JENA-64
> Failed read of imported ontology leaves a memory in the ModelMaker
>
> JENA-58
> Schemagen includeSource issues
>
> JENA-353
> RDFList.append doc indicates a copy is created not always so.
>
> JENA-357
> rdfcat warnings appear on stdout
>
> JENA-280
> OntTools.nameHierarchyRoots gives wrong answer when reasoner attached
>
> JENA-57
> Schemagen does not cope well with resources that have multiple language
> tags
>
> JENA-84
> Clearing the cache in an OntModel should clear the ModelMaker cache as well
>
>
> == Rob
>
> JENA-388
> Make Fuseki responses cacheable
>
> JENA-382
> SPARQL Updates are not cancelable
>
> JENA-267
> SPARQL JSON Parser is not streaming
>
> JENA-507
> Add support for Leviathan extension functions to ARQ
>
>
> == Stephen
>
> JENA-119
> Eliminate memory bounds during query execution
>
> JENA-226
> New Client API
>
--
I like: Like Like - The likeliest place on the web<http://like-like.xenei.com>
Identity: https://www.identify.nu/user.php?claude@xenei.com
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Jena 2.11.0 release?
Posted by Andy Seaborne <an...@apache.org>.
I went through JIRA and picked out the items with assigned names.
This is not imply any blockers for a release; it's just here to help get
an overview. No one should feel guilty.
Please unassign, close, update or whatever if any are no longer appropriate.
Feel free to take over any of mine :-)
== Andy
JENA-218
Fuseki should allow timeouts to be specified on a per-request basis
JENA-427
Statistics for Fuseki usage.
JENA-291
NodeTableTrans re-implementation
JENA-478
Provide graceful server shutdown
JENA-516
Fuseki should use dataset transactions where available, not parse to an
intermediate datastructure
JENA-458
Make model work across transaction boundaries / make model.begin do
something reasonable.
JENA-46
Assembler registration improperly located
== Chris
JENA-43
documentation errors on "the Assembler howto"
== Claude
JENA-397
testing files not included in the test jar
JENA-396
Request for Info
JENA-380
Migrate core tests to junit4
== Damian
JENA-118
SDB can't concurrently write (duplicate key error)
JENA-28
Drop Temporary Tables in Postgres (PATCH)
== Dave
JENA-61
Expected result not entailed
JENA-30
Inconsistency in rdfs8
JENA-168
Progressive slow down due to unclosed interpreters
JENA-246
date time support in rules Min/Max operators
JENA-149
Nodes of type XSD duration don't equate-by-value forms with different
lexical forms for the same duration.
JENA-75
Document assembler URIs for reasoners
JENA-68
Embedded new lines in Rule string literals
JENA-410
Reinstate or deprecate user-defined types
== Ian
JENA-64
Failed read of imported ontology leaves a memory in the ModelMaker
JENA-58
Schemagen includeSource issues
JENA-353
RDFList.append doc indicates a copy is created not always so.
JENA-357
rdfcat warnings appear on stdout
JENA-280
OntTools.nameHierarchyRoots gives wrong answer when reasoner attached
JENA-57
Schemagen does not cope well with resources that have multiple language tags
JENA-84
Clearing the cache in an OntModel should clear the ModelMaker cache as well
== Rob
JENA-388
Make Fuseki responses cacheable
JENA-382
SPARQL Updates are not cancelable
JENA-267
SPARQL JSON Parser is not streaming
JENA-507
Add support for Leviathan extension functions to ARQ
== Stephen
JENA-119
Eliminate memory bounds during query execution
JENA-226
New Client API
Re: Jena 2.11.0 release?
Posted by Rob Vesse <rv...@yarcdata.com>.
Yes we got a bit busy with fixing some issues that came up. I have some
thoughts about JDBC which I will send in a separate email.
Bumping to 2.11.0 does seem appropriate.
Rob
On 8/23/13 11:04 AM, "Andy Seaborne" <an...@apache.org> wrote:
>We were discussing a release
>
>http://mail-archives.apache.org/mod_mbox/jena-dev/201307.mbox/%3C51F8EEE7.
>4040109%40apache.org%3E
>
>and then things seem to have got rather busy.
>
>I think we should try for a release even if everything isn't done, then
>release again if necessary. There are some great new things already in
>the pipeline.
>
>We have a number of things and I think this is worth bumping to 2.11.
>
>* New website
>
>* jena-text
>* jena-jdbc
>
>I'm assuming that these are not in download, they are in trunk though,
>so released via maven and it all forms part of one release vote.
>
>jena-text drags in Lucene which might be considered a bit big to put
>into the distribution (not something that worries me that much).
>
>jena-jdbc:
>Is there documentation?
>(at least something an announcment can point to :-)
>
>And also:
>
>* jena-client
>Include if ready, not blocking.
>
>* jena-security
>
>Not sure the roadmap is here. Claude - thoughts?
>
>It can be anything from in trunk, so part of the formal release if the
>legals are done, to advertising and keeping as a SNAPSHOT for now but
>version-fixed to 2.11.0.
>
>(ps you want to depend on apache-jena-libs, not apache-jena)
>
> Andy
>
>
>
>
>