Hi, Based on the discussion
and the +1/-1 voting, it sounds like the majority of the team is interested
in prioritizing Java SE 8 over Java SE 11. My count indicates 12
in favor of prioritizing Java SE 8, with only 2 indicating a preference
for Java SE 11 prioritization. I plan to voice this re-direction
to the Steering Committee tomorrow. Thanks for all of the input!
A few of you reached out to me asking me which was I was leaning. I
didn't want to sway anyone's opinion or vote, so I stayed neutral until
those people voiced their opinion on the mailing list. Then, I told
them that I was favoring the Java SE 8 prioritization. So, the 12
votes for Java SE 8 includes mine.) --------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect @ IBM e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
Thomas <markt@xxxxxxxxxx> To:
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>,
David Blevins <dblevins@xxxxxxxxxxxxx> Cc:
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx> Date:
Re: [jakartaee-platform-dev] [jakartaee-spec-project-leads] Java 8 vs Java
11 Compatibility requirements Sent
I too would prefer the priority to be Java 8.
Experience with Apache Tomcat (I've been testing Tomcat 10.0.x against local builds of the EL, JSP, WebSocket and Servlet TCKs with Java 8 and Java 11) suggests that Java 11 issues are more likely to be with the TCK than the implementation.
Those four particular TCKs should be ready for both Java 8 and Java 11 but they are, or course, only a subset.
On 09/07/2020 19:03, David Blevins wrote: > My preference would be option #2 with our TCK effort focused primarily > on JDK 8 with occasional Java 11 runs. We may get lucky and
pass both, > but let's focus on 8 for now. > >> On Jul 8, 2020, at 8:47 PM, reza_rahman <reza_rahman@xxxxxxxxx >> <mailto:reza_rahman@xxxxxxxxx>>
wrote: >> >> In my opinion, a more rapid release cadence than Java EE is a
key >> objective for Jakarta EE. I also agree that most people are still
on >> Java SE 8. It would actually be even more impressive to have a
Jakarta >> EE 9.1 release that features Java SE 11 support. > > Agree with Reza and Dmitry. > > As Kevin notes later, we could potentially see Compatible > Implementations pass the TCK using Java 11 with no issues. If
we do end > up having to address issues in the TCK that prevent Java 11 runs and > there are any significant changes, we should consider a 9.1 release
as > it could be a great way to show progress. > > > -David > > > _______________________________________________ > jakartaee-spec-project-leads mailing list > jakartaee-spec-project-leads@xxxxxxxxxxx > To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads >