>> 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.
But this is explicitly declared a *development* version, for good reasons! Users *must* expect changes, and they *must* run `convert-ly`. > 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. I disagree. I think it is unfair to put this burden on us developers for the 2.25.xx series. On the other hand, it is certainly useful to explicitly add a reminder to the 2.26.0 announcement note to use `convert-ly`. Werner
