Re: Time (to start planning) for a new release?

On Mon, 22 Jan 2024 00:00:52 +0000, Nick Morrott wrote:
[...]
> Whether Windows builds are disabled during pre-release testing is a
> separate question. Build testing is usually a good idea.
>
[...]
> If we want to tag pre-release versions it makes sense to continue to
> adopt SemVer [1] for the pre-release versioning. E.g. (assuming 1.3.0
> is the next version):
> 
> 1.3.0-beta.1
> 1.3.0-rc.1
> 
>   [1] https://semver.org/
> 
> Does this make sense?
> 

Looks like a good idea.

The GH Action will always make the Windows build, but only pushes the exe to SourceForge and http://xmltv.org/alpha/ if the workflow was triggered by a 'push' action. 
(So, for example, it still tests the build but does not upload when people generate pull requests.) 
(q.v. winbuild.yml L178 et sub.)

So, other commits (e.g. during release preparation) will cause upload to SF & Alpha. We probably don't want these polluting the release space, so should we mod the GH action to only upload if a pre-release versioning is not present?  

(q.v. winbuild.yml L129-148 where it uses 'git describe HEAD' to get the version tag)

Rgds,
Geoff