Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] BALLOT: Approval to adopt the Jakarta EE Specification Process 1.2

+1  approve] BALLOT: Approval to adopt the Jakarta EE Specification Process 1.2

Greetings Jakarta EE Specification Committee.

I need your vote to approve the adoption of the Jakarta EE Specification Process (JESP) 1.2. This new version is based on the recently approved Eclipse Foundation Specification Process(EFSP) 1.2, and include changes discussed in Specification Committee meetings (and captured in the minutes). A diff of the changes is availableÂhere. I have attached a copy of the generated HTML.

Per the process, this will be a seven day ballot, ending on July 15/2019. I require a Super-majority positive vote of the Specification Committee members. Comments are, of course, welcome, but changes will not be entertained during this ballot period. Community input is also 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), 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.




Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Title: Jakarta EE Specification Process
Jakarta EE Specification Process
version 1.2. Effective July 16/2019
The Jakarta EE Specification Process (JESP) is concerned with the Specification Process as it applies to Specification Projects operating under the purview of the Jakarta EE Working Group.
The Jakarta EE Specification Committee hereby adopts the Eclipse Foundation Specification Process v1.2(EFSP) as the Jakarta EE Specification Process with the following modifications:
  1. Any modification to or revision of this Jakarta EE Specification Process, including the adoption of a new version of the EFSP, must be approved by a Super-majority of the Specification Committee, including a Super-majority of the Strategic Members of the Jakarta EE Working Group, in addition to any other ballot requirements set forth in the EFSP.
  2. All specification committee approval ballot periods will have the minimum duration as outlined below (notwithstanding the exception process defined by the EFSP, these periods may not be shortened)
    1. Creation Review: 7 calendar days;
    2. Plan Review: 7 calendar days;
    3. Progress Review: 14 calendar days;
    4. Release Review: 14 calendar days;
    5. Service Release Review: 14 calendar days; and
    6. JESP Update: 7 calendar days.
  3. A ballot will be declared invalid and concluded immediately in the event that the Specifiation Team withdraws from the corresponding review.
  4. Specification Projects must engage in at least one Progress or Release Review per year while in active development.
All development that modifies content in the javaxnamespace must be moved to a jakartanamespace. All jakartanamespace development must occur within the scope of a Specification Project operating under the purview of the Jakarta EE Working Groupâs Specification Committee and must implement the process as defined by the most recently adopted revision of the JESP.
The EFSP takes precedence in cases where this document is silent. The primacy of the EFSP notwithstanding, this document takes precedence in all matters related to Specification development undertaken by Specification Projects within the purview of the Jakarta EE Working Group.
Last updated 2019-07-03 23:10:51 EDT

Best regards,

Dan Bandera
(512) 286-5228
Program Director, Blockchain, Istio, Java technologies, Node.js
IBM Open Technologies, Austin, Texas
The OSGi Alliance ( ) President and Board of Directors

Back to the top