[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [rdf4j-dev] release planning for 4.2.4 and 4.3.0
|
Hi all, Jeen
I'd like to come back to the release planning once more,
specifically 4.3.0
We are approaching the final phase of our product release and would
require a proper (final) release of RDF4J, i.e. 4.3.0. Note that we
are currently using 4.3.0-M1 and for our final release want to
switch to 4.3.0
Would it be possible to aim for the 4.3.0 release within the next
two weeks from now?
Thanks,
Andreas
Am 23.04.2023 um 04:09 schrieb Jeen
Broekstra:
Sorry Matthew, 4.2.4 is already out the door - but there's
always a next release :)
Jeen
On Sat, 22 Apr 2023, at 23:48, Matthew Nguyen via rdf4j-dev
wrote:
Hi Jeen, I expect to submit a patch to the
activetransactionregistry (to make it pluggable) over the
next couple of days. Wouldn't complain if 4.2.4 stalled til
next weekend :-)
Thanks all - I didn't get around to doing any
releases last weekend, in the end, however I've
got some time today and tomorrow. I'm taking a
quick look at
https://github.com/eclipse/rdf4j/issues/4512,
after that I'll prep the 4.2.4 release. Not yet
sure I can get around to a second milestone this
weekend - we'll see how it goes.
Jeen
On Wed, 12 Apr 2023, at 07:58, Bart Hanssens
(BOSA) via rdf4j-dev wrote:
Hi,
I’m hoping to get the
(somewhat) newer versions of ES / Solr /
Lucene approved for 4.3.0
(still a few small CQs that
need IPR-approval from Eclipse…
I’ll have to send a few
gentle reminders since the tickets have
been entered quite some weeks ago)
Though not a blocker IMHO…
Best regards
Bart
Hi
Jeen,
thanks
for the initiative.
I'd
like to comment from our perspective
on 4.3.0:
we
are currently using the 4.3.0 M1 build
(which for us allowed to do the
Jakarta EE migration by getting rid of
JAXB in the core modules). For our
final product release we would like to
ship a proper RDF4J release, i.e.
4.3.0. From the timeline it would be
really great to have the 4.3.0 out
within the next 4 weeks, which should
be in line with what you are stating.
One
further remark: the current 4.3
snapshot contains the changes to the
repository configuration schema /
vocabulary. We can offer to test this
in the wild (specifically w.r.t
backwards compatibility) when there is
another M2 milestone. Do you think it
makes sense to have another M2 build
for this?
Regarding
4.2.4: no strong opinion. If there are
fixes, better to roll them out earlier
than later :)
I
was considering doing a 4.2.4
patch release next week as
there's several bug fixes
available (see https://github.com/orgs/eclipse/projects/36/views/4
). There's also a couple of open
bug reports, some of which are
in progress, but they seem to
have stalled a bit (partly due
to myself not having a lot of
spare time these days).
I'd
also like to propose that we
start thinking about a release
for 4.3.0. Ideally I'd like us
to get to a 4.3 final release
quite soon, so that afterwards
we can merge the 5.0 branch into
develop, and give its
development more priority.
There's
still a lot of open issues
planned against 4.3 but I want
to do some culling in that, move
them back to 5.0 or unplanned
until we can get around to them.
There's some things I'd
_definitely_ like to see
included though. For me, the
main themes of 4.3.0 are:
- prep
of our project to migrate fully
to Jakarta EE (all the work Erik
GB has been doing)
- migration
to tag-based config vocabulary
- various
SHACL features and improvements
Thoughts?
Questions? Protests?
_______________________________________________
rdf4j-dev mailing list
_______________________________________________
rdf4j-dev mailing list
_______________________________________________
rdf4j-dev mailing list
_______________________________________________
rdf4j-dev mailing list
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev