Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] [Ballot] - Denoting which implementation was used to ratify a specification

I vote for Option 3. At the time of ballot the compatible implementation used to pass the TCK can be a release candidate (fixed in time). Instead of the release link, it can point to the CCR.

 

When a final version is released it can be added under compatible implementation.

 

Honestly, Option 2 is hard to find. After scrolling the page twice I noticed the CCR link.

 

Thanks

Hussain

 

From: jakarta.ee-spec <jakarta.ee-spec-bounces@xxxxxxxxxxx> On Behalf Of David Blevins
Sent: Wednesday, March 24, 2021 1:21 AM
To: Jakarta specification discussions <jakarta.ee-spec@xxxxxxxxxxx>
Subject: Re: [jakarta.ee-spec] [Ballot] - Denoting which implementation was used to ratify a specification

 

[External]

Quick community note based on offline feedback I got.  Yes, everyone can vote.  Like our release votes only the Spec Committee member votes are binding, but hearing from everyone is encouraged and welcome.

 

If you have thoughts, go ahead and vote!

On Mar 22, 2021, at 11:00 AM, Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx> wrote:

 


The Specification Committee has discussed the proposal to demote on a specification page which open source implementation was used during ratification of the specification during a Release Review. There have been robust discussions on the mailing list and in meetings. Four options emerged which I have listed below. They have been mocked up by Ivar, see the PRs. Option 4 has no PR since it is the "do nothing" choice.  Options:

1.     Place an asterisk beside implementation in the list of Compatible Implementations (https://deploy-preview-338--jakartaee-specifications.netlify.app/specifications/jsonp/2.0/)

2.     Provide a link to the Compatibility Certification Requests used for the Ballot at the bottom of the page (https://deploy-preview-337--jakartaee-specifications.netlify.app/specifications/jsonp/2.0/)

3.     Include the compatible implementation in the list of  release artifacts at the top of the spec page (https://deploy-preview-329--jakartaee-specifications.netlify.app/specifications/jsonp/2.0/)

4.     Do nothing, as is, no denotation (https://jakarta.ee/specifications/jsonp/2.0/)

Specification Committee members, please respond with your choice: 1, 2, 3, or 4.

 

Thanks ... Paul

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

 

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.

Back to the top