I think hosting the TCK results in the spec project would be fine.
If you need GitHub Pages enabled for your project and can't do it
yourself, I'm sure you can file a bug at Eclipse to have it done.
For the final approval, you should be using the EFTL-licensed
version of the TCK (although admittedly they differ only in the
license file). And the PR for approval needs to link to that
version of the TCK.
Tom Jenkinson wrote on 7/24/19 4:42 AM:
From your email I am not entirely certain whether it would
be Glassfish as the "Compatible Implementation" project which
should host the TCK results file for Jakarta Transactions or
whether the API project should host it instead? I saw Jakarta
Mail providing it themselves but that is an implementation too
in the project so it seemed OK to do that. Assuming it is OK
for an API project to host results for Glassfish, do we just
need to create something like:
https://github.com/eclipse-ee4j/javamail/blob/gh-pages/TCK-Results.md
(but I suppose we need to ask someone to enable Github pages
on our repos (
https://pages.github.com/#project-site)?
Once
you've decided where to publish your TCK results, please edit
your
jakarta.ee/specifications
Pull Request and add this entry:
- [ ] The URL of the TCK results summary:
<add URL here>
and fill it in with a link to your TCK results. Example here:
https://github.com/jakartaee/specifications/pull/3
Thanks.
Bill Shannon wrote on 7/23/19 12:32 PM:
> I wanted to summarize a few discussions that have
occurred recently.
> There's some important details here; sorry this message
is so long.
>
> - Publishing TCK results
>
> TCK results need to be published in a permanent, stable
location for
> each release of a Compatible Implementation. TCK results
should *not*
> be included as content in the jakarta.ee/specifications
Pull Request.
>
> TCK results should be published in some location related
to the project,
> e.g., on the project's web site, on the project's wiki,
or in the
> project's repository. It's up to the project where to
publish them.
> For example, I've published the results for Jakarta Mail
here:
> https://eclipse-ee4j.github.io/javamail/TCK-Results.html
>
> TCK results need only include the summary/total lines
from the JavaTest
> output (as in the example above). The complete list of
which tests have
> been passed is not required, but may be included.
>
>
> - TCK location
>
> The staged version of the EFTL-licensed TCK for a project
should be
> published in the project's download area on download.eclipse.org.
> Currently most of the TCKs are created in the
jakartaee-tck project.
> The staged versions of these TCKs are available here:
> https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/staged/?d
> The URL of the staged TCK zip file should be included in
the
> jakarta.ee/specifications
Pull Request.
>
> For projects produced outside of the jakartaee-tck
project, we recommend
> a directory structure under download.eclipse.org
of the following form:
>
> <project>/tck/eftl/ - staged EFTL-license
versions of the TCK
> <project>/tck/epl/ - EPL licensed non-final
versions of the TCK
>
> This is only a recommendation; projects are free to
organize their download
> directory however they want.
>
> After approval, the TCKs will be signed and published at
this location:
> https://download.eclipse.org/jakartaee/<project>/<major>.<minor>/<zip-file-name>
> where <project> is the project's short name from
the "Code" column of
> this spreadsheet:
> https://docs.google.com/spreadsheets/d/18SraPxRBCOyaS6w-UV6TR-UA1bWy1--sV0ky6msAjWY/edit#gid=0
> This download location should appear in the _index.md
file of the
> jakarta.ee/specifications
Pull Request.
>
>
> - TCK documentation review
>
> We strongly encourage all Project Leads to review the
documentation,
> and especially the TCK User's Guide, included with the
TCK zip files.
> Any problems with the documentation should be corrected
via Pull Requests
> to the appropriate TCK project (e.g., jakartaee-tck), or
via issues filed.
>
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads