[jakarta.ee-spec.committee] TCK download directory conventions

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

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.)