| Re: [jakarta.ee-spec] [External] : Re: [BALLOT] Jakarta RESTful Web Services 3.1 |
Emily
This is a (mis) feature of our process -- The agreed process is to include TCK links in the PR conversation [1]. Once the ballot concludes, the final TCKs are copied (as is) to the location of these links. CDI included links to the proposed final TCK. Once the TCK is copied into the Spec. download, the links will presumably be updated so they point into the Specification normative download folder (currently, this link in the CDI 4 Preview, does not point to the proper final location). The TCK file SHA sum is used to verify that the exact TCK used for the ballot and the CCR, are one and the same.
[1] CDI Spec. PR -- look in the initial submitter checklist, about two thirds the way down.
On 4/5/2022 10:03 AM, Emily Jiang via jakarta.ee-spec wrote:
I found the link to tck jars are broken from here. Any reasons? CDI 4.0 has the workable links to tck jars etc.ThanksEmily
_______________________________________________+1 (Fujitsu)
-Kenji Kazumura
From: jakarta.ee-spec <jakarta.ee-spec-bounces@xxxxxxxxxxx> On Behalf Of Ivar Grimstad
Sent: Thursday, March 24, 2022 3:16 AM
To: Jakarta specification disccusions <jakarta.ee-spec@xxxxxxxxxxx>
Subject: [jakarta.ee-spec] [BALLOT] Jakarta RESTful Web Services 3.1
Greetings Jakarta EE Specification Committee,
I request your vote to approve and ratify the release of Jakarta RESTful Web Services 3.1 as part of the Jakarta EE Platform 10 release.
The JESP/EFSP requires a successful ballot of the Specification Committee in order to ratify the products of this release as a Final Specification (as that term is defined in the EFSP).
The relevant materials are available here:
- https://github.com/jakartaee/specifications/pull/430- https://deploy-preview-430--jakartaee-specifications.netlify.app/specifications/restful-ws/3.1/
Per the process, this will be a fourteen-day ballot, ending on Wednesday, April 6, 2022, that requires a Super-majority positive vote of the Specification Committee members (note that there is no veto). Community input is welcome, but only votes cast by Specification Committee Representatives will be counted.
The Specification Committee is composed of representatives of the Jakarta EE Working Group Member Companies (Fujitsu, IBM, Oracle, Payara, Tomitribe, Primeton, and Shandong Cvicse Middleware Co.), along with individuals who represent the EE4J PMC, Participant Members, and Committer Members.
Specification Committee representatives, your vote is hereby requested. Please respond with +1 (positive), 0 (abstain), or -1 (reject). Any feedback that you can provide to support your vote will be appreciated.
Please note that since this is a restart of the ballot for this specification, all members are requested to vote, even if you voted in the ballot that was discontinued.
Thanks,Ivar
--
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration.
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec
--
Thanks
Emily
_______________________________________________ jakarta.ee-spec mailing list jakarta.ee-spec@xxxxxxxxxxx To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec__;!!ACWV5N9M2RV99hQ!eZ74wASSelaPli8mGu--ZW9V2fogQZBz8OeNDIiUQUH8v2neaF5v9LRFpntdrZI$