Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakarta.ee-spec.committee] Ballots between now and Jakarta EE 8

After today's Steering Committee call, I thought that it might be helpful to provide a list of all the votes that will occur between now and the successful release of Jakarta EE 8.

Does anybody object to me adding those votes that have a (reasonably) well-defined start/end date to the calendar?

EFSP 1.2: I called for this vote on Sunday. Per the process defined for creating new versions of the EFSP, I require a simple majority vote of the specification committee. The process does not define a specific time period, so I'm leaving this vote open for a week.

JESP 1.2: I will deliver a proposed update to the JESP to the Specification Committee tomorrow for discussion. Per the JESP 1.1, a vote to update the JESP requires one week. I will call for this vote when discussion around the update reaches consensus.

Restructuring Review, Round 3: I will start this ballot with my next email to the Specification Committee. Per the JESP (and EFSP), seven days is required for this ballot, and I require Super-majority approval. The restructuring review is scheduled to conclude on July 3 (so the ballot will conclude before the end of the review period). I will make the described changes immediately after the conclusion of the review.

Jakarta Contexts and Dependency Injection: A proposal for this project has been created, but the team has not taken the next step of contacting EMO to turn the draft into a community review. I have reached out to the proposed project lead to ask for status. Following their request to make the proposal public, the process requires a minimum of two weeks of community review. I'll call for a ballot as soon as we post the proposal, and fast track the creation (inasmuch as the process allows).

Jakarta Bean Validation: This proposal is in community review. We're waiting on the project team to engage with us to sort out the alternative licensing scheme that they've requested (Apache-2.0). I've poked the project team to see if can make progress by the end of the week. I don't believe that we need to wait for that to resolve before calling for a Specification Committee ballot, so I'll initiate that as soon as possible. We're also waiting on a mentor for this project, so if any of you Architecture Council members are able to step up, that would be great.

Release Review: The schedule has the ballot for the Jakarta EE 8 Release Review starting on July 22/2019. Per the JESP 1.1, the Specification Committee will have thirty days for this ballot. I'm inclined to pack all of them together into a single (or small batches) ballot like we've done with the Restructuring Reviews. I can push them out individually if committee members prefer.

Wayne
--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.


Back to the top