Hi Karl, Matt, Ursula, Diogo, In the today's team lead call, Curtis raised the issue of QA for community contributions and how we're are already overloaded with QA.
We've agreed to try to integrate community into our existing QA process, at least for things they can easily help with. Major components to this would be: * existing test plans * QA section in cover letters in merge proposals It'd be nice to organize test plan generation scripts to link directly to MPs if available (Ursula and Diogo, if you can find time to do this, that'd be wonderful :), but the first step we want is to get this documented as one of the core steps of contributing on dev.launchpad.net. We want this available to non-coder contributors as well, so having it slightly disconnected from "submit a patch" might be useful. Perhaps a top-level item "I want to... verify stuff works" (or whatever makes most sense). Anyway, I am sure you guys can figure out the best way to lay this out yourself. :) Cheers, Danilo _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
