Re: \set Score.proportionalNotationDuration warning on LilyPond 2.25.23

>
> Isn't that the reason that the changes documentation is written in the
> first place...to warn users about upcoming changes? So an extra warning
> in the email would be redundant, and this warning would also fade into
> the background? (by the way, I don't think that comparatively a _lot_ of
> users use "\set Score.proportionalNotationDuration")
>

When I've led systems migrations, typically the guideline is 3 separate
communications about any given change — minimum. And people still get taken
by surprise.

I agree that added warnings wouldn't be helpful if they are there all the
time. The value would be attaching them only to specific releases with
changes expected to affect a lot more user code than a typical release.

It's true that proportional notation isn't a super widely used feature. But
this change is part of a much larger patch series applying the same type
change to every property that expected a moment for its value.