Sorry, forgot the LINK to the roadmap: https://github.com/eclipse-ee4j/jaxrs-api/wiki/Roadmap
-Markus
From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Markus KARG
Sent: Samstag, 28. Juli 2018 11:59
To: 'jaxrs developer discussions'
Subject: Re: [jaxrs-dev] [Discuss] Initial Roadmap / Preliminary Release Schedule
Committers,
thanks for sharing your ideas!
I have tried to add most of it into an updated preliminary schedule:
LINK
Please be so kind and check this new plan. It now contains more releases in the same time frame so I could add more of your requested features. Now before we can vote on it, we need another round of feedback. In particular, the following questions arise:
- From a purely formal standpoint, can we do JPMS and Java 9 in a minor version increase or does that enforce a major version increase?
- Do we really only want Java 9 in 2019, or shall we directly jump on Java 11 in half a year from now?
Thanks for your feedback!
-Markus
From: Markus KARG [mailto:markus@xxxxxxxxxxxxxxx]
Sent: Samstag, 21. Juli 2018 14:35
To: 'jaxrs developer discussions'
Subject: RE: [jaxrs-dev] [Discuss] Initial Roadmap / Preliminary Release Schedule
Guillermo,
yes, if we remove something in 3.0 then we MUST deprecate it in 2.2 or 2.1.1. But this has to be voted.
IIRC we have not yet voted about any particular content of neither 3.0 nor 2.2 nor 2.1.1, so I just picked what I understood to be common sense of the various discussions so far.
Feel free to open an issue wrt deprecating @Context and set the linked milestone to 3, which effectively opens the possibility for reviewing and voting.
-Markus
Hi Markus,
Thanks for getting it written.
Does 3.0 imply *removing* @Context and other related stuff. If so, those features should be deprecated in a previous version to give users a chance to migrate.