Better ideas. Another possibility is every 24hrs to run parser tests (and any other regression tests that might exist) against all revisions committed into trunk since the last run. Post the results and keep track of the number of bugs each committer has introduced into the code base for the past running 6 month period. Post the names of committers and the number of bugs they have introduced on a "hall of shame" page ordering the list by number of bugs.
Sometimes social pressure can be a very effective behavior modifier. --- On Tue, 7/21/09, Brian <[email protected]> wrote: > From: Brian <[email protected]> > Subject: Re: [Wikitech-l] "known to fail" switch added to parserTests > To: "Wikimedia developers" <[email protected]> > Date: Tuesday, July 21, 2009, 11:10 AM > > Right, well, a pre-commit hook that rejects all commits > which break the > software. Or a memory of what commits broke which tests and > a conditional. > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
