https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7826
--- Comment #74 from Loren Wilton <lwil...@earthlink.net> --- (In reply to Henrik Krohns from comment #72) > > This is my preferred way, would vote +1 I don't have a vote, but I'll vote +1 for this anyway. Sidney, I *think* that the changes can be rolled back in trunk, including the rules. However, there are probably a few people running trunk that are not developers/committers that may have used some of the new terminology. These would break with the rollback. However, I think trunk should be treated as somewhat unstable, so we could just announce what is going to happen (and the implications on own rules) a week or two before the actual drop, and let it go at that. If there was worry over some probably small percentage of the probably few people running trunk suddenly getting lint errors, some work could be done to put some aliasing into trunk, aliasing the new names to the old names. I (again having no vote) would vote against this; it is extra work and likely to destabilize things. As a completely separate longer-term discussion, perhaps rules should be in their own tree and not part of trunk. -- You are receiving this mail because: You are the assignee for the bug.
