It's not like its gone irreversibly - SDB came back.
I do agree with the focus of do the core things well.
I have a batch of website changes to go with the retiring modules so
I'll put in a PR for this and then add it to the list of website changes.
Recorded as JENA-2040.
Andy
On 08/02/2021 11:03, Rob Vesse wrote:
I think there's a strong argument for retiring Elephas
It was a useful piece of work at the time but didn't get a lot of traction and
the data analytics/science space has moved on a lot past Hadoop Map/Reduce in
the meantime. We've certainly abandoned any support for Hadoop Map/Reduce in
our products
There's also argument for doing less if we don’t have the userbase/contributors
to justify it. OSS as a whole has also moved on a lot and its much easier for
people to create and support projects on top of Jena that add these kinds of
extra capabilities that don't make sense in the core
Rob
On 05/02/2021, 11:12, "Andy Seaborne" <[email protected]> wrote:
3.17.0 was 2020-12-01
so the usual timescale is end Feb - end March.
Personally, I'd rather let it slip this time if there are any stability
issues. That said, we've had a ticket reporting one bug due to clearup
so some downstream is at least running with the latest code. (The
version number in GIT and in JIRA isn't updated yet.)
Jena4:
* Java11 [done]
the users@ feedback was this is enough to merit "jena4".
* Rename default branch as "main"
* Retire SDB
* Retire jena-text-es
* Deprecation cleanup [ongoing...]
* IRIx abstraction
(should this become package: org.apache.jena.iri?
and rename the old one?)
This may tighten up some illegal use of URIs (%XX -
where XX is not hex).
* jena-core: rename RDFReader as RDFReaderI
and RDFWriter a RDFWriterI to avoid name clashes
* Upgrades (except jetty 10/11 - wait until our Java11 move has gone OK)
jena-elephas does not build on Java11.
What else, especially things that are changes?
As ever - contributions welcome!
Andy
