From Fedora Project Wiki

  • * [[User:mhough|Morgan Hough]] (Intel related while testing SODECL on Intel NUCs) * Document installation, packages, and general use cases
    9 KB (1,069 words) - 17:52, 14 January 2024
  • ...the date? | If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, fi ...cast of characters will be available testing, workarounds, bug fixes, and general discussion:
    6 KB (971 words) - 02:25, 24 April 2024
  • == RC3 Testing Status == # KDE desktop validation not done
    52 KB (6,228 words) - 22:27, 24 August 2011
  • ...ead of <code>git://</code> in the <code>git clone</code> command above. In general using <code>ssh://</code> could be useful (as a global setting), add to the ...h of the files and do your work there. Then after you've done appropriate testing, you can merge those changes into the branch you retrieved and send them to
    8 KB (1,294 words) - 21:16, 26 March 2015
  • * adamw will continue with Final criteria rewrite and look at updating the validation test case set * jreznik would like to see functional validation of Changes for F20
    59 KB (7,383 words) - 05:50, 5 July 2013
  • ...6 Alpha prep, oVirt node spin review and testing, and Instalatron anaconda testing framework details, to name but a few items. Security Advisories brings us In this section, we cover announcements from the Fedora Project, including general announcements<ref>
    44 KB (6,342 words) - 02:16, 12 August 2011
  • ...memory testing software in place of '''Anaconda'''. '''Memtest86''' memory testing continues until the <code>Esc</code> key is pressed. ...art</code>, and contains a parser and writers. As a result of this change, validation and extension is now much easier.
    8 KB (1,299 words) - 20:45, 16 February 2010
  • ...anata, as well as some simple suggestions on translating, proofreading and testing. 13. Validation options
    21 KB (3,429 words) - 14:06, 2 January 2016
  • ...e of interest. RESTful/JSON APIs and servers such as WebHDFS offer a more general solution that is independent of the client's operating system and programmi ...while resolving any potential issues with the bindings to libgfapi and for testing purposes. Where possible, I will use the same libraries as efforts (e.g.,
    9 KB (1,428 words) - 00:51, 20 March 2014
  • ...e of interest. RESTful/JSON APIs and servers such as WebHDFS offer a more general solution that is independent of the client's operating system and programmi ...while resolving any potential issues with the bindings to libgfapi and for testing purposes. Where possible, I will use the same libraries as efforts (e.g.,
    9 KB (1,428 words) - 05:10, 20 March 2014
  • ...leases/{{FedoraVersion||next}}/Schedule| release schedule]] page. Beta and General Availability (final) releases happen at 14:00 UTC. ...y]]. Packages must go through the [[Repositories#updates-testing|''updates-testing'']] repository for the release before entering its [[Repositories#stable|''
    11 KB (1,695 words) - 21:18, 1 August 2017
  • In this section, we cover announcements from the Fedora Project, including general announcements<ref> === General ===
    22 KB (3,361 words) - 14:21, 20 October 2009
  • ...s goes well, we'll use it for F36. [https://ask.fedoraproject.org/t/we-are-testing-a-new-common-issues-category-and-process/18916 Your feedback] is welcome! ...notes] for specific information about changes in Fedora Linux 35 and other general information.
    16 KB (2,470 words) - 00:01, 15 December 2021
  • ...ent in Greece. In Quality Assurance news, details on the latest Fedora 13 testing processes and results, and reports on two Test Days on Preupgrade Kit and X === Fedora 13 testing ===
    22 KB (3,236 words) - 15:42, 13 May 2010
  • ...eases/{{FedoraVersion||next}}/Schedule| release schedule]] page. Beta, and General Availability (final) releases happen at 14:00 UTC. ...y]]. Packages must go through the [[Repositories#updates-testing|''updates-testing'']] repository for the release before entering its [[Repositories#stable|''
    12 KB (1,732 words) - 22:28, 14 November 2017
  • ...eases/{{FedoraVersion||next}}/Schedule| release schedule]] page. Beta, and General Availability (final) releases happen at 14:00 UTC. ...y]]. Packages must go through the [[Repositories#updates-testing|''updates-testing'']] repository for the release before entering its [[Repositories#stable|''
    12 KB (1,723 words) - 09:47, 5 December 2017
  • ...edoraVersionNumber|next}}-key-tasks.html release schedule] page. Beta, and General Availability (final) releases happen at 14:00 UTC. ...y]]. Packages must go through the [[Repositories#updates-testing|''updates-testing'']] repository for the release before entering its [[Repositories#stable|''
    12 KB (1,745 words) - 17:04, 7 April 2021
  • ...esign beat, updated details on Fedora 13 artwork including wallpapers, and testing results of the new Design Suite spin. Security Advisories provides last we In this section, we cover announcements from the Fedora Project, including general announcements<ref>
    42 KB (6,119 words) - 18:55, 22 February 2010
  • ...finally finish drafting revised partitioning criteria'' - still not done, validation still getting in the way, but existing state should be OK for Beta * TC7 testing over the weekend had revealed only one big issue, RC looked plausible
    47 KB (5,743 words) - 04:29, 1 February 2013
  • ...'' - tflink followed up to some degree, but the status of cloud images and testing did not seem satisfactory, further action required === F20 Alpha RC2 Testing Status ===
    40 KB (4,969 words) - 09:54, 25 September 2013
View ( | ) (20 | 50 | 100 | 250 | 500)