[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cu-dev] Component spec review deadline and when to create 3.1 RC1 and staging of final
|
Hello Nathan,
Concurro is heading towards implementation of 3.1. We started to
execute the TCK in Payara, currently with result:
Tests run: 242, Failures: 5, Errors: 4, Skipped: 24
With Ondro, we did the Flow support today (PR in Concurro). Some
fixes were done in TCK itself, there is definitely one more error
in testSignature.
The work will continue, so I think that Concurro+Payara can serve
as the compatible implementation on Java 21. It will at least test
the TCK. I also plan to add the required parts to Glassfish.
Regarding SignatureTests -- are we going to work on it? I am
convinced, that we discussed its removal, but there were some
changes, so it looks like we are going to adapt it to Java 21?
Petr
On 3/11/24 9:45 PM, Nathan Rauh via
cu-dev wrote:
As a Jakarta EE 11 specification in wave 6,
Jakarta Concurrency 3.1’s deadline for component specification
release review is April 27, 2024. It might sound like is it
still a ways off, but it requires our specification to publish
fully passing TCK results on Java 21 and 17 from a compatible
implementation alpha, beta, or GA release with publicly
available download, after having pushed a candidate final copy
of the specification to staging that can be published upon
successful review.
We need to come up with plans for what our
compatible implementation is expected to be and line it up
with these dates.
In order for Open Liberty to be a
compatible implementation for certification of Jakarta
Concurrency 3.1, our release process would require a 3.1 RC1
to be created by March 20th, after which the API,
specification requirements (and preferably TCK) must not
change. This would allow for the creation of a downloadable
beta release that will become available in time to officially
pass the TCK and post results by the component specification
deadline.
Are there any other implementations that
could be candidates to use for certification of 3.1?
I noticed there has been a lot of work in
the Concurro implementation. Someone who is working on it
would need to let us know how it lines up with the wave 6
component spec release review deadline.
_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev
