[Nasm-devel] Tagging releases on github

[Billy O'Neal (VC AIR)]

Hi there!

We recently had another spat of nasm.us being down causing people to break:  https://github.com/microsoft/vcpkg/issues/2777

We would love to stop having vcpkg customers hammer nasm.us; we don't presently rehost that stuff because it involves ... licensing scary, but as the copyright holders if you added a release we would love to use that as a primary mirror instead.

Thanks!

Billy O'Neal
Visual C++ - vcpkg
________________________________
From: Billy O'Neal (VC AIR) <bion at microsoft.com>
Sent: Tuesday, May 31, 2022 10:43 AM
To: Cyrill Gorcunov <gorcunov at gmail.com>; nasm-devel at nasm.us <nasm-devel at nasm.us>
Subject: Re: Tagging releases on github

The releases appear to be tagged; they just don't have the release binaries attached.

The right way to do that depends on what you use for your release process. Here's an example using GitHub Actions: https://github.com/marketplace/actions/publish-release

Billy3
________________________________
From: Cyrill Gorcunov <gorcunov at gmail.com>
Sent: Sunday, May 29, 2022 02:36 AM
To: nasm-devel at nasm.us <nasm-devel at nasm.us>
Cc: Billy O'Neal (VC AIR) <bion at microsoft.com>
Subject: Tagging releases on github

You don't often get email from gorcunov at gmail.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Hi Billy! Thanks for ideas on tagging releases via github. I think we should do so and will try to figure out how to automate this procedure.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nasm.us/archives/nasm-devel/attachments/20230731/6cba2171/attachment.htm>