[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [websocket-dev] Plan review for WebSocket 2.3
|
On 25/03/2025 21:30, Ed Bratt via websocket-dev wrote:
Thank you for submitting the web-socket 2.3 plan review.
If I'm reading the proposed WebSocket plan review <https://deploy-
preview-806--jakartaee-specifications.netlify.app/specifications/
websocket/2.3/> for version 2.3 correctly, it says: Transfer TCK from
Platform TCK project plus Bug Fixes, Behavior Clarifications, new
features. But there doesn't seem to be any evidence of bug fixes or
specification changes that might be under consideration for EE 12. There
are no issues with the EE12 tag, for example.
You are correct that no issues are explicitly tagged for WebSocket 2.3 /
Jakarta EE 12.
The plan is to address anything marked as a bug and as many of the
enhancements as there is time and support for.
If this is just, move the TCK from one repository to another, do we need
a feature update for that work?
There will be feature updates.
I'm absolutely not against a feature release of WehSocket, but there
isn't much to reflect actual planning for this release. Why go to the
work of generating a feature release if we don't have feature plans?
Perhaps just reviewing the open issues and deciding if any rate the
addition of the EE12 tag would suffice. OR, if that's been done, and
there really isn't anything that is "above the line" maybe we can just
transfer the TCK without changes and handle this with a micro-release.
That is because there hasn't been any planning beyond "anything marked
as a bug and as many of the enhancements as there is time and support
for". I'm pretty much on my own on WebSocket at the moment so the time I
do have is focused moving things forward rather than on admin tasks like
reviewing the tags on issues.
Also, please consider adding text to the Spec. development page, and
also to the top repository readme that tells readers how to get engaged
with this project (file issues, join the websocket-dev mailing list,
meetings (if you have them), Star the repository, whatever ...).
Ack.
Mark
