Re: [jakartaee-platform-dev] [EXTERNAL] Re: Release plan revisions to mi

[Ed Burns <Edward.Burns@xxxxxxxxxxxxx>]

Mark Thomas wrote:

MT> This is a HUGE change. It effectively means that the minimum Java runtime required to be supported has changed from Java 21 to Java 17. 
MT> It is way too late in the process for such a change.

MT> And if the argument is that the minimum runtime version requirement hasn't changed, 
MT> what is the point in requiring anything to work with Java 17 if the minimum runtime is Java 21?

Before assigning a magnitude to the item being labeled as a change, I want to make sure the plan is understood.  I will state our approach to implementing the plan for EE 11 and then we can overlay the language of the plan on it.

Implementation:

GlassFish 8 is slated to be the Ratifying Compatible Implementation for EE 11. It is slated to achieve this by compiling under 17 and passing the platform TCK under a 17 JVM and also passing it under a 21 JVM.

Language:

EB> To ratify a platform specification, there must exist an
EB>             implementation that passes on 17. There must also exist an
EB>             implementation that passes on 21.

In this implementation, GlassFish satisfies the "must exist" requirement. That's it. That's EE 11 done.

Now, vendors can claim to be compliant by passing the 17 compiled TCK under a 17 JVM or a 21 JVM.

If the above text did not alter your understanding, you can resaonably assgn a magnitude.

I have been assured by trusted experts that what we are doing in EE 11 (with 17 and 21) is semantically equivalent to what we did in in EE10 (with 11 and 17).

However, as release co-coordinator, I take responsibility for this plan.

Ed



| edburns@xxxxxxxxxxxxx | office: +1 954 727 1095
| Calendar Booking: https://aka.ms/meetedburns
| 
| Please don't feel obliged to read or reply to this e-mail outside
| of your normal working hours.
|
| Reply anonymously to this email: https://purl.oclc.org/NET/edburns/contact