From Fedora Project Wiki

Page title matches

Page text matches

  • == 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
  • | '''Bug Reporting, Testing, and Quality Assurance''' BR
    2 KB (287 words) - 16:33, 24 May 2008
  • ...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
  • == 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
  • == 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
  • = 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
  • 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
  • * Quality Assurance - [[User:Jlaska|James Laska]]
    1 KB (192 words) - 08:42, 18 September 2009
  • [[QA/Meetings| Quality Assurance (QA)]]
    2 KB (201 words) - 16:33, 24 May 2008
  • = 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
  • == 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
  • == 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
  • == 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
  • ...tp://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html Quality Assurance]
    2 KB (237 words) - 11:44, 18 September 2016
  • == 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
  • * Quality Assurance - [[User:amacerek]]
    2 KB (332 words) - 08:54, 16 October 2009
  • ...ps://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html Quality Assurance]
    3 KB (361 words) - 03:42, 7 December 2014
  • ...//poelstra.fedorapeople.org/schedules/f-12/f-12-quality-tasks.html Quality Assurance]
    3 KB (362 words) - 18:50, 8 November 2011
  • ...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
  • == 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
View ( | ) (20 | 50 | 100 | 250 | 500)