https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7826
--- Comment #77 from Sidney Markowitz <sid...@sidney.com> --- Since there are no more issues with the 4.0 milestone other than this one, perhaps now is the time to create a 4.0 branch. The next steps would be to create two roadmaps, 1) steps that would rollback commits from this issue that are necessary to remove to get to a stable and coherent 4.0.0 release; and an alternate 2) steps that would complete this issue to get to a stable and coherent 4.0.0 release. That way we would not conflate the issue of masscheck having to be run from trunk (bug 7837) with anything having to do with the 4.0.0 release and how this issue will or will not be part of it. Once we know what we would have to do to get a 4.0.0 released with or without the nomenclature change, we can more rationally decide on which one to do. And having the roadmaps will make it easier to plan out and split up the work to getting this done in a more transparent manner with more consensus. It may be that we have to put more urgency into solving bug 7837 in a way that leaves the process of masscheck less fragile in its dependency on bleeding edge code. Anyway, I think the action item out of this that is most likely to get agreement is to create a 4.0 branch. It doesn't have to formally be R-T-C yet, but I would like to have a consensus on what we are going to do with this issue for 4.0.0 before anyone actually takes the step of reverting the commits, i.e., let's do it with a plan and a roadmap this time. -- You are receiving this mail because: You are the assignee for the bug.
