Re: [jakartaee-platform-dev] [ejb-dev] [External] : Please give your est

[David Blevins <dblevins@xxxxxxxxxxxxx>]

> On Mar 19, 2021, at 9:03 AM, Lukas Jungmann <lukas.jungmann@xxxxxxxxxx> wrote:
> 
> On 3/19/21, 4:43 PM, "David Blevins" <dblevins@xxxxxxxxxxxxx> wrote:
> 
>> On Mar 19, 2021, at 8:39 AM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
>> 
>> If we're releasing a new spec, we should release a new TCK so the versions match.
> 
> We are releasing a new _Platform_  spec, not new Activation, Mail, etc... specs, JAF and Mail service releases were able to pass existing 9.0 standalone TCKs on both - JDK 8 as well as JDK 11.
> Given that NO API changes were allowed in included specs, I'd expect that the new 9.1 platform release implementation should pass even the 9.0 platform TCK release `as is` at least on JDK 8 (I don't recall if JDK 8 is a "must" right now but I think you get the point). Don't take me wrong, I understand the need for the new Platform TCK release. It's just about that the Platform itself advertised that nothing should be changed at the components/included specs level.

I'm a little confused.  There will be new tests and other changes for the 9.1 TCK, so the TCKs won't be the same and someone would not be able to use the 9.0 TCK to claim compatibility with 9.1.

We do need to prove that the 9.1 TCK can be passed on JDK 8 and there's no way to cut that corner.  That said, we still probably can use GlassFish 6 to pass the 9.1 TCK on JDK 8 so there shouldn't be extra work.

Scott Marlow, are we running the 9.1 TCK on JDK 8 in addition to 11 and are we factoring passing both into our timelines?

>    That said, the signature files will likely have changed because we added signature test files for each API on Java 11.
> 
> Some standalone TCKs already included signature tests for Java 11 in 9.0 release.

For any standalone TCKs that have new signature files, we'd at least need a service release of each.


-David