arm April 2022

arm@lists.fedoraproject.org

15 participants
13 discussions

Re: Clarification of RPi 4 support
by Peter Robinson 04 Apr '22

04 Apr '22

Please keep cc:s in tact > > Can we also delete the FAQ section as well and just direct them to the > > wiki, I have no idea who added this but I don't ever remember being > > consulted. > > What is that bad with the FAQ section? There are some helpful informations. Probably just add a „note“ box and a link to the corresponding arm wiki? (Saying the arm wiki is the one maintained by arm maintainer and therefore the authoritative one) Well it's basically the one in the FAQ except it's not updated. Why duplicate the information unnecessarily.

2 2

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠fedoraproject.org 03 Apr '22

03 Apr '22

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2022-04-05 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.libera.chat The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/9910/

1 0

Fedora 36 validation testing event: let's do full testing of Fedora 36 Branched 20220401.n.0
by Adam Williamson 01 Apr '22

01 Apr '22

Hi folks! Trying something a bit new here. I've nominated today's Fedora 36 nightly compose for validation testing. We do this regularly in any case, but I'm sending this out to a wider group and asking folks to treat this nightly as it it were a release candidate, and try to complete the *full* set of Final validation tests on it. The idea is to try and make sure we get all the tests done well ahead of the Go/No-Go Meeting, so we can identify any remaining blocker bugs *now*, not have to try and deal with them in a hurry later. Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/36 . You can use this to prioritize tests that have not yet been run at all. You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… The goal is to try and hit every test marked as Basic, Beta or Final (hitting the Optional ones too is great but not required). It'd be particularly good to cover things that often don't get done until late - aarch64 tests, Cloud tests in real clouds, and the full set of Server Active Directory tests, for instance. If you hit a significant failure in a test, please file a bug, and most likely propose it as a release blocker using https://qa.fedoraproject.org/blockerbugs/propose_bug . If you have any questions or need any help with testing or reporting results, please contact us on the test@ list or the QA IRC/Matrix channel (#fedora-qa on IRC, "Fedora QA (Quality Assurance)" on Matrix). Thanks a lot, folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm April 2022