I think we previously agreed that the specifications pages would
list all the compatible implementations (except maybe for the
platform, which is an open issue for the steering committee). But I
still don't think we want all the TCK results for every release of
every compatible implementation to be on the specifications pages.
(And each CI should have only one entry per spec version, not one
per CI release.)
David Blevins wrote on 7/16/19 1:40 PM:
How about this. We the compatible implementations simply seed the
list of compatible implementations. There's a link to their
results as normal. As the list of compatible implementations
increases, that section is simply expanded as per usual. Who was
first can easily be determined by looking at the first commit and
PR if we really need that later.
The rule is simply, "your compatible implementations
list cannot be empty."
Everyone coming later then has a clear example to
follow when they submit their PRs.
--
David Blevins
310-633-3852
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@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
_______________________________________________
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
|
