On Tue, Apr 09, 2013 at 09:54:32AM -0700, Brendan Cully wrote: > The other big thing that mutt gets blocked on is bug fixes and the > effort it takes to avoid regressions. This takes a lot more time than > it should because we don't have any kind of test suite. Rocco once > started working on one at https://bitbucket.org/pdmef/mutt-testdrive > but I don't know how far he was able to get with it. This would be a > great project for someone with a bit of time, with I think very large > benefits for everyone: applying patches would be safer, and reviewing > them would take less work, so we'd be able to get a lot more through > our limited maintenance bandwidth.
That's what I was thinking (that mutt needs a proper regression test suite). Of course writing that is tedious but it needs to be done if y'all are going to make it easier for people to submit patches. There should also be C style and other development requirements (like regression testing, no compile warnings, etc...) clearly spelled out and enforced before any changeset is accepted into the trunk. -- Will Fiveash
