As discussed in today's meeting, no, I don't agree with this.
We need a full TCK run of a compatible implementation in order to
approve a spec. I understand that the timing is tight and some of
them might not be ready by Monday, or even the following Monday when
the real review is scheduled to start. We do have some extra time
in the schedule once JESP 1.2 is approved so that should allow more
than enough time for projects to complete a full TCK run.
If anyone is having trouble getting the TCKs to work, please ask for
help sooner rather than later.
Kevin Sutter wrote on 7/10/19 7:06 AM:
Hi,
All of the
individual
Jakarta EE Spec Projects need to create their skeletal spec
documents and
provide their TCK results for the updated APIs. I've had the
question
raised about how much of the TCK needs to be executed against
these updated
APIs. My response has been only the TCKs that actually verify
the
APIs -- not the full implementation. In most cases, this would
equate
to running the signature tests (although some components have
more elaborate
"APIs" that need further testing). I have also been advocating
that if this simplified TCK can be run without requiring an
application
server -- all the better!
Are we all on
the same page with this direction? Thanks!
---------------------------------------------------
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/kevinwsutter
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
