|Re: [jakartaee-platform-dev] Transitioning Jakarta EE to the jakarta namespace
On 2019-05-07 3:18 p.m., Alasdair Nottingham wrote:
I think those dates are for the specs, I suspect that the implementations will take longer to adapt to the change and this will have knock-on implications for the availability of the next spec release.
Alasdair,Although generally true, your statement is likely not correct for the specific case of a "...release of Jakarta EE that is identical to Java EE 8...".
Since (a) it is identical to Java EE 8, so the certification costs are nearly zero, and (b) the more open licensing model of Jakarta will save the vendors significant (e.g. millions of dollars) licensing costs relative to Java EE 8, I predict that such a release would see blindingly fast adoption by vendor implementations.
On May 7, 2019, at 8:10 PM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote: There's naturally an "I want to go as fast as possible" theme in many of the response. This is good. There's also a naturally a tendency to view version numbers as dates. This is not accurate. Putting more in a release doesn't make it come sooner. Using no version numbers whatsoever, here are the most likely potential release windows based on effort: - Any release of Jakarta EE that is identical to Java EE 8. Achievable this summer or early fall. Low risk. - Any release of Jakarta EE that contains any form of namespace change. Achievable late fall to winter. Medium risk. - Any release of Jakarta EE that contains any new features or pruning. Achievable mid to late next year. High risk. Others can chime in, but I don't believe the rough framing of these dates is way off.
Back to the top