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")

-William

On 2/9/25 22:50, Saul Tobin wrote:
    Do you think this isn't prominently enough?  If so, how could this be
    improved?


I think that as with many warnings, the fact that it's always there leads to it fading into the background for many readers, particularly as they learn from experience that for /most/ code, /most/ of the time, convert-ly doesn't even make changes between versions. I also suspect that many users download and install without going to the changelog page at all.

My thought is that we often have some idea ahead of time if a particular change is likely to affect a lot of users. In those cases, I think it might be helpful to include an extra heads up note in the announcement email and on the download page that this particular development release has bigger changes than normal and most users should expect convert-ly to be needed.

--
William Rehwinkel (any pronouns)
Juilliard School '26 - Oberlin Conservatory '24
will...@williamrehwinkel.net - https://williamrehwinkel.net
PGP Public Key: https://ftp.williamrehwinkel.net/pubkey.txt

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to