Fedora Triaging and QA

[Rahul Sundaram]

Hi

For those who have been wanting to improve the quality of releases, get 
effective dialogue and responses in bugzilla and work on reducing the 
chances for regressions in Fedora updates, here is a good opportunity to 
get involved.

http://www.livejournal.com/users/gregdek/2714.html. Contact gregdek AT 
redhat.com

There are some low hanging fruits that the community can potentially 
tackle in a better way. Every new update is first pushed into 
updates-testing repository to enable the community to test and check for 
regressions and provide feedback in the fedora-test list and  the 
relevant bugzilla reports. The amount of feedback at times have been 
very low and thats usually ok for the large majority of updates but some 
of the them are heavy impact ones like the Kernel or Xorg updates and do 
require community testing. Internal testing does not always reveal 
regressions in specific chipsets, architecture and hardware . If you 
have a spare test machine lying around that you could use and you would 
like to tinker and get involved in Fedora, updates-testing and the 
Fedora development tree are for you.

General guidelines and instructions are available at : 
http://fedoraproject.org/wiki/Docs/Drafts/TestingGuide

regards
Rahul