-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question related to next jersey release #5433
Comments
The first release is 2.41, then 3.0.12, then 3.1.4.
but not JPMS, which ought to be part of 3.2, hopefully after 3.1.4. |
Ok, thank you, that's great. Could you please add a few words on how you plan contents and dates of upcoming jersey releases (see my first question)? It would help us to sync our own release planning. |
ASAP :) We have some open PRs we want to review for the release, hopefully we will be able to finish 2.41 next week. The other releases should come shortly after. As for 3.2, there could be some more work, however. |
Ok, thanks for the info. Looking forward for 3.1.4 and 3.2 :) |
Hi, I'd like to better understand how dates and contents of jersey releases are coordinated. I tried to find something at the mailing list (https://www.eclipse.org/lists/jersey-dev), the wiki roadmap (https://github.com/eclipse-ee4j/jersey/wiki/Road-Map) and the milestone list (https://github.com/eclipse-ee4j/jersey/milestones) but could not find more details on this. A short explaination would be great :)
In particular, we are eagerly waiting for a release containing
Is it correct that release 3.2 (announced for this month) will contain these changes?
Thank you very much for your feedback!
The text was updated successfully, but these errors were encountered: