https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7826
Sidney Markowitz <sid...@sidney.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sid...@sidney.com --- Comment #66 from Sidney Markowitz <sid...@sidney.com> --- I guess I'll peer into this barrel of worms, though with great trepidation. It seems we are about rapidly approaching the release of 4.0.0, I don't understand how we can 1. fulfill a stated intention to remove "whitelist" and "blacklist" from our code in the same time frame as fixing the other milestone 4.0.0 issues 2. avoid creating additional worse problems with backwards compatibility if we release 4.0.0 without the changes to whitelist and blacklist, then try to get them in a point release 3. release 4.0.0 from trunk in its current state where it seems that a large start to the whitelist blacklist changeover has already been committed but not completed I know that there are many people running from trunk and that mass-check depends on trunk, so whatever has been committed must be usable at this time. But does what is in trunk right now make sense as a coherent release with a partway change in terminology? Kevin, can you explain what the current state is, the roadmap for the rest of it, and your understanding of how an imminent 4.0.0 release can happen? -- You are receiving this mail because: You are the assignee for the bug.