nullack at gmail.com
Fri Sep 12 04:07:15 UTC 2008
Sorry, gmail had an issue. So following on from my mail.
With my experience testing Intrepid I think there is value in me
looking at serious bugs not yet on the milestone list as well as bugs
that need priority/attention increased.
I informally did this in the past like a recent issue that broke flash
for Intrepid users with Brian.
My thinking is around some sort of sketchpad / wiki to jot down
feedback for the next QA status report? Or I could provide my work to
someone who then consilidates all the QA team feedback for
presentation at the release meeting?
More information about the Ubuntu-qa