Thanks for the rate limiting information, Ivar.
In light of that, I've created a PR so it is published in our specifications repository and will show up on the website:
After mentioning not using HTTP, I thought further and remembered the point of that part of the script was to do the verification steps as a user would need to do them to ensure they could successfully verify the downloads. If we're hitting github rate limit issues, they might hit them as well. Having the key in the same location where it is referenced on the specification pages is ideal. Basically, anywhere but the downloads area where the binaries live is viable.
Once we get this merged I'll update the CI scripts and send another PR to update the link we use for the public key in our specification pages.
-- David Blevins 310-633-3852
_______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|