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

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

Scott Stark wrote on 7/17/19 11:09 AM:
> So as I understand what David was suggesting, there would be a further release version in the project directory structure, so the root for a given release review would be download.eclipse.org/ee4j/<project>/x.y

That was part of the confusion in the meeting.  I think he was only
proposing that for the jakartaee directory.

> This is consistent with what we are doing with the jakarta.ee specifications content. David was also talking about this convention for what the spec committee promotes as final under the specification committee specific download.eclipse.org/jakartaee/<project>/x.y directory as you have indicated for the TCK.
> 
> End of the day, download.eclipse.org/ee4j/<project> is a good minimum requirement. Details can be left to project provided that the candidate eftl binary is not overwritten during the release review.

I agree.

>> On Jul 17, 2019, at 10:53 AM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>>
>> Now that I've had time to think about it, I think I understand David's
>> proposal...
>>
>> Projects would put their staged EFTL TCK zip file somewhere under
>> download.eclipse.org/ee4j/<project>/
>>
>> Where exactly they put it doesn't matter.
>>
>> The URL to the zip file would be included with the release review.
>>
>> When the spec is approved, the zip file would be picked up from the
>> URL location and copied to download.eclipse.org/jakartaee/<spec>/<version>/
>> and signed.
>>
>> The <spec>/<version> directory might contain multiple versions of the TCK
>> as it evolves for that spec version, e.g., as the exclude list is updated.
>> The TCK zip file thus needs to be named in a way that allows multiple
>> versions for a particular spec version to coexist in the same directory.
>>
>> Ideally, the staged EFTL zip file would be removed after it has been copied
>> and signed, but that's not critical.
>>
>> The non-final EPL-licensed TCK zip files would also be put under
>> download.eclipse.org/ee4j/<project>/, again in a directory structure
>> that might follow a convention but could be decided by each project.
>>
>> This all seems fine to me.
>>
>> I might recommend that projects use the directory structure conventions we
>> discussed below and in the meeting, but again that's not critical.
>>
>> Comments?
>>
>>
>> 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
>