Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] [BALLOT] Plan Review for Jakarta WebSocket 2.1

+1 PMC

On Mon, May 3, 2021 at 2:36 PM kzr@xxxxxxxxxxx <kzr@xxxxxxxxxxx> wrote:
+1 (Fujitsu)

-Kenji Kazumura

> -----Original Message-----
> From: <> On Behalf Of kzr@xxxxxxxxxxx
> Sent: Monday, May 3, 2021 9:34 PM
> To: '' <>
> Subject: [] [BALLOT] Plan Review for Jakarta WebSocket 2.1
> Greetings Jakarta EE Specification Committee.
> I need your vote to approve the Plan Review of Jakarta WebSocket 2.1.
> 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, May 10, 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
> -Kenji Kazumura
> _______________________________________________
> mailing list
> To unsubscribe from this list, visit
_______________________________________________ mailing list
To unsubscribe from this list, visit


Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 

Back to the top