Search results

This page provides the results of testing guest operating systems on a Fedora 17 KVM There are 4 test cases to be evaluated against each guest OS:

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''(VERSION) (PRE-RELEASE)''' release. == How to test ==

|Create |{{result|pass|vondruch}} [https://bugzilla.redhat.com/show_bug.cgi?id=838801 838801]

This page provides a high-level roadmap for implementing the [[Is_anaconda_broken_pro ...teria <ref>[[Fedora Release Criteria]]</ref>. This includes adjusting the test case priority to match milestone criteria.

This page is intended to record [[QA:Fedora_13_Install_Test_Plan]] test results for the '''Final RC2''' milestone. This page tracks test results against the Fedora 13 '''Final RC2''' build. Test results against other Fedora 13 milestones can be found at [[:Category:Fedo

| name = Upgrade Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

| name = Cloud/Atomic Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

This page is intended to record [[QA:Fedora_13_Install_Test_Plan]] test results for the '''Final RC3''' milestone. This page tracks test results against the Fedora 13 '''Final RC3''' build. Test results against other Fedora 13 milestones can be found at [[:Category:Fedo

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create .

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create .

| name = Fedora 21 Server Test Day ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create .

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create .

| name = Fedora Test Days | caption = OpenStack Test Day

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create.

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create.

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create .

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create .

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create .

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create.

This page is intended to record [[QA:Fedora_16_Install_Test_Plan]] test results for the '''Fedora 16 Final RC3''' milestone. ...s can be found at [[:Category:Fedora_16_Test_Results]]. The explanation of test case priority is available at [[QA:Fedora_16_Install_Test_Plan#Test_Priorit

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create .

#Copy the below tests and results chart to a page that you create . #Check the boot result:

#Copy the below tests and results chart to a page that you create . #Check the boot result:

#Copy the below tests and results chart to a page that you create . #Check the boot result:

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

| name = Cloud Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

#Copy the below tests and results chart to a page that you create . #Check the boot result:

#Copy the below tests and results chart to a page that you create . #Check the boot result:

#Copy the below tests and results chart to a page that you create. #Check the boot result:

#Copy the below tests and results chart to a page that you create . #Check the boot result:

#Copy the below tests and results chart to a page that you create. #Check the boot result:

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create.

...if the image is ready. Please include the categories at the bottom of the page. #Copy the below tests and results chart to a page that you create.

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

#Copy the below tests and results chart to a page that you create . #Check the boot result:

#Copy the below tests and results chart to a page that you create. #Check the boot result:

#Copy the below tests and results chart to a page that you create. #Check the boot result:

...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) == What to test? ==

| name = Fedora Test Days ...ing-48px.png|link=https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day]]

* We do not create easily exploitable security vulnerabilities When adding a user or group at package install-time, there are four system states:

| name = Fedora Test Days ...ing-48px.png|link=https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day]]

#Copy the below tests and results chart to a page that you create . #Check the boot result:

| name = Cloud Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

...[[QA:Fedora_15_Install_Test_Plan]] test results for the '''Fedora 15 Alpha Test Compose 1''' milestone. ...s can be found at [[:Category:Fedora_15_Test_Results]]. The explanation of test case priority is available at [[QA:Fedora_15_Install_Test_Plan#Test_Priorit

...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) === What to test? ===

This is the test result page for Versatile Express + XFCE ARMHFP. #Check the boot result:

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

{{admon/caution|Draft|This page is only draft, and will change in time.}} * <code>testplan_url</code> ~ link to wiki page with metadata (usefull for frontends)

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

==Test Results== #Copy the below tests and results chart to a page that you create .

| name = Fedora Test Days | caption = Cockpit Test Day

<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name. This keeps all fea ...HE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

|Create |{{result|pass|}} [https://bugzilla.redhat.com/1207280 1207280]

| name = Fedora Test Days | caption = Cockpit Test Day

...is page provides guidance on arranging and announcing a release validation test event. For any concerns, please contact the [[QA]] group. ...n/caution|This process is now automated|The creation of release validation test events is now automated. Wiki pages are created and an announcement email s

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

Please join us on Thursday, 20 December as we test all available images to be used in the Fedora 18 Beta TC3. All can particip ===Test Instructions===

| name = Cloud Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

...e is intended to record [[QA/TestPlans/Fedora10Install|Fedora 10 Install]] test results for the Preview milestone. ...divided up by architecture, please be sure to record the appropriate test result with the corresponding architecture.

| name = Fedora Test Days | caption = Virtualization Test Day

Please join us on Friday, 01 Febuary as we test all available images to be used in the Fedora 18 RC1. All can participate - ===Test Instructions===

Please join us on Friday, 01 Febuary as we test all available images to be used in the Fedora 18 RC1. All can participate - ===Test Instructions===

Please join us on Monday October 15th as we test all available images to be used in the Fedora 18 TC1. All can participate - ===Test Instructions===

Please join us on Friday October 26th as we test all available images to be used in the Fedora 18 Alpha RC1. All can partici ===Test Instructions===

| name = Fedora Test Days ...ing-48px.png|link=https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day]]

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...ced Inscript standard which is in draft currently. This standard allows to create a new keymap with a design policy which would retain the major features of

| name = Fedora Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

| name = Cloud Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

Please join on Friday June 15th as we test all available images to be used in the Fedora 17 ARM RC1. All can participa ===Test Instructions===

| name = Fedora Test Days | caption = OpenStack Test Day

...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) = What to test? =

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

| name = Fedora Test Days ...ing-48px.png|link=https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day]]

| name = Fedora CoreOS Test Week | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. All can participa ===Test Instructions===

| name = Cloud/Atomic Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

Please join us on Tuesday, 21 May as we test all available images to be used in the Fedora 19 RC2. All can participate - ===Test Instructions===

#Copy the below tests and results chart to a page that you create . #Check the boot result:

Please join us on Monday December 3rd as we test all available images to be used in the Fedora 18 Beta TC1. All can particip ===Test Instructions===

| name = Cloud Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu GNOME Color Manager is a session framework that makes it easy to manage, install and generate color profiles in the GNOME desktop.

#Copy the below tests and results chart to a page that you create . #Check the boot result:

| name = Fedora Test Days | caption = SPICE Test Day

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) ...the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}

...able user to perform tiny installation. This installation is later used to create minimalistic server or desktop appliance. *# making the anaconda text mode minimal install match

{{draft|<br/>Page may contain inaccurate info, outated results, and traces of nuts.}} ...e is intended to record [[QA/TestPlans/Fedora10Install|Fedora 10 Install]] test results for the Beta milestone.

| name = Cloud/Atomic Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) === What to test? ===

| name = Fedora Test Day | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

= Additional buildroot to test x86-64 micro-architecture update = Create a dedicated buildroot to test packages built with x86-64 micro-architecture update.

| name = OpenStack Test Day ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day, webirc])

...is intended to record [[QA/TestPlans/Fedora10Install| Fedora 10 Install]] test results for the Alpha milestone. ...divided up by architecture, please be sure to record the appropriate test result with the corresponding architecture.

| name = Cloud Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. -->

| name = Cloud/Atomic Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

| name = Fedora CoreOS Test Week | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

...HE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> ...www.ralinktech.com/en/04_support/support.php?sn=501 Ralinktech's site] and create the patches needed to add support for the device id of this device as well

Please join on Friday June 15th as we test all available images to be used in the Fedora 17 ARM RC1. All can participa ===Test Results===

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

Only create "host-only" initramfs images. A generic fallback image will be generated, i ...tramfs, which takes a long time to load on system start and a long time to create on kernel updates.

<!--This should link to your home wiki page so we know who you are--> ...HE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->

...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) === What to test? ===

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

Install apache and mod_wsgi using [[dnf|DNF]] or [[yum|YUM]]: dnf|yum install httpd mod_wsgi

...rite. The entire storage subsystem was rewritten from scratch in F11, this page tracks the cleanup and last bits of support. ...tracks progress. It also documents the storage device filtering design and test requirements.

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

| name = OpenStack Test Days ...the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}

| name = Fedora Test Day | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

...what it will do. This information is used for the overall feature summary page for each release. --> <!--This should link to your home wiki page so we know who you are-->

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

| name = Fedora Test Day | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

This should link to your home wiki page so we know who you are. <!-- When your change proposal page is completed and ready for review and announcement -->

| name = Fedora Test Days | website = [http://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day Fedora Calendar]

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

...what it will do. This information is used for the overall feature summary page for each release. --> ...lity to re-test installed [[Perl]] packages by automatically providing the test suites of each package in a "perl-Foo-tests" subpackage, and providing a fr

| name = Silverblue Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. -->

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. -->

| name = Fedora Test Days ...ing-48px.png|link=https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day]]

* Multiple Python versions — 2.6, 2.7, 3.3, 3.4 and 3.5 — to help run test suites across several Python configurations, as well as PyPy, PyPy3, and Jy ...e Certificate Authorities''': FreeIPA Certificate Authority now is able to create subordinate CAs to issue certificates with a specific scope.

This is a page detailing my personal mock setup, intended for local package testing and Ex ...dencies, and for customizing the buildroot. Creating a local repo is easy. Create the directory tree:

...at http://wiki.xensource.com/xenwiki/ and the Fedora [[Tools/xen| Xen]] page. ...ate version of the [[FedoraXenQuickstart| Fedora Core 4 Xen Quick Start]] page. A number of things have changed since FC4 and Xen 2 such as package names

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

| name = Fedora Test Day | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. -->

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu <!--This should link to your home wiki page so we know who you are-->

...disk image to be accidentally added to two different virtual machines. The result of such a mistake is likely to be catastrophic destruction of the virtual m ...ce the risk that a virtual machines' disk image will become corrupted as a result.

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

...what it will do. This information is used for the overall feature summary page for each release. --> Create a collection of software that provides an out-of-the-box usable robotic sim

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

...''test suite'' (including framework) and the CI system that is running the test suite. This is the standard interface. ...e integration tests, both Fedora QA and the Atomic Host team would like to create more integration tests, Red Hat would like to bring integration tests upstr

<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name. This keeps all fea ...what it will do. This information is used for the overall feature summary page for each release. -->

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name. This keeps all fea <!--This should link to your home wiki page so we know who you are-->

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

<!--This should link to your home wiki page so we know who you are--> == How To Test ==

...''test suite'' (including framework) and the CI system that is running the test suite. This is the standard interface. ...e integration tests, both Fedora QA and the Atomic Host team would like to create more integration tests, Red Hat would like to bring integration tests upstr

| name = Fedora Test Days | caption = Virtualization Test Day

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

This should link to your home wiki page so we know who you are. ...accepted by FESCo, tracking bug is created in Bugzilla and linked to this page

| name = Fedora Test Days | caption = Virtualization Test Day

...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) == What to test ==

| name = Upgrade Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

...installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release # Test [[Releases/19/FeatureList|accepted features of {{FedoraVersion|long|19}}]]

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

This page is intended to gather feedback from the Fedora [[QA]] community on things t ...cerns, send mail to [https://admin.fedoraproject.org/mailman/listinfo/test test@lists.fedoraproject.org].

<!--This should link to your home wiki page so we know who you are--> ...e the consistency of the user experience between installation and the post-install environment.

<!--This should link to your home wiki page so we know who you are--> ...HE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->

| name = Fedora Test Days | caption = Sugar Desktop Test Day

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- When your change proposal page is completed and ready for review and announcement -->

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name. This keeps all fea ...what it will do. This information is used for the overall feature summary page for each release. -->

This document describes the test process by which Fedora 10 will be verified for operation consistent to tha * Organize a community test effort

| name = Fedora Test Week | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

| name = Fedora CoreOS Test Week | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

...ing tests for [[AutoQA]]. There's four parts to a test: the test code, the test object, the Autotest control file, and the AutoQA control file. Typically t ...test or autoqa. This page outlines the process of integrating an existing test into [[AutoQA]].}}

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

<!--This should link to your home wiki page so we know who you are--> ...accepted by FESCo, tracking bug is created in Bugzilla and linked to this page

...equest to the design team, and details on a new custom blog aggregator, to create a .planet file just for the Art team. This week's issue completes with sec ...re interested in contributing to Fedora Weekly News, please see our 'join' page<ref>http://fedoraproject.org/wiki/NewsProject/Join</ref>. We welcome reader

This should link to your home wiki page so we know who you are. ...accepted by FESCo, tracking bug is created in Bugzilla and linked to this page

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene This should link to your home wiki page so we know who you are.

This page is intended to gather feedback from the Fedora [[QA]] community on things t ...d mail to [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list@redhat.com].

...be incomplete. Please use the dracut.cmdline.7 (alias dracut.kernel.7) man page or point your browser at /usr/share/doc/dracut-*/dracut.html}} .../pub/linux/utils/boot/dracut/dracut.html#dracut.kernel dracut.kernel.7 man page].

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. -->

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

...accepted by FESCo, tracking bug is created in Bugzilla and linked to this page ...for rpmdb (and similar databases) is discussed in the thread, with the end result being `/usr/lib/sysimage/rpm`.

| name = Fedora Test Days | caption = Virtualization Test Day

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps = POWER 4KiB page size =

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene

This should link to your home wiki page so we know who you are. <!-- When your change proposal page is completed and ready for review and announcement -->

...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene This should link to your home wiki page so we know who you are.

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. -->

<!-- Make sure the pages is named as "Test Day:YYYY-MM-DD topic" --> | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

| name = Fedora Test Day | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all featu ...what it will do. This information is used for the overall feature summary page for each release. -->

...st name, name on PyPI) in the canonical format<ref name="canonical" /> and create a virtual Provides tag with the value <code>pythonX.Ydist(CANONICAL_NAME)</ ...hat it will do. This information is used for the overall changeset summary page for each release. -->

This page is intended to gather feedback from the Fedora [[QA]] community on things t ...cerns, send mail to [https://admin.fedoraproject.org/mailman/listinfo/test test@lists.fedoraproject.org].

<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name. This keeps all fea ...what it will do. This information is used for the overall feature summary page for each release. -->

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

...accepted by FESCo, tracking bug is created in Bugzilla and linked to this page By providing this software to them in a pre-packaged, ready to install Lab image, we hope to enable their work.

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release.

| name = '''Kernel 6.8 Test Week''' | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release.

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene

...read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSA <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

| name = Fedora Test Day | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

...read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSA <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

...</th><td class="text" style="color: #407a40">| so getting something like a test case/plan tracker, or bugzilla metroid tracker, or similar web-based tester ...we do have software coming down teh pike for test case management and test result management</td><td class="time"><a href="#tMay 21 11:19:31" class="time">Ma

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene

...ll update the Test Day SOP as agreed (encourage use of webapp for tracking test day results)'' - this was [https://fedoraproject.org/w/index.php?title=QA%2 * adamw noted that it was Graphics Test Week and asked people to help out with testing

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...oot), kickstart (bootloader --sdboot) such that the "everything" media can install a grub free machine.

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene

...useful, except when it's slow. zram is a RAM drive that uses compression. Create a swap-on-zram during start-up. And no longer use swap partitions by defaul ...ce, typically <span style=color:brown>/dev/zram0</span>, has a size set at create time during early boot, by zram-generator† per its configuration file. Th

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. -->

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. -->

...read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSA <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

The correct way to make changes to them is to create a file with the same name in the "/etc/systemd/system/" directory. Files he Active: failed (Result: exit-code) since Wed 2019-08-28 08:28:33 EDT; 1min 9s ago

This page is intended to help packagers manage existing or future packages that embed === Is this page a Fedora guideline? ===

...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) ...the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release.

<!-- When your change proposal page is completed and ready for review and announcement --> <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move

| name = '''Kernel 6.5 Test Week''' | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

'''8.''' Test a scratch build, and wait for it to complete. ...unexpected failures. A list of known failures is kept at the end of this page, and should be updated as needed.

| name = Fedora Test Week | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

...re interested in contributing to Fedora Weekly News, please see our 'join' page<ref>http://fedoraproject.org/wiki/NewsProject/Join</ref>. We welcome reader ...tes to the fonts packaging guidelines, and re-packaging of many fonts as a result.

.... The initial survey is available [https://www.redhat.com/archives/fedora-test-list/2009-June/msg00160.html here] and included below. The Fedora QA team would like your feedback on Fedora 11 Test Days. You

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release.

...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene This should link to your home wiki page so we know who you are.

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release.

This page outlines the plan to make Fedora the preferred environment of choice for Ja .../www.slideshare.net/CharlesNutter/euruko-2012-jruby/58]. This boost is the result of numerous optimizations made by the JVM, the most significant of which is

| name = '''Kernel 6.6 Test Week''' | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps = Create Fedora Windows Subsystem for Linux Images =

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps This should link to your home wiki page so we know who you are.

...what it will do. This information is used for the overall feature summary page for each release. --> <!--This should link to your home wiki page so we know who you are-->

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- When your change proposal page is completed and ready for review and announcement -->

on his machine without having to install policy sources. semanage is the command line tool for doing this. It's man page describes the tool as the following:

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene This should link to your home wiki page so we know who you are.

...read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSA <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

This should link to your home wiki page so we know who you are. <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. -->

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release.

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release.

...and the [[QA:Update_feedback_guidelines|update feedback guidelines]]. This page specifically covers the update submission process. ...single multi-package update, such that no user will face problems if they install all the packages in the update together.