From Fedora Project Wiki
(Advancing the learning process with just one more observation.) |
(Added metbot link) |
||
| Line 43: | Line 43: | ||
<div> | <div> | ||
Visit me here: [http://englishgrammar.josephpesco.info My Personal Blog ] | Visit me here: [http://englishgrammar.josephpesco.info My Personal Blog ] | ||
[https://meetbot.fedoraproject.org/ Fedora Meeting Bot] | |||
[https://fedoraproject.org/wiki/QA/Join#release-validation release-validation] | [https://fedoraproject.org/wiki/QA/Join#release-validation release-validation] | ||
Revision as of 16:01, 23 October 2020
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.
Release Schedule
The Life Cycle of a Fedora Release
Test Days
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