Re: [jakarta.ee-spec] BALLOT: Approval to release Jakarta Deployment 1.7
+1 from Tomitribe with the explicit note these staged API binaries were deleted due to 30-day expiration and will need to be recreated or the backups I made redeployed.
> On Aug 14, 2019, at 11:43 AM, Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> Greetings Jakarta EE Specification Committee.
> I need your vote to approve the service release of the Jakarta Deployment 1.7 as part of the Jakarta Stable APIs project's 1.0.1 release. By way of background, the project engaged in a successful release review for their 1.0 release.
> The JESP/EFSP requires a successful ballot of the Specification Committee in order to ratify and make this service release final. No release review (or formal ceremony beyond a successful ballot result from the Specification Committee) is required for a service release.
> The relevant materials are available here:
> Per the process, this will be a fourteen day ballot, ending on August 28/2019. I require a Super-majority positive vote of the Specification Committee members. 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), 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.
> jakarta.ee-spec mailing list
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit