From Fedora Project Wiki

No edit summary
(38 intermediate revisions by 2 users not shown)
Line 1: Line 1:
===Condor's Notes===
<!-- This is a comment! -->
[[File:fedora_notebook.jpg | thumb | 400px | Decison making tools in action! Asking myself, "What should be the next step?" ]]
[[File:fedora_notebook.jpg | thumb | 400px | Decison making tools in action: What should be the next installation? ]]
<br/>
<br/>
==Introduction==
----
<p>
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 [https://fedoraproject.org/wiki/Releases Fedora's Hybrid Release Schedule]. These observations are of the release of Fedora 33 in October 2020.
</p> 
<p>


</p>


==f34 current while f35 is under development==
==f33 current while f34 is under development==




{| class="wikitable"
[https://en.wikipedia.org/wiki/Digital_signal_processing Digital Signal Processing] ->
! Ordinal Coordinate || Task Name  || Description
[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
1
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
'''Activity Log'''
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>
[[user: condor/dribble | Activity Log ]] 
|-
|
2
||
'''Fedora Flock 2015'''
||
[[user: condor/flock | Flock Itinary ]] 


[[ User:Condor/flock_2015_attendence_evaluation | Attendence Evaluation ]]
<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==
2/9/21</br>
Applications</br>
OpenSCAD</br >
Gazebo</br>
FreeCAD</br>
Synfig (New Interest)</br>


1/9/21</br>
Once again communications channels.</br>


|3
==F32 -> F33==
||
12/08/2020
'''Purpose Statement'''
IRC Chat, Telegram, Matriix</br>
||
Rebasing Silverblue</br>
I'm chasing the bleeding, leading edge of the Gnu/Linux Family of Technologies by focusing on the Fedora Ecosystem. I ever increase my technical knowledge of the Fedora ecosystem and Fedora methodologies as they advance by networking within the community and actively using Fedora. A byproduct of this involvement in Fedora is promotion Fedora to the general public with demonstrated productivity.
My first Silverblue installation went belly up this morning,</br>
|-
therefore 12/15/2020 is declared a Fedora involvement.</br>
|4
|| Schedule in principle
||


{| class="wikitable"
==Release Schedule==
! Day Of Week || Task  || Description
[https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle The Life Cycle of a Fedora Release]
|-
|
Monday
||
# '''Career Development'''<BR />
# '''CONDOR Activities'''<BR />
# '''Fedora QA'''
||
Description Body
|-
|
Tuesday
||
'''Typical day off'''<BR />
||
Description Body
|-
|
Wednesday
||
# '''The Day Gig.'''
||
Description Body
|-
|
Thursday
||
# '''The Day Gig.'''
||
Description Body
|-
|
Friday
||
# '''The Day Gig.'''
||
Description Body
|-
|
Saturday
||
# '''The Day Gig.'''
||
Description Body
|-
|
Sunday
||
'''Typical Day Off (with nothing scheduled)'''
||
Description Body
|}
|-
|5
||Important Links
||




==Test Days==
===F34 Testing===


[https://lists.fedoraproject.org/pipermail/test/ Test Mailing List Archive]<BR />
[https://fedoraproject.org/wiki/Test_Day:2021-01-04_Kernel_5.10_Test_Week Kernel 5.10 ]


[http://lists.gnu.org/archive/html/help-bash/ Bash Help List Archive]<BR />
virt-manager test</br>
[http://lists.gnu.org/archive/html/bug-bash/ Bash Bug List Archive]<BR />
SilverBlue test</br>
[http://fedoraproject.org/wiki/Fedora.next Fedora Next]<BR />
Raspberry Pi test</br>
<BR />
----
[https://lists.gnu.org/archive/html/qemu-devel/ Qemu Devel List]<BR />
<BR />


[https://lists.fedoraproject.org/pipermail/test/2014-May/121247.html May Test Matrix]<BR />
[https://lists.fedoraproject.org/pipermail/qa-devel/ QA Devel Mailing List Archive]


|-
===F33 IoT Test Day===
|6
----
||Miscellany
====Initial====
||
[http://fedoraproject.org/wiki/Test_Day:2020-09-30_Fedora_33_IoT_Edition IoT Test Announcement Day]
[[user:condor/notes | Top Level of my notes]]<BR />
[http://docs.fedoraproject.org/en-US/index.html Fedora Documentation]<BR /> 
[[User:Condor/Networking-notes | (Preliminary) Networking Notes]]
|}


[https://testdays.fedorainfracloud.org/events/95 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====
[https://btrfs.wiki.kernel.org/index.php/Main_Page btrfs home page @ kernel.org]


==Resources==
----
<div>
Visit me here: [http://englishgrammar.josephpesco.info My Personal Blog ]


Visit me here: [http://www.josephpesco.info/qaz My Wiki ]
[https://meetbot.fedoraproject.org/ Fedora Meeting Bot]
 
[https://fedoraproject.org/wiki/QA/Join#release-validation release-validation]


[[Help:Wiki_syntax_and_markup | Local Wikimarkup cheat sheet]]
[[Help:Wiki_syntax_and_markup | Local Wikimarkup cheat sheet]]


[https://www.mediawiki.org/wiki/Help:Formatting  Mediawiki help]
[https://en.wikipedia.org/wiki/Btrfs English Wikipedia Btrfs Article]
[https://bugzilla.redhat.com/page.cgi?id=bug-writing.html Red Hat Bugzilla Bug Writing Guidelines]
[https://docs.fedoraproject.org/en-US/project/code-of-conduct/ Code of Conduct]
[https://fedoraproject.org/wiki/Legal:PrivacyPolicy?rd=Fedora_Project_Wiki:Privacy_policy Privacy Policy]
</div>
<!-- ==================================== -->
<!-- ==================================== -->


<!-- https://fedoraproject.org/wiki/User:Condor/Networking-notes  -->
<!-- https://fedoraproject.org/wiki/User:Condor/Networking-notes  -->

Revision as of 19:17, 21 March 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

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


Retrieved from "https://fedoraproject.org/w/index.php?title=User:Condor&oldid=609454"