Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] BALLOT: Approval to release Jakarta Interceptors 2.0
+1 (Tomitribe)

But with some comments and fixes for future maintenance

- apidoc has a reference to jakarta.xml.rpc.handler.MessageContext. Isn't it supposed to be javax.... ?

- the TCK zip link in PR should be the same (promoted versus staged, and RC1, versus 9.0.0 final) as the CSR and TCK result page.
I tested the SHA and they are all identical. So really just a minor thing for next time.

- the date in the index is probably a bit too far in the past. Can be fixed with the ballot result PR

- spec html and pdf should have jakarta- prefix next time. Not required for this release.

- the TCK results are for Glassfish RC2. The CSR is referencing glassfish 6.0.0 final, so is the spec PR mentioning as part of the compatible implementation section.




On Fri, Nov 6, 2020 at 7:41 AM Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx> wrote:
+1 (PMC)

On Wed, Nov 4, 2020 at 1:57 AM kzr@xxxxxxxxxxx <kzr@xxxxxxxxxxx> wrote:
Greetings Jakarta EE Specification Committee.

I need your vote to approve and ratify the release of Jakarta Interceptors 2.0 as part of the Jakarta EE Platform 9 release.

The JESP/EFSP requires a successful ballot of the Specification Committee in order to ratify the products of this release as a Final Specification (as that term is defined in the EFSP).

The relevant materials are available here:

https://github.com/jakartaee/specifications/pull/233
https://deploy-preview-233--jakartaee-specifications.netlify.app/

Per the process, this will be a fourteen-day ballot, ending on Tuesday November 16, 2020 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.

NOTE: this ballot depends on the Platform ballot and won't close until the platform ballot closes itself successfully.

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

_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec


--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Eclipse Foundation - Community. Code. Collaboration. 

_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec

Back to the top