Re: Windows releases

On Wed, 27 Apr 2022 at 21:43, Robert Eden <[email protected]> wrote:

[public mailing list]

> The normal way to build a full windows release is
>
> Perl Makefile.PL PREFIX=/path/to/temp/xmltv-1.1.2-win32
> make windows_dist
> (answer question about is the README updated... maybe remove question from build?)
> Copy xmltv.exe to  /path/to/temp/xmltv-1.1.2-win32/xmltv.exe
> zip it up
> upload
>
> The benefit over "bare" xmltv.exe is it includes TXT versions of all the man pages... in other words, documentation! :)
>
> If we create an "action" for automating official releases (not just pre-release artifacts for testing), something similar should be done for windows.  I'm not sure how Nick has done previous releases, but Gary is a wizard in this regard! :)

Currently, releases are made by tagging the release commit in git and
pushing it. A new release against that tag can then be created on the
Releases page by drafting a new release with notes, and then releasing
it. It takes a few minutes.

The tarball and zip file are automatically added to the release, I've
been manually adding the xmltv.exe when available, but this step can
likely be automated now that it's building via Github Actions?

I would be hesitant about automating the _whole_ process (up to and
including the actual "Release the hounds"), but would be keen to have
it automate everything to create the draft release, notes and assets,
before being approved manually. Does this sound sensible?

Thanks,
Nick