|
We have an M2 due in two weeks now so I'm back on this. Does anyone think we can sort out the CDI integration in time for a final release? If not, I propose we target a 4.1 with these issues:
I plan this week to look at CI and see if we can produce a $version-M1 depending on which version we decide to go with. I then plan on working on the issues as I can.
Opinions are welcome 🙂
James R. Perkins
Software Developer
IBM
From: James Perkins <jperkins@xxxxxxx>
Sent: Tuesday, December 9, 2025 8:57 AM
To: rest-dev@xxxxxxxxxxx <rest-dev@xxxxxxxxxxx>
Subject: Jakarta REST Release Plans
Our current release plan [1] has 9 open issues. Does anyone feel we're going to have time to sort out the CDI changes we want? If not, should we be doing a 4.1 instead of a 5.0 given we won't be changing much else?
We do need changes for the OSSRH updates. This is something I can have a look at.
Jakarta EE 12 would like an M2 by January 27th. We missed the M1 release as we weren't ready for it. I don't think we should miss the M2, which was previously due today, though. The Jakarta REST spec is in the Jakarta EE Core Profile so we really need to be
prepared for a release.
James R. Perkins
Software Developer
IBM
|