| Re: [jaxrs-dev] Updating Roadmap to reflect Jakarta EE 9 Release Plans |
Thanks for your proposal. I would pref if we discuss first before changing the WIKI to not confuse readers. As the platform project is not our superior (only the spec committee and EE4J PMC are), and as the SE Bootstrap is backwards compatible (it is an *optional* feature), I do not see that we MUST shift SE Bootstrap to 3.1. As it is already existing since 1,5 years in Jersey, so our downstreams EE 9 platform and Eclipse GlassFish both have no efforts including it, and customers have no drawbacks. Hence I would vote for including it in 3.0 already unless either the spec committee or the EE4J PMC officially forbid that. Regarding the time frame, users expect to get things more early and more often. 3.0 (zero new features!) in Q2 and 3.1 (more or less one single feature) in ONE YEAR FROM OW is much too late, much too less. It is "one year lost" from the user's view angle. We have to commit to more in less time (again, it is not IBM, Oracle and Red Hat doing that committment and work, it is this project and *all* its committers, so there are more hands than possible seen when drafting the plan). My counterproposal is: Reverting your changes in the WIKI and then adjust *only* the version numbers. Hence, keep the original plan but just with a different name. What do others think? -Markus Von: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] Im Auftrag von Andy McCright Hi All, I updated the JAX-RS Roadmap page [1] to reflect the requirements of the Jakarta EE 9 release plan [2]. The main changes are: (1) Updating the major versions (i.e. from 2.2 to 3.0) - as I understand it, this is a hard requirement for EE 9. (2) Removing "additional content" from the 3.0 (previously 2.2) release. As I understand it, the EE9 release plan requires no changes to the EE 8 APIs other than the package rename (and pruning, where relevant). I interpret this as we will need to remove the SE bootstrap feature from the 3.0 release, so I put that into the 3.1 release. Please review these changes - feedback appreciated. Thanks, Andy |