|Re: [jakarta.ee-spec] BALLOT: Approval to release Jakarta Tags 2.0|
Ok you only mean the TCK release notes, as Kevin said, it’s probably best to do this in an update release instead of doing it all over again.
In fact, our checklist may have to be phrased differently, because it points out a TCK User's Guide (or equivalent documentation) but says nothing about other documents like the release notes or those Assertion Folders which look like they also contain TCK results.
I think that Paragraph should be a Little more generic and refer to TCK documents or similar and especially if those assertions are a mandatory part of each TCK Archive, they should explicitly be mentioned in the checklist.
Good comments, Jean-Louis. My two cents worth...
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:
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.
Back to the top