From Fedora Project Wiki

< FWN‎ | Beats

Revision as of 22:03, 30 June 2010 by Adamwill (talk | contribs) (initial cut at next beat)

QualityAssurance

In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2].

Contributing Writer: Adam Williamson

Test Day process improvements

A message[1] from James Laska prompted a wide discussion of possible improvements to the Test Day process to improve participation. James asked[2] if the group was trying to run too many events and not dedicating sufficient time to each, but Adam Williamson did not think so[3].

Jóhann Guðmundsson suggested[4] extending the test period to a week and broadening the coverage of each event. Adam felt the concurrency aspect of a single day to bring testers and developers together in real-time was valuable, but thought Jóhann had a valuable point in that the group could do a better job of making it clear to potential testers that testing performed outside of the Test Day is still valuable. Jeff Raber made some concrete suggestions[5] as to how this could be achieved, and Adam implemented them[6].

Jeff also suggested changing the name of the events, though Adam mentioned in his reply that he had not been able to think of anything that improved on 'Test Day'. Eric Blake suggsted[7] 'Test Blitz', James contributed[8] 'Bug Day' and Jóhann favored[9]'Test Sprint'. Adam jokingly proposed a poll[10], and added some wider-ranging thoughts about how the process could be re-organized to provide greater opportunities for participation and publicity while not losing the aspect of concurrency.

Proven testers

After several more revisions following the work mentioned in last week's issue, Aaron Farnes announced[1] that the proven testers instruction page had been moved to the main wiki space[2]. Several people replied to congratulate Aaron on the clarity of the page.

New desktop release criteria

Adam Williamson proposed[1] several new release criteria, as a result of his discussions with the various desktop SIGs. These would cover session management tasks, update notification, and keyring functionality.

Fedora 14 recommendations

James Laska announced[1] that he had filed a group of trac tickets covering the recommendations for the Fedora 14 cycle which had derived from the Fedora 13 retrospective discussed in previous issues.