Announce-gen generate this snippet: > Here is the GNU libtasn1 home page: > https://gnu.org/s/libtasn1/
Why? Shouldn't we use the canonical URL in the announcement? I think the above just looks ugly when the real URL is: https://www.gnu.org/software/libtasn1/ I can see the utility to shorten in some places, but I think the first URL to the project in the announcements should use the canonical URL. Any objections to changing this? README-release says: > * Wait a few minutes (maybe up to 30?) and then use the release URLs to > download all tarball/signature pairs and use gpg --verify to ensure > that they're all valid. I found today that this is problematic -- I waited for around 4 hours until I gave up and changed the announcement to use ftp.gnu.org/gnu/libtasn1/ URLs instead. There is mirror status available -- https://download.savannah.gnu.org/mirmon/allgnu/ -- and some sites are up to 24 hours late. The https://ftpmirror.gnu.org redirector also does not seem to work very well, it can pick a rather stale mirror or a currently offline mirror -- right now I get redirected to https://ftp.wayne.edu/gnu/ which is not answering. And then you can't get redirected to another mirror if you retry the ftpmirror.gnu.org URL again. I can live with manually doing s,ftpmirror.gnu.org/PROJECT,ftp.gnu.org/gnu/PROJECT, while preparing release notes, but I wonder if we should just give up on using ftpmirrors.gnu.org URLs in the announcements? /Simon
signature.asc
Description: PGP signature
