We discovered a bug/feature/? preventing a 4.0 client talking to a 3.7 server (latest graphdb). We weren't able fo fille the issue before the weekend but will do so asap tomorrow. Not sure of the criticality for you,for us it's a 4.0 migration showstopper.
Am 15. Mai 2022 08:43:00 MESZ schrieb "Håvard Ottestad" <hmottestad@xxxxxxxxx>:
I took a look at those PRs and I see that one of them needs more work and the other needs some tests. I don't think any of these are blockers that are critical for 4.0.1.
Håvard
These two could potentially make it in:
- https://github.com/eclipse/rdf4j/pull/3879Håvard Fwiw I've just noticed that we seem to have a couple of third party contributions for small bug fixes coming in. Are you aiming to include those as well?
Jeen
On Fri, 13 May 2022, at 16:58, Jeen Broekstra wrote:
Sounds good!
Cheers,
Jeen
On Thu, 12 May 2022, at 17:24, Håvard Ottestad wrote:
Hi everyone,
I would like to start moving towards releasing 4.0.1 soon. We have merged a few bug fixes already and I can see a few more that could probably make it in.
_______________________________________________
rdf4j-dev mailing list
_______________________________________________
rdf4j-dev mailing list
_______________________________________________rdf4j-dev mailing listrdf4j-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. |
