Search results

This template is used to produce multiple upgrade test cases for release validation testing, found at [[Template:Installation_test_matri ...conditionalized, based on template parameters, to let you produce the test cases that cover upgrading from different configurations.

** Modify {{package|kwin}} to switch to Wayland *** Make {{package|kwin}} require <code>kwin-wayland</code> and recommend <code>kwin-x11</code

...cerns, send mail to [https://admin.fedoraproject.org/mailman/listinfo/test test@lists.fedoraproject.org]. ...it's still pretty good: it shows the way to improve my knowledge about the test proces.

...ult for Plasma. We will also attempt to automatically fall back to Xorg in cases where wayland is unavailable (like nvidia). There will still be option to u ...release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue

...page records [[QA:Desktop_validation_testing|desktop validation testing]] test results for the Fedora '''14 Final RC#1''' release. == How to test ==

== '''Test Matrix''' == ! Milestone !! Test Case !! [[Workstation]] !! [[KDE]]

== '''Test Matrix''' == ! Milestone !! Test Case !! [[Workstation]] !! [[KDE]]

=== Rawhide as Test Ground === ...than shipping an incomplete port.) There will also be an atlantikdesigner package built from the KDE 3 kdeaddons, or we might just keep kdeaddons 3.5 entirel

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

== '''Test Matrix''' == ! Milestone !! Test Case !! [[Workstation]] !! [[KDE]]

* '''Proposal owners:''' Update the <tt>fedora-release</tt> package with subpackages for the various non-edition outputs. The "convert-to-editi ...eng/issue/7499 #7499] Release Engineering owns the <tt>fedora-release</tt> package.

...kde-workspace, or move it to a subpackage that would conflict with kscreen package and ensure that kscreen is installed by default. == How To Test ==

...ains all the exciting features of Fedora 19 in a form that anyone can help test. This testing, guided by the [[QA|Fedora QA team]], helps us target and ide ...ating new features and pushing fixes [https://docs.fedoraproject.org/en-US/package-maintainers/Staying_Close_to_Upstream_Projects/ upstream] as much as feasib

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

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

...ng an installed system (e.g. installer updates, or GNOME/Plasma updates to test the live images). The second is to produce a compose that can be released: ...composes can be requested prior to the freeze date if they are required to test one or more updates before they can be pushed stable, but ideally this shou

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

...Assistant provides an easy method for developers to start new projects via package sets by language (currently C, Java, and Python). A new project can take ad ...arted with templates and samples, code with the appropriate toolchain, and package and distribute your creations.''

...d normal disks (or with FW RAID turned off) shouldn't be affected. In most cases, you can use the UEFI boot menu as a workaround. Different systems (differe <li>First, make sure your libhif package version is the same as described above or newer:

* bltk with various user cases Also a new package will be able to set the power saving levels: