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

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

That's fine, we can collapse the eftl staged and release directories.

And I'm fine with the shorter names too.

Any other opinions?

Scott Stark wrote on 7/17/19 9:02 AM:

After looking at this in more detail, I don’t think we need an eftl release directory as the idea as I understand it is that the spec committee would sign the staged final eftl candidate and then promote that to a spec committee area on downloads.eclipse.org and this would be linked to from the spec page on jakarta.ee.

In terms of the naming convention, I prefer the shorter one.

On Jul 15, 2019, at 1:27 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

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