This seems like a good idea if it will help other implementations pass the TCK by picking up the necessary TCK updates to resolve the various challenges
https://github.com/jakartaee/concurrency/issues?q=is%3Aissue+is%3Aopen+label%3Achallenge I think the pulls for these still need to be merged, so make sure to do that before creating the service release.
From:
cu-dev <cu-dev-bounces@xxxxxxxxxxx> on behalf of Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx>
Date: Friday, June 17, 2022 at 4:54 AM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] [cu-dev] Service Release
All, Before the final platform release do we want to create a service release for TCK and API jar to fix various issues e.g. Execute unit tests in the build and
fix scope for test dependencies by pzygielo · Pull Request #216 ·
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
All,
Before the final platform release do we want to create a service release for TCK and API jar to fix various issues e.g.
Execute unit tests in the build and fix scope for test dependencies by pzygielo · Pull Request #216 · jakartaee/concurrency · GitHub . I am not familiar with the service release process but I’ve seen other specs doing them quite quickly.
I don’t think a service release impacts the ballot.
Steve Millidge