Re: [jakarta.ee-spec.committee] eclipse-* -> jakarta-* for TCK zip files

[David Blevins <dblevins@xxxxxxxxxxxxx>]

> On Aug 14, 2019, at 5:46 PM, Scott Stark <sstark@xxxxxxxxxx> wrote:
> 
> How I understood the conversation is that nothing was required from the existing PRs, cert requests and TCK results. The rename would only happen when the current eclipse-*tck EFTL candidate was finalized, signed and copied over to the spec committee location. At that point the spec/x.y/_index.md would also need to be updated.

Correct.  Hashes and signatures all will validate regardless of the file name, so we can fix the branding issue with extremely low impact on one person.

I assume myself obligated to do it as I pointed out the branding issue.  I suspect that signs me up to fix other link issues while I'm at it.  I'm ok with that too.



-David

> 
>> On Aug 14, 2019, at 4:34 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>> 
>> Note that making this change will effect all the certification requests
>> that have been submitted, and will break links in all the TCK results
>> that have been published, both of which include the URL to the TCK download.
>> 
>> Fixing the jakarta.ee/specifications web site might be easy, but fixing
>> all these others is a distributed problem.  I think we should seriously
>> consider delaying this renaming until the next release.
>> _______________________________________________
>> 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