> So, taking [Bug 6426] and [Bug 6544] as examples, what is > a sentiment about such? Just close after the change has been > commited to trunk for some time, or should we follow a voting > procedure for each open problem report?
Documentation is here: http://wiki.apache.org/spamassassin/DevelopmentMode It links to: http://www.apache.org/foundation/glossary.html#CommitThenReview Which says: "(Often abbreviated 'CTR' or 'C-T-R'.) A policy governing code changes which permits developers to make changes at will, with the possibility of being retroactively vetoed. C-T-R is an application of decision making through lazy consensus. The C-T-R model is useful in rapid-prototyping environments, but because of the lack of mandatory review it may permit more bugs through than the R-T-C alternative. Compare , and see the description of the voting process." Which I interpret to mean that you should close such bugs immediately. It doesn't actually say review is necessary anywhere. -- "Let's just say that if complete and utter chaos was lightning, then he'd be the sort to stand on a hilltop in a thunderstorm wearing wet copper armour and shouting 'All gods are bastards'." - The Color of Magic http://www.ChaosReigns.com
