[email protected] wrote on 11/21/12 9:28 AM: > 3. We establish a review policy that any patches that can definitely > have a crashtest associated with them has to be included on check-in > by the developer building the patch. If the patch comes in without a > crashtest that can indeed possibly have one, the patch gets a review- > until the test is included. That will balance both validating that > the patch actually does work at check-in, but also starts to burn > through progressively building out a crashtest regression automation > suite.
We need a policy for in-testsuite? in general. Lots of bugs depend on our judgement right now. I would love if devs would take care of this flag and set it appropriately after the landing on inbound or m-c. That would give us a perfect way to track upcoming and left-to-do work. Shall we only do that for crashtests and mochitests? I would think so because unit tests should be landed together with the actual patch. -- Henrik _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
