m (→F34 -> F35) |
|||
| Line 15: | Line 15: | ||
==F34 -> F35== | ==F34 -> F35== | ||
[https://fedoraproject.org/wiki/Test_Day:2021-03-03_Audio_Test_Day Pipewire Testing]</br> | |||
[https://fedoraproject.org/wiki/Test_Day:2021-03-17_Fedora_34_GNOME_40 Gnome 40 Testing]</br> | |||
<p>Writing an evaluation before the end of the procedure seems odd, but sometimes we need | <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 | to take a breath and collect our thoughts. This is only the second release cycle I'm | ||
Revision as of 09:00, 19 March 2021
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 -> F35
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 internal.
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.
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
virt-manager test
SilverBlue test
Raspberry Pi test
F33 IoT Test Day
Initial
Resources
F33 Btrfs By Default Test Week
Initial
Install to Previous KVM
Release-blocking (x86_64)
Desktop
Modularity
Guided Storage Configuration
Exploration
Resources
Resources
Visit me here: My Personal Blog
English Wikipedia Btrfs Article