Sorry to must have have overlooked that in all the many mails just like Red Hat ;-O I saw a reminder for Authorization 2.1 almost in parallel while I launched one for Authorization 3.0 myself, so if you sent one for this Ballot, I’m afraid it vanished in the „swamp“ of other emails or got caught by the spam filter. Werner Hi all,
I declare this ballot complete and approved. The summary of the votes is below.
The project team and Specification Committee may now engage to complete the release.
Congratulations! Representative | Representative for: | Vote | Kenji Kazumura | Fujitsu | +1 | Dan Bandera, Kevin Sutter | IBM | +1 | Ed Bratt, Dmitry Kornilov | Oracle | +1 | Andrew Pielage, Matt Gill | Payara | +1 | Scott Stark, Mark Little | Red Hat | No vote | David Blevins, Jean-Louis Monteiro | Tomitribe | +1 | Ivar Grimstad | EE4J PMC | +1 | Marcelo Ancelmo, Martijn Verburg | Participant Members | +1 | Werner Keil | Committer Members | No vote | Dr. Jun Qian | Enterprise Members | +1 | | Total | 8 |
I am preparing to close the ballot, and while counting the votes I cannot find the votes from Committer Members and Red Hat. I apologize if I missed those emails. I will close the ballot soon, so if you have cast your vote, please indicate it in this thread so I can find the email and properly count it | | | | ![]() 联系我
|
| | |
------------------ Original ------------------ Date: Wed, Jun 2, 2021 03:07 PM Subject: Re: [jakarta.ee-spec] BALLOT: Plan Review for Jakarta Servlet 6.0 +1 PMC We should remove the links to empty artifacts on the 6.0.0 page after the PR has been merged, but that is a minor cosmetic issue Forgot to add BALLOT to the subject Greetings Jakarta EE Specification Committee. I need your vote to approve the Plan Review of Jakarta Servlet 6.0 The JESP/EFSP states a Plan Review provides a means for the Specification Project Team to present their Release Plan to the Project Leadership Chain, the Specification Committee, and the community for feedback. Also, the JESP/EFSP requires a successful ballot of the Specification Committee in order to ratify the Plan Review. The relevant materials are available here: Per the process, this will be a seven-day ballot, ending on Monday, Jun 7th , 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 Committee 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.
_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec
-- 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 |
