The renaming is only occurring in 4.0.0 codebase. We have no timeline for when 4.0 will come out but there will be plenty of warning and UPGRADE notices about the nomenclature changes which include backwards compatibility with the old nomenclature but documented as deprecated. The old nomenclature will not be removed for at least a year and only when we jump to 4.1.0
NOTE: 3.4.5 which is being worked on is just a bug fix without nomenclature changes. 3.4.5-pre1 came out a week or so ago and I'll look to build a pre2 with some more minor fixes. Regards, KAM -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 On Fri, Jul 10, 2020 at 4:58 AM jdow <j...@earthlink.net> wrote: > On 20200710 01:46:55, Olivier wrote: > > Hi, > > > > One solution maybe to release the next version of SA with only the > > renaming and no other change in the features. And give the users time to > > see whether it works or if the renaming creates serious problems of > > compatibility. > > > > While I find the words black/white list easy to use, I wou;ld not mind a > > renaming if the new names are something common, like deny/allow. The > > conned names block/welcome sound very artificial to me. > > > > But the realy main issue is compatibility. > > > > Best regards, > > > > Olivier > > > > Quick, somebody - fork the project while they er "fork" it. > > {^_-} >
