| I’ll try to get to it soon.
This is the script I use: https://github.com/eclipse/rdf4j/blob/main/scripts/milestone-release.shHåvard On 22 Feb 2023, at 10:09, Andreas Schwarte <aschwarte10@xxxxxxxxx> wrote:
Hi,
thanks Jean and Bart for your responses. This really helps in getting a picture.
Question to Håvard: could you maybe help us and produce a 4.3.0-M1 build so that we can continue the path towards Jakarta EE in our product? I would also be interested to learn (maybe watch?) how such releases are created if time permits.
Thanks, Andreas
Hi,
still working on the ElasticSearch / Solr upgrade (the remaining issue is the ElasticSearch-runner used in tests),
but as far as I’m concerned that upgrade is not be essential for getting 4.3.0 out of the door…
Best regards
Bart
my 2 cents: not a problem, we can do a milestone build whenever.
I am not really on top of the proposed Jakarta migration work to be honest, and am currently finding it difficult to find sufficient time to really get into it - so my opinion is purely that of an interested spectator :) I get the impression
that both yourself, Wolfgang, and Eric GB are tackling this head on though!
As for planning a 4.3 release, I am not quite sure. The current list of issues planned against 4.3.0 (https://github.com/eclipse/rdf4j/milestone/89) is rather long and, I feel,
not very well groomed. I suggest we try and go through that list and weed it down a bit to the "must haves" - then we can start guesstimating a realistic release date. I'll give it a first pass to remove some issues that I think are either non-critical or
just unlikely to be picked up in the near term.
On Sat, 18 Feb 2023, at 05:36, Andreas Schwarte wrote:
in our product we are currently doing the Jakarta EE migration. One of the remaining issues is the use of 'javax.xml.bind' in some of the core RDF4J APIs (see [1]). Meanwhile there is
also a fix available for the development branch (i.e. targeting 4.3.0) (see [2]). We have verified the proposed change using a locally built snapshot.
Would it be possible to create an 4.3.0-M1 build next week, so that we can do further validation in our product and continue the bigger migration to Jakarta EE on our end?
I would guess that also other users of RDF4J who are currently going the road towards Jakarta EE would like to see this fix available.
Also, what is the current timeline for the 4.3.0 release?
Btw: I really like to see things like these issues to be resolved so smoothly in the RDF4J project in a collaboration of multiple developers. Thanks for that!
_______________________________________________
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev
|
