From Fedora Project Wiki

Page title matches

Page text matches

  • File:FQA2.png
    Fedora Quality Assurance Header draft 2
    (468 × 60 (28 KB)) - 14:09, 3 November 2008
  • Architectures/ARM/Quality Assurance
    * [[Architectures/ARM/Quality Assurance/Rawhide |Rawhide Images]] * [[Architectures/ARM/Quality Assurance/2013-05-21-VFAD-Fedora 19 Beta RC2|Fedora 18 RC2]]
    3 KB (335 words) - 20:08, 9 August 2013
  • Development
    ...e mechanism gives the project goals for which to strive, while maintaining quality. == Quality Assurance ==
    1 KB (209 words) - 12:30, 18 September 2017
  • Byone
    * [[QA| Fedora Quality Assurance]] * Working on Quality Assurance for Localization (L10N) and Internationalization (I18N) in order to improve
    1 KB (172 words) - 21:49, 12 March 2011
  • QA/Draft
    = Fedora Quality Assurance = The Quality Assurance project is engaged in the following activities:
    2 KB (312 words) - 15:00, 9 February 2009
  • GCI 2012/Task Page
    ==Quality Assurance== {{Admon/tip|Tasks related to testing and ensuring code is of high quality}}
    2 KB (283 words) - 15:45, 3 November 2012
  • Joining EPEL
    == Testing and Quality Assurance == ...PEL_QA |EPEL QA]] page for information on helping with testing and quality assurance.
    2 KB (269 words) - 19:55, 6 January 2022
  • Spins Test Plans
    ...lives in [[:Category:LiveCD Test Cases]]. This list comes from the Quality Assurance Team, and may be extended with help of the Spins SIG, the Spin Maintainers ...late:QA/Test_Case]]) for every item that needs to be tested by the Quality Assurance Team.
    1 KB (177 words) - 14:41, 29 November 2010
  • JohnBabich/Sandbox/Releasenotes
    ...l10n) and internationalization (i18n), which result in comprehensive, high-quality release notes in a variety of languages. == Quality Assurance for Test Releases ==
    3 KB (531 words) - 16:31, 24 May 2008
  • QA/Contributors
    == Contributors to the Fedora Quality Assurance Team ==
    313 bytes (31 words) - 19:49, 9 November 2009
  • L10N/th
    == การรายงานบั๊ก การทดสอบ และทำ Quality Assurance ==
    13 KB (764 words) - 18:37, 6 December 2018
  • EPEL QA
    = EPEL Quality Assurance = EPEL strives to produce bug free and stable packages. Testing and Quality assurance is vital to this effort.
    2 KB (252 words) - 20:03, 6 January 2022
  • FWN/Beats/EventsMeetings
    === Fedora Quality Assurance Meeting 2008-MM-DD ===
    2 KB (160 words) - 21:35, 20 September 2016
  • SecuritySpin:QA Brainstorm
    This page is for brainstorming a Quality Assurance plan for the upcoming [[SecuritySpin]] based on [https://fedorahosted.org/s ...ine of the test cases and we can use them to format into an actual Quality Assurance plan at a later date.
    2 KB (253 words) - 01:14, 19 February 2010
  • Media Handout Requirements
    === Quality Assurance === * Must have an approved test plan on file with the Fedora Quality Assurance team
    3 KB (527 words) - 11:25, 12 June 2011
  • Artwork/EchoDevelopment
    '''Bug Reporting, Testing, and Quality Assurance''' Before filing a bug, please read through the list of [https://bugzilla.r
    988 bytes (134 words) - 02:39, 7 June 2013
  • Virtualization testing
    [[Category:Quality assurance]]
    1 KB (160 words) - 09:13, 23 January 2009
  • JosephJacksonIv
    * [[QA|Fedora Quality Assurance]]
    1 KB (101 words) - 21:04, 19 September 2016
  • GCI 2012/Task Page/QA
    '''Task related with Quality Assurance''' ** '''Tags :''' Quality Assurance
    4 KB (569 words) - 20:56, 19 September 2016
  • Category:Fonts and text QA
    ...ture}} [[Category:Fonts SIG|QA]] [[Category:BugTriage]] [[Category:Quality assurance]]
    8 members (0 subcategories, 0 files) - 19:08, 27 June 2008
  • Releases/8/Test/F8Test1/ReleaseNotes
    == Quality Assurance for Test Releases == The Fedora Project has a process in place for ensuring the highest possible quality even in our test releases. Many bugs are identified, prioritized and fixed
    4 KB (677 words) - 21:31, 19 September 2016
  • Kadischi/BugReporting
    | '''Bug Reporting, Testing, and Quality Assurance''' BR
    2 KB (287 words) - 16:33, 24 May 2008
  • Go No Go Meeting
    ...meeting representatives from Development, Release Engineering, and Quality Assurance should be clearly identified ...D'' by a representative from Development, Release Engineering, and Quality Assurance.
    3 KB (446 words) - 20:38, 12 October 2017
  • F7Test1/ReleaseNotes
    == Quality Assurance for Test Releases == The Fedora Project has a process in place for ensuring the highest possible quality even in our test releases. Many bugs are identified, prioritized and fixed
    5 KB (723 words) - 20:41, 19 September 2016
  • F7Test2/ReleaseNotes
    == Quality Assurance for Test Releases == The Fedora Project has a process in place for ensuring the highest possible quality even in our test releases. Many bugs are identified, prioritized and fixed
    7 KB (1,000 words) - 04:24, 26 February 2009
  • QA
    = Fedora Quality Assurance = ...he software that makes up Fedora. It's our goal to continually improve the quality of Fedora releases and updates.
    5 KB (776 words) - 12:42, 18 January 2024
  • Category:QA SOPs
    This page documents the Standard Operating Procedures for the Fedora Quality Assurance (QA) team.
    20 members (0 subcategories, 0 files) - 21:53, 28 July 2011
  • Test Day:2009-10-01 Draft Anaconda/Features/StorageFiltering
    * Quality Assurance - [[User:Jlaska|James Laska]]
    1 KB (192 words) - 08:42, 18 September 2009
  • JohnBabich/Meetings
    [[QA/Meetings| Quality Assurance (QA)]]
    2 KB (201 words) - 16:33, 24 May 2008
  • QA/ko
    = Fedora Quality Assurance = ...he software that makes up Fedora. It's our goal to continually improve the quality of Fedora releases and updates.
    5 KB (736 words) - 13:08, 7 April 2021
  • F7Test3/ReleaseNotes
    == Quality Assurance for Test Releases == The Fedora Project has a process in place for ensuring the highest possible quality even in our test releases. Many bugs are identified, prioritized and fixed
    6 KB (901 words) - 20:41, 19 September 2016
  • F7Test4/ReleaseNotes
    == Quality Assurance for Test Releases == The Fedora Project has a process in place for ensuring the highest possible quality even in our test releases. Many bugs are identified, prioritized and fixed
    6 KB (990 words) - 20:42, 19 September 2016
  • L10N
    == Bug Reporting, Testing, and Quality Assurance == Joining this event allows the participants to improve the translation quality for the final release without waiting for next available release.
    9 KB (1,356 words) - 18:15, 25 June 2021
  • Releases/21/Schedule/ko
    ...tp://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html Quality Assurance]
    2 KB (237 words) - 11:44, 18 September 2016
  • Releases/8/Test/F8Test2/ReleaseNotes
    == Quality Assurance for Test Releases == The Fedora Project has a process in place for ensuring the highest possible quality even in our test releases. Many bugs are identified, prioritized and fixed
    6 KB (969 words) - 21:31, 19 September 2016
  • Test Day:2009-10-29cancelled
    * Quality Assurance - [[User:amacerek]]
    2 KB (332 words) - 08:54, 16 October 2009
  • Releases/21/Schedule
    ...ps://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html Quality Assurance]
    3 KB (361 words) - 03:42, 7 December 2014
  • Releases/12
    ...//poelstra.fedorapeople.org/schedules/f-12/f-12-quality-tasks.html Quality Assurance]
    3 KB (362 words) - 18:50, 8 November 2011
  • Smolt
    ...ux, and submits them to a central server for statistical purposes, quality assurance and support. It was initiated by Fedora, with the release of Fedora 7 and i
    2 KB (278 words) - 05:56, 13 August 2019
  • L10N/fa
    == Bug Reporting, Testing, and Quality Assurance == Joining this event allows the participants to improve the translation quality for the final release without waiting for next available release.
    10 KB (1,313 words) - 10:23, 20 May 2020
  • GSOC 2013/Student Application Blaskovic
    ...thesis. From February 2012 I am working in Red Hat Brno office in Quality Assurance team (internship).
    1 KB (219 words) - 16:26, 2 May 2013
  • Test Day:2008-09-25 FirstAidKit
    * Quality Assurance - [[User:jlaska]], [[User:wwoods]]
    2 KB (272 words) - 19:43, 26 June 2015
  • Releases/22/Schedule/es
    ...tp://fedorapeople.org/groups/schedule/f-22/f-22-quality-tasks.html Quality Assurance]
    3 KB (346 words) - 06:28, 26 February 2015
  • QA/it
    = Fedora Quality Assurance = Il progetto Quality Assurance è impegnato nelle seguenti attività:
    4 KB (576 words) - 14:55, 29 January 2016
  • Releases/13/Schedule
    ...//poelstra.fedorapeople.org/schedules/f-13/f-13-quality-tasks.html Quality Assurance]
    3 KB (416 words) - 18:48, 8 November 2011
  • Releases/14/Schedule
    ...//poelstra.fedorapeople.org/schedules/f-14/f-14-quality-tasks.html Quality Assurance]
    3 KB (415 words) - 22:26, 13 December 2011
  • Releases/22/Schedule
    ...tp://fedorapeople.org/groups/schedule/f-22/f-22-quality-tasks.html Quality Assurance]
    3 KB (426 words) - 19:04, 9 April 2015
  • QAChecklist
    This is a list of things to check for within a src.rpm during Quality Assurance testing of Fedora packages. It is to be understood as inspiration. Not ev
    4 KB (585 words) - 16:38, 24 May 2008
  • Test Day:2013-03-28 Gnome 3.8
    * Quality Assurance - [[User:Vbenes|Vladimír Beneš]] (vbenes)
    3 KB (355 words) - 06:11, 26 December 2014
  • Features/QA
    = Quality Assurance =
    3 KB (502 words) - 18:21, 4 November 2008
View (previous 50 | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://fedoraproject.org/wiki/Special:Search"