As others have stated, testers know not what to look for when testing hot new code. Suggestions included some sort of a form, or checklist, for testers to review and submit back to devs. Sometimes patches are meant to be security or performance related with no overt and obvious changes to gui/functionality that an end-user type tester would be looking for. A disclaimer or instructions on what to look for would be important in these cases.
Jefte On 3/17/06, Abhay Kumar <[EMAIL PROTECTED]> wrote: > > > Anybody on the list willing to take the lead on this initiative? :^) > > What exactly are you looking to formalize? With trac as a bug/feature > ticket tracker and this email list / IRC, are we missing some key > element that is necessary to improve the current model? > > AK > -- > Abhay Kumar > http://abhaykumar.net/ > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
