From Fedora Project Wiki
Page title matches
- 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
- ...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
- ...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
- * 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 is2 KB (317 words) - 17:03, 3 July 2008
- ...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
- ..._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
- *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 update3 KB (477 words) - 18:04, 8 August 2012
- ...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 included7 KB (1,041 words) - 19:51, 8 August 2012
- ...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
- ...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 included7 KB (1,076 words) - 20:30, 9 August 2012
- ...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
- ...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
- ..._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
- ...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
- ..._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
- tasks, and all their future children, into hierarchical groups with A *cgroup* associates a set of tasks with a set of parameters for one13 KB (1,937 words) - 13:26, 28 March 2012
- ..._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
- ...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
- ...on Shell System provides an easy to use interactive command line interface with a standardized syntax to manage your system. ...e [https://github.com/agrover/configshell-fb python-configshell] framework with a standardized syntax to manage your system. It consists of the command <co11 KB (1,491 words) - 15:56, 12 February 2013
- ...28, Fedora will provide a new set of repositories for software and updates with alternative versions from those shipped in the default release. ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.11 KB (1,780 words) - 14:35, 2 March 2018
- ...eorganization of the Xen git tree for the dom0 kernel. Our issue wraps up with news from the KDE SIG, including details on the expected feature set for Fe ...erested, please join the list and let us know how you would like to assist with this effort.35 KB (5,265 words) - 14:51, 5 October 2009