From Fedora Project Wiki

(Add some boot related information)
(thoughts and hyperlinks worked on)
Line 15: Line 15:
  
 
==f34 current while f35 is under development==
 
==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>
 +
 +
[https://fedoraproject.org/wiki/QA:Release_validation_test_plan Validation Testing]
 +
 
[https://fedoraproject.org/wiki/Releases/35/ChangeSet Fedora 35 Change Set]
 
[https://fedoraproject.org/wiki/Releases/35/ChangeSet Fedora 35 Change Set]
 +
 
[https://fedorapeople.org/groups/schedule/f-35/f-35-quality-tasks.html Fedora 35 QA Schedule]
 
[https://fedorapeople.org/groups/schedule/f-35/f-35-quality-tasks.html Fedora 35 QA Schedule]
  

Revision as of 09:25, 16 June 2021

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



Introduction


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.

f34 current while f35 is under development

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.

Validation Testing

Fedora 35 Change Set

Fedora 35 QA Schedule

f33 current while f34 is under development

Digital Signal Processing -> Pipewire Testing
Gnome 40 Testing

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.

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.

Early adopters of the next release need the new software to be production quality ASAP.

f32 current while f33 is under development

F33 -> F34

2/9/21
Applications
OpenSCAD
Gazebo
FreeCAD
Synfig (New Interest)

1/9/21
Once again communications channels.

F32 -> F33

12/08/2020 IRC Chat, Telegram, Matriix
Rebasing Silverblue
My first Silverblue installation went belly up this morning,
therefore 12/15/2020 is declared a Fedora involvement.

Release Schedule

The Life Cycle of a Fedora Release


Test Days

F34 Testing

Kernel 5.10

virt-manager test
SilverBlue test
Raspberry Pi test



F33 IoT Test Day


Initial

IoT Test Announcement Day

IoT Edition Result Page

Resources

F33 Btrfs By Default Test Week


Initial

Install to Previous KVM

Release-blocking (x86_64)

Desktop

Modularity

Guided Storage Configuration

Exploration

Resources

btrfs home page @ kernel.org

Resources



How Grubby Can You Be?

Fedora Multiboot Guide

Boot Basics


Other Resources