https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7826
--- Comment #81 from Henrik Krohns <apa...@hege.li> --- (In reply to Sidney Markowitz from comment #77) > 2) steps that would complete this issue to get to a stable > and coherent 4.0.0 release. It could go something like this: - Test trunk-welcomelist - Disable automatic updates per this comment # If https://svn.apache.org/repos/asf/spamassassin/trunk/rulesrc/scores/DISABLE-AUTOMATIC-UPDATES # exists then DNS updates will be skipped so that update publishing is # effectively disabled - Merge trunk-welcomelist into trunk - Wait for rule updates to run, then manually get the new rule package and test it works ok on few 3.4 and trunk systems - Enable automatic updates - Create 4.0 branch if needed. There was discussion before if we really need one.. I think agreement was that development is so marginal that it's fine to do things in trunk directly. As long as commits are "complete and tested", and not some bits and pieces of large update like this bug - those should be done in a branch.. or simply don't commit clearly unfinished things which you never get back working on. -- You are receiving this mail because: You are the assignee for the bug.
