I don’t know the answer, but to be safe, let’s not make any changes to the API jar (Do we even need to rebuild the API jar at all?) As far as I am aware, all of the TCK challenges should be addressed by updating the TCK tests rather than
the API. Even in the case of the one controversial TCK challenge, it either gets left as is if the challenge didn’t succeed or if the challenge did succeed then the proper update is to the TCK test: either to disable it or disable the portions of it that
relied on the challenged assertion, in either case with the opportunity in Concurrency 3.1 to more fully clarify the specification requirement and add tests back in asserting the behavior at that time.
From:
cu-dev <cu-dev-bounces@xxxxxxxxxxx> on behalf of Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx>
Date: Monday, June 20, 2022 at 3:44 AM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [cu-dev] Service Release
I have merged outstanding PRs. We still have this PR for the TCK which is more controversial. I also need to understand what you can and can’t do on the api and
TCK on a service release. Anyone know?
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
I have merged outstanding PRs. We still have this PR for the TCK which is more controversial.
I also need to understand what you can and can’t do on the api and TCK on a service release. Anyone know?
Steve
From: cu-dev <cu-dev-bounces@xxxxxxxxxxx>
On Behalf Of Nathan Rauh
Sent: 17 June 2022 14:26
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: Re: [cu-dev] Service Release
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.
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