| Re: [jaxrs-dev] [discuss] Releasing JAX-RS API 2.2 |
It was approved by the PMC on Wednesday. There seems to be an issue regarding license headers. Not sure who is responsible for fixing that, or if the project team can do it. Currently, most of the EF staff is in transit on their way to Ludwigsburg, so we'll probably know when they land...IvarOn Sat, Oct 19, 2019 at 4:57 PM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:_______________________________________________No problem with that as long as it happens before end of the year.
Von: Christian Kaltepoth
Gesendet: Samstag, 19. Oktober 2019 16:20
An: jaxrs developer discussions
Betreff: Re: [jaxrs-dev] [discuss] Releasing JAX-RS API 2.2
Hi Markus,
I definitely share your frustration regarding the lack of progress. And I also would like to see 2.2 released as soon as possible.
However, in my eyes the 2.1 release was already some kind of pseudo-release as it only contained a placeholder specification document without any content. And I don't think that our first feature release should also be a pseudo-release without a spec document. I'm not even sure if the spec committee would approve such a release.
So my vote goes for cleaning up the spec document which we will get in a few days (there is already a CQ for it and AFAIK we are just waiting for the PMC approval) and release 2.2 with the current feature set AND the specification document.
Christian
Am Sa., 19. Okt. 2019 um 14:41 Uhr schrieb Markus KARG <markus@xxxxxxxxxxxxxxx>:
While preparing my presentation for EclipseCon I noticed that I will give the n-th presentation of the exactly same JAX-RS preview meanwhile. Now that Jakarta EE 8 is published, it would be good if at least I could tell the audience that this is the last show basing on a preview only.
Looking at the Milestones tracker in Github it seems that all changes we explicitly planned for JAX-RS 2.2 are actually implemented meanwhile.
Looking at the recent discussions we had, it seems NONE of the discussed issues is a REAL showstopper for 2.2, as all of those points had been declared as „To be decided by the JAX-RS committers“. Hence I would vote for immediately releasing of 2.2 „as-is“, and adopt those „side issues“ (like spec PDF, TCK split, etc.) in 2.3 or 3.0 once these actually become are available.
So the question to discuss is: Shall we release immediately to make the way free for 2.3 and 3.0, or are there issues that actually MUST be resolved before 2.2?
-Markus
_______________________________________________
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
--
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
--_______________________________________________Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation, Inc.
Eclipse Foundation: The Platform for Open Innovation and Collaboration
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