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
The template for this is:
So we could just add a TCK Summary section to that.
I don’t think we should be concerned with long term persistent results for the release reviews. We have stronger requirements for when the associated compatible implementations request certification, and there I expect that an implementation certification request will be associated with some product release page.
Some TCKs have optional elements. This would change the total number of tests passed. I don't know how difficult it is to attribute specific test groups with the optional elements. My recommendation would be, at least: list the number pass. There should be zero failed and zero tests with errors. List the required/optional selections. Maybe include the complete test summary (though that will be quite lengthy for some Specifications (notably, the 46K lines for a successful, with all optional elements, result for Jakarta EE full platform.) But, it's just text so even that's not super "taxing" on any resource -- but I wouldn't want this in the release text summary on GitHub. I think the goal ought to be to provide sufficient detail so that the result is understood and could be replicated if there was any question. How long must these results be made available? -- Ed On 7/15/2019 4:43 PM, Bill Shannon wrote: Rereading our instructions I see that the link to the staged TCK
is supposed to be in the GitHub release text for the spec release.
But where do we provide the link to the GitHub release for the spec?
For example, the Jakarta Mail spec release is here:
https://github.com/eclipse-ee4j/mail-spec/releases/tag/1.6
Is that what we want a GitHub spec release to look like? I'd love to have
a template for that as well! :-)
Bill Shannon wrote on 7/15/19 3:31 PM:
The specifications PR template doesn't ask for the location of the
staged TCK. The _index.md file should have the location of the released
TCK. How should the location of the staged TCK be communicated to the
spec committee for review? Should we add it to the PR template?
Bill Shannon wrote on 7/15/19 1:27 PM:
It would be good to establish some conventions for the
download directories containing the TCKs.
The TCKs currently produced from the jakartaee-tck repo are being put in
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/staged/
with the expectation that the signed and approved versions would be moved to
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/release/
For Jakarta Mail I followed a similar pattern, putting the TCK in
https://download.eclipse.org/ee4j/javamail/mail-tck/mail-tck-eftl/staged/
I don't think there's any reason that all the TCK downloads need to be
in the jakartaee-tck directory.
If/when the component TCKs are split out of the jakartaee-tck project,
we would want them in a download directory associated with their spec
project. I'm thinking of a pattern like this (all under
http://download.eclipse.org/):
ee4j/<project>/<project>-tck/<project>-tck-eftl/staged/
ee4j/<project>/<project>-tck/<project>-tck-eftl/release/
ee4j/<project>/<project>-tck/<project>-tck-epl/
That allows ee4j/<project> to contain other project downloads,
and separates the eftl and epl versions of the TCK. If that seems
too verbose, we could use something like:
ee4j/<project>/tck/eftl/staged/
ee4j/<project>/tck/eftl/release/
ee4j/<project>/tck/epl/
Comments?
(Note that the component TCKs produced from the jakartaee-tck repo would
continue to be put in the jakartaee-tck directory for now.)
_______________________________________________
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
_______________________________________________
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@xxxxxxxxxxxTo 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@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
