My preference would be we handle all compatible results consistently and simply require that they publish/host their own results and make a link available as written in the TCK Process document.
My concern with us hosting some results on jakarta.ee is this re-adds the "first through the door" marketing advantage I was hoping we could avoid eliminating RIs. If we're going to start hosting results, the only fair thing would be host everyone's when they are done so those who put the work in can eventually get fair treatment. Otherwise we have a system that always favors impls with the most resources, which is a tough world to live in.
That is what I’m proposing to do with compatible implementations results that are being used to validate the spec api release. Include a TCK summary results section that provides the run of every compatible implementation being used as validation.
On the related thread on this topic, I’m suggesting that the TCK summary results just be a section in the jakarta.ee specification release version page that lists the links to the spec docs, ballots, TCK, etc.
For clarity, the "spec" doesn't have TCK results but compatible implementations do. What are we proposing to do with a compatible implementation's results?
-David
_______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
