> A question I have is then: how can we ensure this is actually done
> *every* year? It actually *is* embarrassing that the released
> versions give a wrong year in the output of lilypond --version.
This is a different issue. Right now, the version number shown in
`--version' must be updated manually, since it is not a file's
copyright notice.
> Can running make grand-replace (and committing the results) be made
> part of the release process?
The basic question is whether `grand-replace' actually handles the
`--version' messages also... IMHO, it should. Then it is fully
sufficient to run it manually at the beginning of new year.
Werner
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
