From Fedora Project Wiki

(Shuffling content about.)
Tag: Replaced
Line 1: Line 1:
<!-- This is a comment! -->
[[File:fedora_notebook.jpg | thumb | 400px | Decison making tools in action: What should be the next installation? ]]
[[File:fedora_notebook.jpg | thumb | 400px | Decison making tools in action: What should be the next installation? ]]
[ Test case research]
[ Release
testing history]
This content concerns community involvement starting with comprehending Fedora Quality Assurance
practices and protocols related to being friendly. Looking above Quality Assurance my first observation
is the importance of the current release schedule and the nature of [ Fedora's Hybrid Release Schedule]. These observations are of the release of Fedora 33 in October 2020.
[ Test case research]
==f34 current while f35 is under development==
<p>As an example of using my time better for the Fedora 35 release cycle I'll first
examine the Validation Testing material then begin downloading the current nightly
compose nominated for testing. My primary production machine is a desktop back
in my home lab that's been neglected since I began working graveyard shifts.</p>
[ Validation Testing]
[ Fedora 35 Change Set]
[ Fedora 35 QA Schedule]
==f33 current while f34 is under development==
[ Digital Signal Processing] ->
[ Pipewire Testing]</br>
[  Gnome 40 Testing]</br>
<p>Writing an evaluation before the end of the procedure seems odd, but sometimes we need
to take a breath and collect our thoughts. This is only the second release cycle I'm
following closely and I'm making decision on the move. For instance, the delicate Win 10
installation that's been my laptop's internal hard drive has been removed and the ancient
60 GB SATA drive I've used for testing is now the laptop's internal hard drive.</p>
<p>It seems best to base testing on what is important when using a production installation in a
production role. It also good practice to continue testing the features previously tested
as part of the lead up to new testing. Hence, looking at btrfs, ARM, and pipewire, before
on to test Gnome 40.</p> 
<p>Early adopters of the next release need the new software to be production quality ASAP.</p>
==f32 current while f33 is under development==
==F33 -> F34==
OpenSCAD</br >
Synfig (New Interest)</br>
Once again communications channels.</br>
==F32 -> F33==
IRC Chat, Telegram, Matriix</br>
Rebasing Silverblue</br>
My first Silverblue installation went belly up this morning,</br>
therefore 12/15/2020 is declared a Fedora involvement.</br>
==Release Schedule==
[ The Life Cycle of a Fedora Release]
==Test Days==
===F34 Testing===
[ Kernel 5.10 ]
virt-manager test</br>
SilverBlue test</br>
Raspberry Pi test</br>
===F33 IoT Test Day===
[ IoT Test Announcement Day]
[ IoT Edition Result Page]
===F33 Btrfs By Default Test Week===
Install to Previous KVM
====Release-blocking (x86_64)====
====Guided Storage Configuration====
[ btrfs home page @]
====How Grubby Can You Be?====
[ Fedora Multiboot Guide]
[ Boot Basics]
===Other Resources===
Visit me here: [ My Personal Blog ]
[ Fedora Meeting Bot]
[ release-validation]
[[Help:Wiki_syntax_and_markup | Local Wikimarkup cheat sheet]]
[  Mediawiki help]
[ English Wikipedia Btrfs Article]
[ Red Hat Bugzilla Bug Writing Guidelines]
[ Code of Conduct]
[ Privacy Policy]
<!-- ==================================== -->
<!--  -->
[ Release Testing History]

Revision as of 10:19, 30 June 2021

Decison making tools in action: What should be the next installation?

Test case research

Release Testing History