[Issue 15910] Prevent mismatch of VERSION information in dmd releases

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=15910

Martin Nowak <code at dawg.eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |code at dawg.eu

--- Comment #1 from Martin Nowak <code at dawg.eu> ---
> For the second release in a row (2.070.0 followed by 2.071.0), dmd has been released with the VERSION file not updated to match the release version

That's not entirely correct b/c the downloadable packages contain the correct
VERSION file, it's only that the tagged git commits have an incorrect VERSION
file.
Now we could validate that the VERSION file contains the to be build tag, but
this will be a constant nuisance, e.g. deleting already created tags, changing
the VERSION from 2.071.0-b1 to 2.071.0-b2, retag, and build.
I'd instead suggest that any build script using the git repo or tags, should
get the VERSION from git or write the VERSION file when downloading a tar
bundle from github.
VERSION can also be set through make -f posix.mak VERSION=2.071.0.

--