| Re: [jakarta.ee-spec] BALLOT: Approval to release Jakarta Security 2.0 |
|
+1 (Payara)
As pointed out by Kevin, the compatible implementation of 2.0.0-RC1 mentioned in the _index.md doesn't exist but is currently in the process of being fixed to point at M3 which is what was actually used.
Thanks,
Andrew Pielage
Java Developer at Payara Services Ltd
Open Source Enterprise Software & Support From: jakarta.ee-spec-bounces@xxxxxxxxxxx <jakarta.ee-spec-bounces@xxxxxxxxxxx> on behalf of Scott Stark <starksm64@xxxxxxxxx>
Sent: 08 October 2020 00:35 To: Jakarta specification disccusions <jakarta.ee-spec@xxxxxxxxxxx> Subject: [jakarta.ee-spec] BALLOT: Approval to release Jakarta Security 2.0 Greetings Jakarta EE Specification Committee. I need your vote to approve and ratify the release of Jakarta Security as part of the Jakarta EE Platform 9 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/263 Per the process, this will be a fourteen-day ballot, ending on Wednesday October 21, 2020 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, Red Hat, Tomitribe, and Primeton), 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. Thanks … |