Re: [jakarta.ee-spec] BALLOT: Approval to release Jakarta Tags 2.0

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Good comments, Jean-Louis.
 My two cents worth...

• Wondering if the use of javax.el.ValueExpression is just a docs issue or if it's an actual type issue on the attribute?  Arjan or Paul?
  
• I agree that the TCK Release Notes is not in good shape.  But, this could be corrected in a TCK update release (2.0.x).

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Jean-Louis
Monteiro <jlmonteiro@xxxxxxxxxxxxx>
To:
       Jakarta
specification discussions <jakarta.ee-spec@xxxxxxxxxxx>
Date:
       10/26/2020
09:24
Subject:
       [EXTERNAL]
Re: [jakarta.ee-spec] BALLOT: Approval to release Jakarta Tags 2.0
Sent
by:        jakarta.ee-spec-bounces@xxxxxxxxxxx

---

On the specification PR itself ...

There is a javax.el.ValueExpression in
ForEach tagdocs.

On the TCK zip ...

The TCK release notes are still referencing
version 1.2 instead of 2.0.
I think it should maybe also use Glassfish
6.0 instead of 5.1
The date is september 2019

Index also refers to 1.2 instead of 2.0

I'll check with David what we want to do
as Tomitribe.
Please don't update the PR quick yet

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Oct 23, 2020 at 4:06 PM Scott
Stark <starksm64@xxxxxxxxx>
wrote:
+1 Red Hat

On Wed, Oct 21, 2020 at 10:43 AM Werner
Keil <werner.keil@xxxxxxx>
wrote:

Greetings Jakarta EE Specification Committee.

I need your vote to approve and ratify the release of Jakarta Tags 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/277
https://deploy-preview-277--jakartaee-specifications.netlify.app/specifications/tags/2.0/

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

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
…

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

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