Re: [jakarta.ee-spec] [Ballot] Optional Features Resolution
+1 Red Hat.
The use cases for optional behavior at the spec levels can be dealt with by breaking up specs. At the platform level this just introduces non-portable behavior that serves no purpose.
Thanks to all that have cast their ballot. Votes appear to be missing from:
Participant Member (Marcelo)
Committer Member (Werner)
The ballot concludes today.
Thanks ... Paul
Greetings Jakarta EE Specification Committee,
I need your vote to approve the following resolution:
RESOLUTION: The Jakarta EE Specification Committee resolves that no new optional features may be added in Jakarta EE 10 and beyond in component, Platform, or Profile specifications.
This is a seven day ballot, ending on Wednesday, August 4th. 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
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
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec