| [lyo-dev] Fwd: Bumps in the road(map) |
|
Hello everyone,
Jena is planning to drop JDK 11 support shortly after JDK 21 LTS is released. Doesn’t seem a big problem for Lyo, we already build successfully on JDK 11, 17, 20, and 21-ea: https://github.com/eclipse/lyo/actions/runs/4707208264 However,
it could be disruptive for Lyo users. Our previous surveys show that quite a few users are stuck on Lyo 2.x or 4.x and haven’t migrated to Lyo 5 yet. If anyone wants a 2023 survey, please indicate your interest.
But this doesn’t seem like the most disruptive change to m. Their plan to do a javax->jakarta migration in one go means a lot of code changes would be needed, even if most of them could be automated. Dropping javax would mean a major release – Lyo 6.0.
Just like with Jena 3->4 migration, Lyo could trying staying on the last release of Jena 4.x for as long as possible and switch when the first CVE comes. Just as before, we need to be prepared, though. Ideally, we would release a lot of duplicate artifacts
that only differ in targeting jakarta. We could do this in a 5.x release. Another option is to do a breaking release Lyo 6.0 and maintain 5.x a bit longer if there would be real drive in the community for that. If anyone switched to jakarta.* already, please
offer your perspective on the move.
Dropping Json-ld 1.0 should not be a big deal but we can test it in Lyo by introducing a switch that would force 1.0 or 1.1 parser/serializer for JSON-LD. If you use JSON-LD actively, please give us your feedback on which version of it do you use and if
dropping 1.0 support would be disruptive for you.
This summer I am expecting to be really busy and the timeline from Jena looks quite aggressive. Any help is appreciated.
–Andrew
Vidarebefordrat brev:
|