From Fedora Project Wiki

View ( | ) (20 | 50 | 100 | 250 | 500)
  • ...te, both sections are meant for users of Fedora variants like Workstation, Server, or KDE Plasma Desktop; in case you are using a Fedora Atomic Desktop like ...BIOS Setup or through a process initiated through <code>mokutil --disable-validation</code>; that's required, as your firmware will otherwise reject booting ker ...
    14 KB (2,150 words) - 18:29, 27 June 2024
  • == Fedora 16 - Rawhide acceptance testing == # twu agreed to lead Rawhide Acceptance Tests for Fedora 16, will be testing and posting a matrix for review starting this week ...
    64 KB (7,922 words) - 16:45, 11 July 2011
  • ...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...
    46 KB (6,384 words) - 16:33, 27 March 2020
  • Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} ...
    40 KB (5,519 words) - 18:54, 17 July 2018
  • Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} ...
    40 KB (5,519 words) - 18:57, 17 July 2018
  • Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} ...
    38 KB (5,307 words) - 16:19, 30 June 2017
  • Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} ...
    38 KB (5,351 words) - 23:29, 27 November 2017
  • ...of my progress. I will also be pushing my commits once a week on a remote server specified, sometimes even earlier when I feel major works have been complet * Validation of constraints: ...
    14 KB (2,287 words) - 05:57, 24 March 2014
  • ...to set up a virtual equivalent ASAP, but no one can remember how that old server is configured? People will sell you very expensive software to solve this p ...<ref>http://mairin.wordpress.com/2009/10/17/open-source-portable-usability-testing-lab-part-2-the-parts/</ref> the complete part list to the Fedora portable u ...
    22 KB (3,361 words) - 14:21, 20 October 2009
  • * ''pschindl to send out karma/testing request for not-yet-stable updates in RC2'' - this was likely done, by the ...ke sure some cloud testing is getting done'' - this was done, tim did some testing on RC4 AMIs ...
    58 KB (7,284 words) - 10:16, 25 September 2013
  • Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} ...
    39 KB (5,491 words) - 17:25, 1 February 2018
  • ...l of Fedora Workstation to be more in line with the base install of Fedora Server. ...to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change ...
    14 KB (2,271 words) - 16:27, 29 January 2021
  • ...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...
    49 KB (6,924 words) - 11:03, 7 October 2020
  • ...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...
    49 KB (6,928 words) - 15:01, 5 October 2020
  • ...ill want to do some best-effort testing on it and try and work it into the validation process somehow for F17 * Before that, they will start providing test images as soon as external testing will actually be of use to them, with instructions ...
    60 KB (7,664 words) - 21:29, 19 September 2016
  • ...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...
    50 KB (7,002 words) - 10:25, 17 May 2021
  • ...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...
    50 KB (7,039 words) - 13:18, 6 October 2021
  • Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} ...
    43 KB (6,012 words) - 01:30, 3 April 2019
  • Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} ...
    43 KB (6,012 words) - 00:06, 5 July 2019
  • ...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...
    55 KB (7,755 words) - 13:36, 10 October 2022
View ( | ) (20 | 50 | 100 | 250 | 500)