Bill,
i
assume you are right, but…
I
have no problem with immediately calling JAX-RS 2.2 now
JAX-RS 3.0, but this is really something I'd like to ask the
PMC to decide for ALL spec projects before we do it.
The
effect of your words would be that ALL Jakarta
specifications (not just JAX-RS) that like to add ANY -even
backwards compatible- functionality MUST immediate increase
their major version number, because they MUST rename the
package in that case. I wonder why the PMC / Spec Committee
did not tell us much, much earlier? Thanks for further
confusing all of us! I just published the roadmap including
version numbers in my JakartaOne Livestream talk to
thousands of viewers, and the prerecording was checked by
before streaming, and nobody of the officials complaint
about the version numbers told (while they DID complainn
about the audio quality - so they DID listen). Sigh. ;-(
-Markus
I strongly
believe that the switch to the jakarta.* namespace should
result in a new major version of the spec, e.g., Jakarta
RESTful Web Services 3.0. It's a big incompatible change that
shouldn't be slipped in in a minor release.
Santiago Pericas-Geertsen wrote on
9/25/19 10:05 AM:
Hi All,
Now that Jakarta EE 8 is officially
out, we should revisit our existing roadmap. I updated it
with some tentative dates for the versions that we had
planned.
Please take look and provide feedback.
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
