Yes, that's the intent.
The staging location is just a temporary location. Those TCKs might
be removed or overwritten after approval.
The PR is for what we want the specification web site to look like after
approval, and thus needs to have the URL that will be used to access
the TCK after it's approved. We don't put the TCK in that location
before approval to avoid any possible confusion as to whether the
TCK is approved yet or not.
The text in the spec PR includes the staged location of the TCK, so
that we can review it, and so that it can be copied from that
location to the final location after approval.
Does that make sense?
Tom Jenkinson wrote on 8/15/19 9:19 AM:
Please can you confirm, I am seeing specification PRs with
prospective URLs for the TCK location in the _index.html that
404 at the minute.
It does make sense to me to have this permanent URL in the
file for review and in the PR description to have the current
staging URL and I think that is consistent with what is being
asked for but I would just like some confirmation if that is
what we are meant to be doing?
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://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
|