| My reading of everyone's will seems to indicate that focusing on the CTS 8.01 and delaying runs of JSONB 1.0.1 is ok.
The precedent I see is in discussions on certification requests, it was predominately indicated certification requests for the full CTS and a standalone TCK could happen independently of each other. One did not block the other, they could come in any order, and one could fail despite the other succeeding.
We have been applying that in practice to the standalone TCKs, releasing them independently from the full CTS. So, It appears we could release the CTS 8.01 before JSONB 1.0.1.
Others may have other thoughts, but this is my best-effort read of the room.
We are struggling
to get the overall CTS 8.0.1 tested in time for the Certification Requests.
Since we have not run the standalone JSON-B TCK in the past, I have
no idea how involved that is and I can't commit to running that bucket.
But, we are running the Full Platform and (hopefully) the Web Profile
TCKs...
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutterFrom:
David
Blevins <dblevins@xxxxxxxxxxxxx>To:
jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>Cc:
jakarta.ee-spec.committee@xxxxxxxxxxxDate:
09/05/2019
05:45 PMSubject:
[EXTERNAL]
Re: [jakartaee-platform-dev] CTS 8.0.1 and JSONB TCK 1.0.1Sent
by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
We don't have an established protocol
for handling updates like this. I propose the following as a bare
minimum: - JSONB 1.0.1: We get TCK verifications
from *both* GlassFish 5.1 and OpenLiberty in the form of JSONB certification
requests against the new sha256. We then publish immediately. I
published the 1.0.0 TCK moments ago, so I'm happy to do that. - CTS 8.0.1: We get TCK verifications
from *both* GlassFish 5.1 and OpenLiberty in the form of Full and Web Profile
certification requests against the new sha256. We hold the binaries,
add this additional TCK link and certification requests to the Web and
Full PRs. We publish all TCKs when the votes complete.
-- David Blevinshttp://twitter.com/dblevins
http://www.tomitribe.comOn Sep 5, 2019, at 3:34 PM, Gurunandan
Rao <gurunandan.rao@xxxxxxxxxx>
wrote:Hi all,
We have updated CTS, to exclude JSONB tests accepted in TCK challenge described
inhttps://github.com/eclipse-ee4j/jsonb-api/issues/180
Also we have created new bundle for JSONB TCK with excluded tests. Please
refer the below download location for the new bundles.
1. EFTL :
CTS 8.0.1 - http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/staged-801/eclipse-jakartaeetck-8.0.1.zip
JSONB TCK 1.0.1 - http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/staged-801/eclipse-jsonb-tck-1.0.1.zip
2. EPL :
CTS 8.0.1 - http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8/nightly-801/jakartaeetck-8.0.1.zip
JSONB TCK 1.0.1 - http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8/nightly-801/jsonb-tck-1.0.1.zip
regards,
Guru
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________ jakartaee-platform-dev mailing list jakartaee-platform-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
|
