From Fedora Project Wiki

  • == '''Test Matrix''' == ! Milestone !! Test Case !! [[Workstation]] !! [[KDE]]
    18 KB (2,376 words) - 23:01, 4 May 2022
  • The installed size of each package is : ! Package !! Installed Size
    6 KB (866 words) - 16:29, 19 April 2021
  • ...iles contained within each package, are unnecessary in the majority of use cases. Additionally, these metadata files can be large in size, leading to a sign As DNF is integral to various infrastructure tasks like package building and installation, testing environment creation, and server integra
    12 KB (1,819 words) - 12:34, 9 February 2024
  • ...''test suite'' (including framework) and the CI system that is running the test suite. This is the standard interface. ...is a standard way to discover, package and invoke integration tests for a package stored in a Fedora dist-git repo.
    14 KB (2,062 words) - 12:51, 26 July 2017
  • * It would be by far the largest mass package change we would ever have attempted. ...ge. If queried, rpm will show the group as "Unspecified" for every binary package in the distribution instead of just the majority of them. It is theoretica
    7 KB (1,164 words) - 21:09, 7 September 2018
  • ...the next release information, rpmautospec relies on the git history of the package. This information is extracted from the package repository when run as a koji plugin or locally (e.g. using fedpkg).
    9 KB (1,404 words) - 15:54, 18 June 2021
  • ...''test suite'' (including framework) and the CI system that is running the test suite. This is the standard interface. ...is a standard way to discover, package and invoke integration tests for a package stored in a Fedora dist-git repo.
    14 KB (2,163 words) - 16:20, 30 January 2018
  • | name = Fedora Test Days | website = [[http://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day Fedora Calendar]]
    18 KB (2,455 words) - 21:44, 19 September 2016
  • ...to distinguish between short-lived instances (like temporary containers or test machines) and actual installations. ...week, "3" the third week, and so on. This will let us sort out short-lived test or CI infrastructure machines and get a better picture of how systems are u
    7 KB (1,078 words) - 19:45, 29 August 2019
  • ...it applications on x86_64). Dropping i686 architecture support from a leaf package will no longer be considered a breaking change, will not require any announ ...6, not even RPM repositories for i686 are published any longer. The kernel package itself also [[Changes/Stop Building i686 Kernels|dropped support for i686]]
    12 KB (1,934 words) - 11:02, 24 August 2022
  • ...''test suite'' (including framework) and the CI system that is running the test suite. This is the standard interface. ...is a standard way to discover, package and invoke integration tests for a package stored in a Fedora dist-git repo.
    16 KB (2,281 words) - 09:07, 10 July 2017
  • | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]
    8 KB (1,220 words) - 03:43, 21 April 2017
  • | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]
    19 KB (2,724 words) - 09:23, 27 September 2018
  • DNF5 can be used in most cases during container builds (Containerfile/Dockerfiles) for a familiar UX, init ...ionally to DNF we will still provide '''rpm-ostree''' as the main tool for package layering on the client side and '''bootc''' to manage transactional, in-pla
    16 KB (2,643 words) - 17:22, 7 May 2024
  • ...of package management in Fedora. The new package manager (provided by dnf5 package) has ambitions to provide all major features of DNF without losing its mini The new package manager (DNF5) will provide huge improvements and in some cases better behavior than DNF. In the future, the new Microdnf will replace DNF.
    18 KB (2,853 words) - 19:27, 21 February 2024
  • | name = Upgrade Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]
    17 KB (2,220 words) - 05:44, 16 December 2021
  • ...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee
    40 KB (5,259 words) - 15:05, 17 June 2016
  • ..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i
    32 KB (4,510 words) - 17:20, 5 April 2017
  • ..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i
    32 KB (4,506 words) - 00:10, 12 October 2017
  • | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]
    6 KB (953 words) - 18:03, 30 April 2019
View ( | ) (20 | 50 | 100 | 250 | 500)