Search results

Page title matches

• Category:Features with incomplete test plans
  This is a category for features whose "How To Test" section does not meet QA standards. ...for the "How To Test" section. This information is included in the page [[Features/EmptyTemplate]].
  1 member (0 subcategories, 0 files) - 03:26, 26 February 2009

Page text matches

• Category:QA approved feature pages
  ...complete scope]] and [[:Category:Features with incomplete test plans]] for features which didn't make the grade.
  4 members (0 subcategories, 0 files) - 19:53, 22 January 2009
• Category:Features needing QA approval
  ...tures with incomplete scope]] or [[:Category:Features with incomplete test plans]]. Or both. [[Category:Features]]
  0 members (0 subcategories, 0 files) - 03:25, 26 February 2009
• Features/F10PolicyReview
  * Current policy http://fedoraproject.org/wiki/Features/Policy ...and constructive suggestions for improvement for a one week period ending with a FESCo vote to ammend the existing policy as directed or leave it as it is
  2 KB (317 words) - 17:03, 3 July 2008
• Features/DBusPolicy
  ...open, and a number of applications relied on this and shipped incorrect or incomplete policy files in <tt>/etc/dbus-1/system.d</tt>. == Test Plan ==
  3 KB (373 words) - 07:39, 5 March 2009
• Architectures/ARM/Fedora 18 Beta Release Criteria
  ..._Policy|code complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle # Finish testing [[Releases/18/FeatureList| Fedora 18 Features]]
  4 KB (573 words) - 19:35, 9 August 2012
• Architectures/ARM/Quality Assurance/Beta Release Criteria
  *In most cases, the installed system must be able to play back sound with gstreamer-based applications (see Blocker_Bug_FAQ), if supported audio outp **Cannot be fixed with a future stable update 
  3 KB (477 words) - 18:04, 8 August 2012
• Architectures/ARM/Quality Assurance/Alpha Release Criteria
  ...o publicly release ready-to-run image media versions of a feature complete test release, which will run on: ...ion process as clear and straightforward as possible. Mostly met items are incomplete until they are met. Optional and nice to have items should not be included
  7 KB (1,041 words) - 19:51, 8 August 2012
• Architectures/ARM/Fedora 18 Final Release Criteria
  ...on process as clear and straightforward as possible. Mostly  met items are incomplete until they are met. Optional and nice to have  items should not be include ...rity of the case when  the issue is encountered, and the ease or otherwise with which the issue  can be avoided by both informed and uninformed users.
  6 KB (966 words) - 19:48, 9 August 2012
• Architectures/ARM/Fedora 18 Alpha Release Criteria
  ...o publicly release ready-to-run image media versions of a feature complete test release, which will run on: ...ion process as clear and straightforward as possible. Mostly met items are incomplete until they are met. Optional and nice to have items should not be included
  7 KB (1,076 words) - 20:30, 9 August 2012
• Architectures/ARM/Quality Assurance/Final Release Criteria
  ...on process as clear and straightforward as possible. Mostly  met items are incomplete until they are met. Optional and nice to have  items should not be include ...rity of the case when  the issue is encountered, and the ease or otherwise with which the issue  can be avoided by both informed and uninformed users.<br>
  6 KB (926 words) - 18:11, 8 August 2012
• Fedora 13 Alpha Release Criteria
  ...installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release # Test [[Releases/13/FeatureList|accepted features of {{FedoraVersion|long|13}}]]
  5 KB (706 words) - 18:09, 18 June 2010
• Meeting:CommOps 2016-06-28
  ...everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask. ** #info === "Friends. Features. Freedom. First. Forever." ===
  8 KB (1,246 words) - 17:21, 28 June 2016
• Fedora 13 Beta Release Criteria
  ..._Policy|code complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle # Finish testing [[Releases/13/FeatureList| Fedora 13 Features]]
  5 KB (755 words) - 23:09, 28 June 2010
• Fedora 14 Alpha Release Criteria
  ...installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release # Test [[Releases/14/FeatureList|accepted features of {{FedoraVersion|long|14}}]]
  5 KB (816 words) - 18:23, 7 October 2010
• Fedora 14 Beta Release Criteria
  ..._Policy|code complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle # Finish testing [[Releases/14/FeatureList| Fedora 14 Features]]
  6 KB (842 words) - 20:37, 26 November 2010
• Features/ControlGroups
  tasks, and all their future children, into hierarchical groups with A *cgroup* associates a set of tasks with a set of parameters for one
  13 KB (1,937 words) - 13:26, 28 March 2012
• User:Adamwill/Draft Beta criteria revision
  ..._Policy|code complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle # Finish testing [[Releases/15/FeatureList| Fedora 15 Features]]
  6 KB (970 words) - 20:01, 17 March 2011
• Fedora 15 Beta Release Criteria
  ..._Policy|code complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle # Finish testing [[Releases/15/FeatureList| Fedora 15 Features]]
  6 KB (983 words) - 19:27, 29 March 2011
• Fedora 15 Alpha Release Criteria
  ...installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release # Test [[Releases/15/FeatureList|accepted features of {{FedoraVersion|long|15}}]]
  7 KB (1,121 words) - 19:25, 29 March 2011
• User:Adamwill/Draft Alpha criteria revision
  ...installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release # Test [[Releases/15/FeatureList|accepted features of {{FedoraVersion|long|15}}]]
  7 KB (1,121 words) - 19:45, 17 March 2011