From Fedora Project Wiki

< FWN

No edit summary
No edit summary
Line 86: Line 86:


<references/>
<references/>
{{Anchor|QualityAssurance}}
== QualityAssurance ==
In this section, we cover the activities of the QA team<ref>http://fedoraproject.org/wiki/QA</ref>. For more information on the work of the QA team and how you can get involved, see the Joining page<ref>http://fedoraproject.org/wiki/QA/Join</ref>.
Contributing Writer: [[User:Adamwill|Adam Williamson]]
<references/>
=== Test Days ===
The last Fedora 14 Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2010-10-14_OpenLDAP/NSS</ref> on 2010-10-14 was on the use of OpenLDAP with the NSS security library - the use of NSS with OpenLDAP is new in Fedora 14, replacing the previous use of OpenSSL. [[User:Kparal|Kamil Paral]] provided a recap to the list<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094698.html</ref>. He noted that "the participation was little low, but it was somehow expected, because this was a non-trivial topic" and that the event discovered three bugs and confirmed the rest of the functionality worked.
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<ref>http://fedorahosted.org/fedora-qa/</ref>.
<references/>
=== Fedora 14 Final testing ===
The QA group put together a great team effort to perform comprehensive and efficient validation testing on the Fedora 14 final release. The Test Compose was announced on 2010-10-13<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094596.html</ref>, and the installation<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_14_Final_TC1_Install</ref> and desktop<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_14_Final_TC1_Desktop</ref> test matrices were completed quickly, with results coming in from many different group members. The testing identified several blocker bugs, which were all resolved in time for the release of the Release Candidate on 2010-10-21<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094893.html</ref>. Once again, the group came together to perform the installation<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_14_Final_RC1_Install</ref> and desktop<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_14_Final_RC1_Desktop</ref> validation testing, which was mostly completed by the weekend. No further blocker bugs were discovered (as outlined by [[User:Rhe|Rui He]] in the RC1 testing recap<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094998.html</ref>), and so the QA group was able to join with release engineering and development to sign off on the release of RC1 as Fedora 14 Final at the go/no-go meeting of 2010-10-26<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-10-26/fedora-meeting.2010-10-26-20.59.log.html</ref>. [[User:Adamwill|Adam Williamson]] thanked all of the large number of community members who contributed to the validation testing in a blog post<ref>http://www.happyassassin.net/2010/10/26/fedora-14-goes-gold/</ref>.
<references/>
=== Reporting bugs from downstream distributions ===
[[User:Tk009|Edward Kirk]] reported that the lead developer of Fusion Linux, a distribution based on Fedora, was suggesting users file bugs in Fedora Bugzilla<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094830.html</ref>. A discussion ensued on whether it was correct for users of distributions downstream of Fedora to report bugs directly to Fedora's bug tracker. [[User:Johannbg|Jóhann Guðmundsson]] felt strongly that it was not appropriate, and such distributions should have their own bug trackers<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094844.html</ref>. [[User:Mschwendt|Michael Schwendt]] pointed out that Fedora's abrt does not currently make it easy for downstream distributions to modify it to report crashes to a different bug tracking system<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094848.html</ref>. [[User:Adamwill|Adam Williamson]] thought it made sense for bugs in Fedora packages which are present unchanged in Fusion Linux to be reported to Fedora's bug tracker, in the same way Fedora bug reports are often sent upstream to GNOME or KDE<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094852.html</ref>. The Fusion Linux developer, [[User:Valent|Valent Turkovic]], said that his plan was for Fusion Linux developers to check reports of bugs and ask the user to file them in Fedora Bugzilla if the package was unchanged from Fedora, RPM Fusion Bugzilla if the package came from there, or with Fusion Linux's developers if the bug related to Fusion Linux-specific customizations.
<references/>
=== Release criteria ===
[[User:Adamwill|Adam Williamson]] proposed a new release criterion<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094785.html</ref> requiring the final release notes from the Documentation team be present in packaged form in the release repository (at Final release stage). [[User:Jkeating|Jesse Keating]] suggested similar criteria for artwork, spin-kickstarts and fedora-release packages<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094799.html</ref>. Adam provided revised drafts for all three proposed criteria<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094802.html</ref>.
<references/>
=== Testing new versions of anaconda ===
[[User:mcloaked|Mike Cloaked]] provided a very useful guide to creating a custom USB key to test new releases of anaconda when images containing that version of anaconda are not available<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094752.html</ref>. [[User:Bcl|Brian Lane]] said it was good to see someone else using his work, and pointed out that the script Mike used should also be able to produce a full, updated DVD ISO, but would take longer to do so.
<references/>
=== Fedora QA retrospective ===
[[User:Jlaska|James Laska]] announced the QA retrospective page for Fedora 14<ref>http://lists.fedoraproject.org/pipermail/test/2010-October/094587.html</ref>. The retrospective attempts to identify things that went well and things that went badly during the release cycle, to help the group improve with future releases. He appealed for contributions to the retrospective from anyone who could identify good or bad elements of the QA work for the Fedora 14 release.
<references/>


{{Anchor|Translation}}
{{Anchor|Translation}}

Revision as of 10:24, 28 October 2010

Fedora Weekly News Issue 249

Welcome to Fedora Weekly News Issue 249[1] for the week ending October 27, 2010. What follows are some highlights from this issue.


An audio version of some issues of FWN - FAWN - are available! You can listen to existing issues[2] on the Internet Archive. If anyone is interested in helping spread the load of FAWN production, please contact us!

If you are interested in contributing to Fedora Weekly News, please see our 'join' page[3]. We welcome reader feedback: news@lists.fedoraproject.org

FWN Editorial Team: Pascal Calarco, Adam Williamson

Marketing

In this section, we cover the happenings for Fedora Marketing Project from 2010-10-20 to 2010-10-26.

http://fedoraproject.org/wiki/Marketing

Contributing Writer: Neville A. Cross

Jonas Karlsson started a thread[1] asking about the "core" still present on the packaging names as "fc" designation. Paul W. Frields stated[2] that there are technical reasons for keeping, and thus has been renamed as "Fedora Collection". Beth Lynn Eicher followed up[3] by editing the FAQ wiki[4] to include a answer to that question. Rahul Sundaram contributed[5] more details.

Robyn Bergeron announced[6] that she has posted her interview with Justin Forbes regarding EC2 feature profile.

Last week was asked about links to photo albums for using pictures in the One Release note. Neville A. Cross posted[7] that he browsed all the links and made a pre-selection.

Ambassadors

This section covers the news surrounding the Fedora Ambassadors Project[1].

Contributing Writer: Sankarshan Mukhopadhyay

Welcome New Ambassadors

This week the Fedora Ambassadors Project had a new member joining.

Brandon Lozza from Canada mentored by Larry Cafiero

Summary of traffic on Ambassadors mailing list

Carlos Carreno informed [1] about Fedora Party 2010 at Lima, Peru to be held on 2010-11-06 at Ricardo Palma University. The thread [2] has inputs from other Ambassadors about how to set up an event

David Ramsey reminded [3] about T minus 2 weeks to Fedora 14 and commented about events and party photographs [4]

Christoph Wickert responded [5] to a set of questions from Jesse Keating arounc the multi-desktop DVD. Máirín Duffy pointed out [6] that a few questions still required responses

Chris Tyler thought [7] the multi-desktop DVD to be a 'great idea' but it seemed 'a bit rushed'. He suggested moving this to the F15 timeframe so as to ensure a pleasant end user experience

Further discussion around the timing of introduction of the multi-desktop DVD happened on the thread [8]

Bert Desmet posted [9] about the Call for Speakers [10] at FOSDEM 2011

Scott Williams posted [11] about a possible Fedora Activity Day at SCaLE and asked about things that could be done.

Christopher Hawker thought about a FAD at Sydney, Australia [12] that could be arranged.

Scott Williams posted [13] a request from SCaLE about a 'portable mirror' to be present on-site during the show

Scott Williams posted [14] about the Call for Papers at SCaLE [15]

Gent Thaçi asked [16] about the approval for swag. Christoph Wickert responded [17] asking specific questions around the request for swag

John Poelstra posted [18] details of upcoming Fedora tasks in light of GA being a week away

Susmit Shannigrahi encouraged [19] Ambassadors to nominate themselves/others in the upcoming FAmSCo elections in December [20]

  1. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015764.html
  2. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/thread.html#15764
  3. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015769.html
  4. https://fedoraproject.org/wiki/Marketing_photos
  5. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015775.html
  6. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015785.html
  7. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015782.html
  8. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/thread.html#15796
  9. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015783.html
  10. http://fosdem.org/2011/call_for_mainspeakers_devrooms
  11. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015790.html
  12. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015795.html
  13. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015792.html
  14. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015803.html
  15. http://www.socallinuxexpo.org/scale9x/blog/scale-9x-call-papers
  16. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015798.html
  17. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015813.html
  18. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015804.html
  19. http://lists.fedoraproject.org/pipermail/ambassadors/2010-October/015817.html
  20. https://fedoraproject.org/wiki/FAmSCo_election_2010_nominations

Summary of traffic on FAmSCo mailing list

Joerg Simon responded [1] to Christoph Wickert about FAmSCo taking too long to give a statement on the budget about the multi-desktop DVD

Joerg Simon reminded [2] about the FAmSCo meeting on 2010-10-25

Max Spevack posted [3] about the FAmSCo election nominations [4] The thread [5] has mails from other FAmSCo members discussing about re-election and also posting messages to various Ambassador forums.

Joerg Simon informed [6] that the meeting on 2010-10-25 had no quorum to vote but there was discussion [7] about FUDCon LATAM 2011 [8] and, a request to provide 1200 USD in form of funding for Fedora presence [9] at Comic Con

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 last Fedora 14 Test Day[1] on 2010-10-14 was on the use of OpenLDAP with the NSS security library - the use of NSS with OpenLDAP is new in Fedora 14, replacing the previous use of OpenSSL. Kamil Paral provided a recap to the list[2]. He noted that "the participation was little low, but it was somehow expected, because this was a non-trivial topic" and that the event discovered three bugs and confirmed the rest of the functionality worked.

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[3].

Fedora 14 Final testing

The QA group put together a great team effort to perform comprehensive and efficient validation testing on the Fedora 14 final release. The Test Compose was announced on 2010-10-13[1], and the installation[2] and desktop[3] test matrices were completed quickly, with results coming in from many different group members. The testing identified several blocker bugs, which were all resolved in time for the release of the Release Candidate on 2010-10-21[4]. Once again, the group came together to perform the installation[5] and desktop[6] validation testing, which was mostly completed by the weekend. No further blocker bugs were discovered (as outlined by Rui He in the RC1 testing recap[7]), and so the QA group was able to join with release engineering and development to sign off on the release of RC1 as Fedora 14 Final at the go/no-go meeting of 2010-10-26[8]. Adam Williamson thanked all of the large number of community members who contributed to the validation testing in a blog post[9].

Reporting bugs from downstream distributions

Edward Kirk reported that the lead developer of Fusion Linux, a distribution based on Fedora, was suggesting users file bugs in Fedora Bugzilla[1]. A discussion ensued on whether it was correct for users of distributions downstream of Fedora to report bugs directly to Fedora's bug tracker. Jóhann Guðmundsson felt strongly that it was not appropriate, and such distributions should have their own bug trackers[2]. Michael Schwendt pointed out that Fedora's abrt does not currently make it easy for downstream distributions to modify it to report crashes to a different bug tracking system[3]. Adam Williamson thought it made sense for bugs in Fedora packages which are present unchanged in Fusion Linux to be reported to Fedora's bug tracker, in the same way Fedora bug reports are often sent upstream to GNOME or KDE[4]. The Fusion Linux developer, Valent Turkovic, said that his plan was for Fusion Linux developers to check reports of bugs and ask the user to file them in Fedora Bugzilla if the package was unchanged from Fedora, RPM Fusion Bugzilla if the package came from there, or with Fusion Linux's developers if the bug related to Fusion Linux-specific customizations.

Release criteria

Adam Williamson proposed a new release criterion[1] requiring the final release notes from the Documentation team be present in packaged form in the release repository (at Final release stage). Jesse Keating suggested similar criteria for artwork, spin-kickstarts and fedora-release packages[2]. Adam provided revised drafts for all three proposed criteria[3].

Testing new versions of anaconda

Mike Cloaked provided a very useful guide to creating a custom USB key to test new releases of anaconda when images containing that version of anaconda are not available[1]. Brian Lane said it was good to see someone else using his work, and pointed out that the script Mike used should also be able to produce a full, updated DVD ISO, but would take longer to do so.

Fedora QA retrospective

James Laska announced the QA retrospective page for Fedora 14[1]. The retrospective attempts to identify things that went well and things that went badly during the release cycle, to help the group improve with future releases. He appealed for contributions to the retrospective from anyone who could identify good or bad elements of the QA work for the Fedora 14 release.


Translation

This section covers the news surrounding the Fedora Translation (L10n) Project[1].

Contributing Writer: Runa Bhattacharjee

Fedora 14 Tasks

John Poelstra informed[1] in the list about the upcoming tasks for Fedora 14. As per the schedule, review and correction of the Final Translated Guides (i.e. daily build htmls), Website content and 0-day Release Notes is currently underway.

Updates to Various Modules of Fedora Websites

POT files for spins.fedoraproject.org[1] and the new fedoraproject.org[2] website content have been updated. Some last minute errors were fixed for the latter.

Publican 2.3 Released

Ruediger Landmann announced the release of Publican v2.3[1]. A number of bugs related to localization have been fixed in this version. Also, Release Notes have been made available for the first time with a Publican release. The updated packages of the new version are available on koji.

New Members and Sponsors in FLP

Balakrishnan K (Tamil)[1] and Andrey Panasyuk (Belorussian)[2] joined the FLP recently.

Design

In this section, we cover the Fedora Design Team[1].

Contributing Writer: Nicu Buculei

Icon Work

As a new contributor to the Design Team, Bryan Nielsen completed his first task[1] with guidance from Jakub Steiner "Thanks for all the assistance in putting this together, there were some gaps in my Inkscape and SVG knowledge and skills that have now been filled." After growing in experience he grew confidence to continue "I'm looking forward to taking on another ticket once this one is put to bed" and started working[2] on another icon "I quickly threw together a couple of hires mock ups that reuse existing components", again with Jakub's guidance[3] "Here's a few tips. Starting with a highres always leads to suboptimal metaphors. Think how you'd execute that at 16x16px."

Logo Work

Felipe Echeverria, new contributor to the Design Team, tackled[1] as his first task the logo/icon design for the blogging client Lekhonee, a ticket[2] open for a long time. He works with guidance[3] from Máirín Duffy "maybe rotate the pen on the right 90 degrees clockwise, so the two pen nibs make an 'L' for Lekhonee. But as they are now they make a great 'W' which makes me think of Wordpress so this may be entirely unnecessary" and advancing in subsequent iterations[4]

Mockup Work

Luya Tshimbalanga posted[1] his mockups for an Anaconda redesign "I started to work on initial Fedora installer mockup[1]. The concept is based on openSUSE first screen installer (GRUB) and uses design team default typeface", Máirín Duffy explained[2] is a bit early for this task before an usability study "I think it's fine to work through visual design ideas right now, but we haven't really begun a usability assessment of Anaconda so I also think it's a bit too early to start mocking up the UI screen-by-screen" and proposed[3] the Fedora 15 development cycle for this "Yep definitely, once F14 is out the door I definitely want to start working with the Anaconda team and post stuff here on-list as well as on the wiki."

Security Advisories

In this section, we cover Security Advisories from fedora-package-announce.

http://lists.fedoraproject.org/pipermail/package-announce

Contributing Writer: Pascal Calarco

Fedora 14 Security Advisories

none

Fedora 13 Security Advisories

Fedora 12 Security Advisories