>> 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.
This is in a warning box on page 1 of `changes.pdf`, as is https://lilypond.org/doc/v2.24/Documentation/changes/index.html https://lilypond.org/doc/v2.25/Documentation/changes/index.html Do you think this isn't prominently enough? If so, how could this be improved? Werner
