Re: \set Score.proportionalNotationDuration warning on LilyPond 2.25.23

>
> if you have reasonable ideas how such API changes could be
> communicated better I am sure people would love to hear them and if
> feasible
> incorporate them.


IMO one relatively simple change would be to add a note to the release
announcement email mentioning that users should expect to need convert-ly.
Such a note could be part of the standard template, but it would be even
better if it were only included for development versions containing changes
likely to require convert-ly. There have been quite a few threads from
confused users who were surprised their code didn't work as is on the
recent development releases. Giving a heads up when a particular
development release includes a significant change like this might help it
go a bit smoother.

Saul