Re: [jakarta.ee-spec.committee] Ideas for downloads area and binary sign

["Kevin Sutter" <sutter@xxxxxxxxxx>]

I would recommend
we drop the date from the file names.  The name and version are sufficient.


---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Bill
Shannon <bill.shannon@xxxxxxxxxx>
To:
       David
Blevins <dblevins@xxxxxxxxxxxxx>
Cc:
       Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:
       07/17/2019
04:04 PM
Subject:
       [EXTERNAL]
Re: [jakarta.ee-spec.committee] Ideas for downloads area and binary signing/promotion
Sent
by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx

---

David Blevins wrote on 7/17/19 1:47
PM:>> Currently our TCK zip files are named
like mailtck-1.6.0_10-Jul-2019.zip.
>> They definitely need the dot-dot version number to allow for updates
to
>> the exclude list (for example).  (All approved versions should
remain
>> available forever, not overwritten by newer approved versions.)
>>
>> Do you want us to remove the date from the name?
>>
>> Do you expect to rename the zip file when promoting and signing
it?
> 
> With an "infrastructure" hat on, I was imagining creating
something that did as little as possible.  So if the project handed
us https://<some-staging-location>/mailtck-1.6.0_10-Jul-2019.zip
and we the Specification Committee wanted to approve that, the infra would
promote that as-is to their directory for that version, becoming:
> 
>  - https://download.eclipse.org/jakartaee/mail/1.6/mailtck-1.6.0_10-Jul-2019.zip
>  - https://download.eclipse.org/jakartaee/mail/1.6/mailtck-1.6.0_10-Jul-2019.zip.asc(our signature)
> 
> Adding would ok.  Deleting would not, nor would overwriting.
> 
> 
> With my spec committee hat on, I'm ok letting specification projects
have some freedom here, but don't have a strong opinion.  If someone
does imagine some naming convention, I'm ok with that.

I'm open to a new naming convention as well, although it doesn't seem
important right now.

Unless a consensus develops otherwise, we'll continue to use our existing
naming convention.
_______________________________________________
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