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 Days
The Fedora 14 Test Day cycle has concluded. If you would like to propose a main track Test Day for the Fedora 15 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[1].
Installing Rawhide
Qiang Li asked what was now the recommended method of installing Rawhide[1], given that a Rawhide installer build is now not always available. Adam Williamson recommended updating from the latest pre-release using yum[2], to which Qiang replied that he does not like doing this due to the time and bandwidth involved[3]. Later in the discussion, Christoph Frieben recommended using the latest pre-release installer and specifying Rawhide repositories during the repository selection step[4]. Rui He[5] and Jesse Keating[6] also suggested this method.
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-October/094970.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-October/094971.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-October/094973.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-October/094977.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-October/094995.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-October/094983.html
Testing updates just prior to release
Kamil Paral asked how one can test the installation of updates shortly before a release, when none are available in the official update repositories[1]. James Laska recommended downgrading an installed package such as gcalctool[2], and noted he has a repository available for this purpose.
Fedora 12 critical path testing
Adam Williamson noted a Fedora 12 updates-testing report which listed many critical path updates which had been awaiting the required proventester testing for some weeks[1]. He proposed removing the proven tester requirement for Fedora 12 critical path updates as a practical measure to allow the updates to go through before EOL. In the mean time, he reported that he had tested several of the updates in a virtual machine[2], and Gene did the same[3], allowing several of the updates to go through.