https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7417
--- Comment #26 from John Hardin <[email protected]> --- (In reply to Dave Jones from comment #25) > I will send the email to the users list right after the commit. "We've checked in a potentially breaking change, you have 36-48 hours to see whether it will break your environment before it actually does break your environment." Is that polite? Given the gush of duplicate bugs opened for the "Can't locate object method "check_for_forged_gmail_received_headers"" oopsie, I'd feel a lot better if we announced "We are *about* to make a potentially breaking change, please check your local rules for these dependencies and correct them:" and wait a bit before the commit. As I said, this isn't time-critical. Let's be as polite and proactive as we can. -- You are receiving this mail because: You are the assignee for the bug.
