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 internationalization and localization test week was delayed due to the delay in the Fedora 16 Alpha release and consequent delay to the entire development schedule, so we can simply reprint the information from last week's FWN:
Next week will be internationalization and localization test week, with three test days: desktop localization on Tuesday 2011-08-30[1], localization and internationalization in the installer on Wednesday 2011-08-31[2], and desktop internationalization on Thursday 2011-09-01[3]. Fedora is used in many countries and many languages, so it's vital to make sure translations, keyboard layouts, input methods and so on are working well. There is also a significant new feature to test: GNOME input integration[4], which brings an integrated input method selector to the GNOME 3 desktop.
Fedora 16 Alpha preparation
Following the previous week's slip, Fedora 16 Alpha RC4 arrived on 2011-08-15[1]. Two more blocker bugs[2] [3] were quickly discovered in the new build, and Alpha RC5 promptly followed it on 2011-08-16[4]. The team put in a heroic effort to complete Alpha validation testing on RC5 in less than 24 hours, with the installation[5], base [6] and desktop [7] matrices all filled out. As the testing exposed no further blocker bugs, the QA team was able to report that RC5 met the release requirements at the Go / No-Go meeting of 2011-08-17[8], and the release was declared gold.
Masami Ichikawa noticed that some libreport packages were missing from the Alpha Xfce and LXDE live images, which stopped abrt and sealert from being able to report bugs on these live images[9]. Kevin Fenzi reported that he had fixed the problem post-Alpha[10].
- ↑ http://lists.fedoraproject.org/pipermail/test-announce/2011-August/000266.html
- ↑ http://bugzilla.redhat.com/show_bug.cgi?id=730863
- ↑ http://bugzilla.redhat.com/show_bug.cgi?id=730887
- ↑ http://lists.fedoraproject.org/pipermail/test-announce/2011-August/000268.html
- ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_16_Alpha_RC5_Install
- ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_16_Alpha_RC5_Base
- ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_16_Alpha_RC5_Desktop
- ↑ http://meetbot.fedoraproject.org/fedora-meeting/2011-08-17/f16_alpha_gono-go_meeting_%232.2011-08-17-21.05.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-August/101912.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2011-August/102002.html
Release criteria updates
Adam Williamson reported that he had committed his proposed modifications to the firstboot release criteria and validation tests (see FWN #284)[1]. Adam also made two alternate proposals for refining how the criteria apply to installations to EFI systems[2]. Peter Robinson[3] and Jurgen Kramer[4] generally agreed with the idea of promoting the importance of EFI installations.
Explaining the need for a BIOS boot partition during installation
Tom Horsley questioned whether the Fedora 16 installer's message explaining the need for a BIOS boot partition when booting from BIOS (rather than EFI) using a drive with a GPT disk label was understandable[1]. Adam Williamson wasn't sure the installer was the right place for a detailed explanation of GPT issues[2], but Scott Robbins[3] and Rahul Sundaram[4] agreed with Tom. Rahul suggested filing a bug requesting the message be improved.