Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] [BALLOT] Release Review for Jakarta Annotations 2.1

+1, EE4J PMC

On Mon, Jan 31, 2022 at 10:56 AM Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx> wrote:


On Mon, Jan 31, 2022 at 10:54 AM kzr@xxxxxxxxxxx <kzr@xxxxxxxxxxx> wrote:

Ivar,

 

Thanks for information.

I understand you are talking about https://github.com/jakartaee/specifications/pull/329 .


Yes, that is correct!
Ivar 

 

-Kenji Kazumura

 

 

From: jakarta.ee-spec <jakarta.ee-spec-bounces@xxxxxxxxxxx> On Behalf Of Ivar Grimstad
Sent: Monday, January 31, 2022 5:09 PM
To: Jakarta specification discussions <jakarta.ee-spec@xxxxxxxxxxx>
Subject: Re: [jakarta.ee-spec] [BALLOT] Release Review for Jakarta Annotations 2.1

 

Hi Kenji,

 

That is the compromise the spec committee decided on following the discussion around JSON-P last year. This is what we came up with: https://jakarta.ee/specifications/jsonp/2.0/

 

Ivar

 

On Mon, Jan 31, 2022 at 2:59 AM kzr@xxxxxxxxxxx <kzr@xxxxxxxxxxx> wrote:

Ivar,

 

> - https://deploy-preview-437--jakartaee-specifications.netlify.app/specifications/annotations/2.1/

 

Do we need the following item in the specification page ?

 

I don’t remember if we decided to add this kind of information to index.md.

 

-Kenji Kazumura

 

 

 

From: jakarta.ee-spec <jakarta.ee-spec-bounces@xxxxxxxxxxx> On Behalf Of Ivar Grimstad
Sent: Thursday, January 27, 2022 3:38 AM
To: Jakarta specification disccusions <jakarta.ee-spec@xxxxxxxxxxx>
Subject: [jakarta.ee-spec] [BALLOT] Release Review for Jakarta Annotations 2.1

 

Greetings Jakarta EE Specification Committee.

I need your vote to approve and ratify the release of Jakarta Annotations 2.1 as part of the Jakarta EE Platform 10 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/437

https://deploy-preview-437--jakartaee-specifications.netlify.app/specifications/annotations/2.1/

Per the process, this will be a fourteen-day ballot, ending on Wednesday, February 9, 2022, 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.

The Specification Committee is composed of representatives of the Jakarta EE Working Group Member Companies (Fujitsu, IBM, Oracle, Payara, Tomitribe, Primeton, and Shandong Cvicse Middleware Co.), 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

 

Ivar

 

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation 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


 

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation 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


--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 



--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 


Back to the top