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 2022/11/22 09:13:27 UTC
Towards Jena 4.7.0
4.7.0 is a large release.
The clock tick is during December.
Here's the status - there are a several items still to be completed.
It's unlikely to be at the start of December.
== In this release:
https://s.apache.org/jena-4.7.0-issues
Currently
38 issues
81 PRs
Major:
* Lucene upgrade 8.11.1 to 9.4.1 - @OyvindLGjesdal
There are changes to the stopword setting in the default
configuration of Lucene's StandardAnalyzer
Issue: https://github.com/apache/jena/issues/1581
PR: https://github.com/apache/jena/pull/1582
* LATERAL joins
This is an experimental feature.
Issue: https://github.com/apache/jena/issues/1615
PR: https://github.com/apache/jena/pull/1631
Documentation:
* RDF Patch
https://lists.apache.org/thread/8oc1gn2qnzx4ddwovx8h545jm270gpyx
Issue: https://github.com/apache/jena/issues/1618
PR: https://github.com/apache/jena/pull/1619
Documentation: https://github.com/apache/jena-site/pull/131
* Path improvements - @SimonBin et al
Plan: https://github.com/apache/jena/issues/1629
In-progress: https://github.com/apache/jena/pull/1616
In-progress: https://github.com/apache/jena/pull/1620
and also:
* ShEx: align naming with the SheX specs.
@ericprud / Eric Prud'hommeaux
Issue: https://github.com/apache/jena/issues/1592
PR: https://github.com/apache/jena/pull/1589
ShapeMap -> ShExMap issue-1592
There is a test-related companion PR to merge.
* Vue3 upgrade
https://github.com/apache/jena/issues/1306
https://github.com/apache/jena/pull/1480
This may require a hard refresh in the browser.
* Source code folder reorganisation
Rename jena-tdb directory as jena-tdb1
Move jena-tdb2 directory to the top level directory
Issue: https://github.com/apache/jena/issues/1539
Issue: https://github.com/apache/jena/issues/1540
Other contributions:
* Improved AsyncParser - @Aklakan / Claus Stadler
Issue: https://github.com/apache/jena/issues/1477
PR: https://github.com/apache/jena/pull/1478
* Improve Graph.isEmpty - @Aklakan / Claus Stadler
Issue: https://github.com/apache/jena/issues/1548
PR: https://github.com/apache/jena/issues/1549, 1450
* Fix error handling for tabs in URI - @bvosburgh-tq
Issue: https://github.com/apache/jena/issues/1551
PR: https://github.com/apache/jena/pull/1552
* CrossOriginFilter handles OPTIONS request - @SimonBin
Issue: https://github.com/apache/jena/issues/1516
PR: https://github.com/apache/jena/pull/1529
* Service Enhancer fix - @Aklakan
Issue: https://github.com/apache/jena/issues/1517
PR: https://github.com/apache/jena/pull/1518/files
Re: Towards Jena 4.7.0
Posted by Martynas Jusevičius <ma...@atomgraph.com>.
Updated based on Andy's comments + support for Writer registries as well.
https://github.com/apache/jena/pull/1682
On Fri, Dec 16, 2022 at 11:04 AM rvesse@dotnetrdf.org
<rv...@dotnetrdf.org> wrote:
>
> Looks nice and straightforward, have approved and merged
>
> Thanks,
>
> Rob
>
> From: Martynas Jusevičius <ma...@atomgraph.com>
> Date: Thursday, 15 December 2022 at 21:49
> To: dev@jena.apache.org <de...@jena.apache.org>
> Subject: Re: Towards Jena 4.7.0
> I'd like to add https://github.com/apache/jena/pull/1677 if it's not
> too late. I think it's pretty low risk.
>
> On Thu, Dec 15, 2022 at 10:12 PM Andy Seaborne <an...@apache.org> wrote:
> >
> >
> >
> > On 01/12/2022 18:12, Andy Seaborne wrote:
> > > This is progressing - hopefully sometime between mid December and
> > > Christmas.
> > >
> > > There have been a lot of changes, and there are some nearly but not
> > > quite there yet PRs.
> > >
> > > It is in a sufficiently completed state now that the development
> > > codebase can be tested as widely as possible.
> > >
> > > I like to have a period of stability. This reduces the risk of
> > > unexpected changes in the 4.7.0 release.
> >
> > Hopefully final PRs have gone in.
> >
> > There is a sort ordering issue outstanding. I have a branch which needs
> > cleaning but does address the issue. For something like this, I think
> > its too late to put into the release, there being a chance of unexpected
> > corner cases.
> >
> > Andy
Re: Towards Jena 4.7.0
Posted by "rvesse@dotnetrdf.org" <rv...@dotnetrdf.org>.
Looks nice and straightforward, have approved and merged
Thanks,
Rob
From: Martynas Jusevičius <ma...@atomgraph.com>
Date: Thursday, 15 December 2022 at 21:49
To: dev@jena.apache.org <de...@jena.apache.org>
Subject: Re: Towards Jena 4.7.0
I'd like to add https://github.com/apache/jena/pull/1677 if it's not
too late. I think it's pretty low risk.
On Thu, Dec 15, 2022 at 10:12 PM Andy Seaborne <an...@apache.org> wrote:
>
>
>
> On 01/12/2022 18:12, Andy Seaborne wrote:
> > This is progressing - hopefully sometime between mid December and
> > Christmas.
> >
> > There have been a lot of changes, and there are some nearly but not
> > quite there yet PRs.
> >
> > It is in a sufficiently completed state now that the development
> > codebase can be tested as widely as possible.
> >
> > I like to have a period of stability. This reduces the risk of
> > unexpected changes in the 4.7.0 release.
>
> Hopefully final PRs have gone in.
>
> There is a sort ordering issue outstanding. I have a branch which needs
> cleaning but does address the issue. For something like this, I think
> its too late to put into the release, there being a chance of unexpected
> corner cases.
>
> Andy
Re: Towards Jena 4.7.0
Posted by Martynas Jusevičius <ma...@atomgraph.com>.
I'd like to add https://github.com/apache/jena/pull/1677 if it's not
too late. I think it's pretty low risk.
On Thu, Dec 15, 2022 at 10:12 PM Andy Seaborne <an...@apache.org> wrote:
>
>
>
> On 01/12/2022 18:12, Andy Seaborne wrote:
> > This is progressing - hopefully sometime between mid December and
> > Christmas.
> >
> > There have been a lot of changes, and there are some nearly but not
> > quite there yet PRs.
> >
> > It is in a sufficiently completed state now that the development
> > codebase can be tested as widely as possible.
> >
> > I like to have a period of stability. This reduces the risk of
> > unexpected changes in the 4.7.0 release.
>
> Hopefully final PRs have gone in.
>
> There is a sort ordering issue outstanding. I have a branch which needs
> cleaning but does address the issue. For something like this, I think
> its too late to put into the release, there being a chance of unexpected
> corner cases.
>
> Andy
Re: Towards Jena 4.7.0
Posted by Andy Seaborne <an...@apache.org>.
On 01/12/2022 18:12, Andy Seaborne wrote:
> This is progressing - hopefully sometime between mid December and
> Christmas.
>
> There have been a lot of changes, and there are some nearly but not
> quite there yet PRs.
>
> It is in a sufficiently completed state now that the development
> codebase can be tested as widely as possible.
>
> I like to have a period of stability. This reduces the risk of
> unexpected changes in the 4.7.0 release.
Hopefully final PRs have gone in.
There is a sort ordering issue outstanding. I have a branch which needs
cleaning but does address the issue. For something like this, I think
its too late to put into the release, there being a chance of unexpected
corner cases.
Andy
Re: Towards Jena 4.7.0
Posted by Andy Seaborne <an...@apache.org>.
This is progressing - hopefully sometime between mid December and Christmas.
There have been a lot of changes, and there are some nearly but not
quite there yet PRs.
It is in a sufficiently completed state now that the development
codebase can be tested as widely as possible.
I like to have a period of stability. This reduces the risk of
unexpected changes in the 4.7.0 release.
PRs that touch core functionality (changes in modules that almost
everything uses to make Fuseki work) need a strong justification. "My
use case" is not a strong justification :-)
Changes in modules that self-contained and aren't significant
dependencies of other parts of the system have less risk.
Large PRs need a stronger justification else wait until next cycle.
Small, point fixes PRs do get considered throughout - and should be
"point". Again, not touching things they don't need to.
Andy
And if something does not get tested and could have been ... we can't
get into a cycle of consuming PMC time.
On 22/11/2022 09:13, Andy Seaborne wrote:
> 4.7.0 is a large release.
>
> The clock tick is during December.
>
> Here's the status - there are a several items still to be completed.
> It's unlikely to be at the start of December.
>
> == In this release:
>
> https://s.apache.org/jena-4.7.0-issues
>
> Major:
>
> * Lucene upgrade 8.11.1 to 9.4.1 - @OyvindLGjesdal
Now 9.4.2
> * LATERAL joins
Merged.
> * RDF Patch
Merge - low impact outside of the new feature.
> * Path improvements - @SimonBin et al
First wave, early there - the rest can wait.
https://github.com/apache/jena/pull/1629.
> * ShEx: align naming with the SheX specs.
And some other ShEx things. Ready though it needs post-merge cleanup.
---
Replacing Apache Commons File Upload - not for 4.7.0.
There are per-web container features in order to use the servlet
standard for this. Jetty works; Tomcat has not been done yet - it may
need user action to reconfigure Tomcat.
---
Sorting bug :
https://github.com/apache/jena/pull/1634
The one thing outstanding it would be good to get in but certainly "at
risk". (My prototype works - but that is not a good enough justification!)
Transactions over complex model setups:
https://github.com/apache/jena/pull/1583
Unclear what the fundamental cause is. It may be small, it may not.