=====================================
# #meeting:fedoraproject.org: Quality
=====================================
Meeting started by @adamwill:fedora.im at 2025-04-28 15:00:49
Meeting summary
---------------
* TOPIC: Roll Call (@adamwill:fedora.im, 15:00:55)
* TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 15:04:33)
* INFO: "adamw to check in with anaconda team and co-ordinate plans for webui during f43 cycle" - I have checked in, the current state is that they attempt to run daily and report to the wiki, but it's a bit unsophisticated: they use a cronjob-equivalent, and use a URL template to find the thing to run against; switching between rawhide and branched has to be done manually. like openQA the system does not report failures, so results need to be checked directly in the test system web UI to see and investigate failures. I'll continue working with the anaconda team on ways to improve and organize this (@adamwill:fedora.im, 15:06:21)
* INFO: kparal notes issues with candidate composes. the current automatic scheduler for the anaconda system does not handle candidate composes at all; even if we fix that, timer-based triggering is a poor fit with candidates where we want the results ASAP (@adamwill:fedora.im, 15:14:13)
* ACTION: adamw to work with anaconda team on tracking the minimum requirements to make this viable for f43 validation (@adamwill:fedora.im, 15:18:28)
* TOPIC: Fedora 43 status (@adamwill:fedora.im, 15:20:19)
* TOPIC: Test Day / community event status (@adamwill:fedora.im, 15:28:39)
* INFO: kernel 6.14 test week happened - https://testdays.fedoraproject.org/events/216 . thanks to everyone who tested! (@adamwill:fedora.im, 15:29:24)
* TOPIC: Open floor (@adamwill:fedora.im, 15:32:56)
* INFO: new version of the testdays webapp is in testing at https://testdays.stg.fedoraproject.org/ . please try it out and report any problems you find to https://pagure.io/fedora-qa/testdays-web/issues (@adamwill:fedora.im, 15:36:10)
Meeting ended at 2025-04-28 15:40:14
Action items
------------
* adamw to work with anaconda team on tracking the minimum requirements to make this viable for f43 validation
People Present (lines said)
---------------------------
* @adamwill:fedora.im (46)
* @bittin:matrix.org (8)
* @nielsenb:fedora.im (8)
* @kparal:matrix.org (7)
* @m4rtink:fedora.im (6)
* @zodbot:fedora.im (5)
* @lruzicka:matrix.org (3)
* @meetbot:fedora.im (2)
* @boniboyblue:fedora.im (1)
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
I'd like to nominate Bug 2360491 - Postfix missing alternative
/usr/sbin/sendmail -> /usr/bin/sendmail.postfix
<https://bugzilla.redhat.com/show_bug.cgi?id=2360491>
as a common bug for Fedora 42 and a blocker for Fedora 43.
The problem is that the alternative for /usr/sbin/sendmail is not
maintained during the /usr/sbin merge leaving many programs unable to
send mail after the upgrade.
Thanks,
Jim
=====================================
# #meeting:fedoraproject.org: Quality
=====================================
Meeting started by @adamwill:fedora.im at 2025-04-14 15:00:13
Meeting summary
---------------
* TOPIC: Roll Call (@adamwill:fedora.im, 15:00:16)
* TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 15:04:26)
* INFO: nothing to follow up on (@adamwill:fedora.im, 15:04:39)
* TOPIC: Fedora 42 pre-release checks and thanks (@adamwill:fedora.im, 15:04:49)
* INFO: Fedora 42 torrents are out at https://torrent.fedoraproject.org/ - if you can help seed that will be great for the release (@adamwill:fedora.im, 15:05:06)
* INFO: general Fedora 42 release is tomorrow (Tuesday) (@adamwill:fedora.im, 15:05:30)
* INFO: common bugs issues are mostly written up over at https://discussion.fedoraproject.org/c/ask/common-issues/82/none , thanks to Kamil Páral for whipping those into shape (@adamwill:fedora.im, 15:06:01)
* AGREED: many thanks to everyone who helped test f42 beta and final and made the release go smoothly! (@adamwill:fedora.im, 15:10:31)
* TOPIC: Fedora 43 cycle pre-planning (@adamwill:fedora.im, 15:14:54)
* INFO: dates for your diary: F40 goes EOL on May 13, F43 Branch is August 12, F43 Beta freeze is August 26 (@adamwill:fedora.im, 15:16:31)
* INFO: detailed F43 schedule at https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html and https://fedorapeople.org/groups/schedule/f-43/f-43-quality-tasks.html (@adamwill:fedora.im, 15:16:58)
* ACTION: adamw to check in with anaconda team and co-ordinate plans for webui during f43 cycle (@adamwill:fedora.im, 15:21:09)
* INFO: Fedora infrastructure is moving datacenters in June. that will affect openQA, Fedora CI and blockerbugs - of course also everything else, but those are the ones primarily of interest to us. announcements and outage windows will follow closer to the date (@adamwill:fedora.im, 15:24:47)
* INFO: forgejo migration may come during Fedora 43 cycle, or...not. if it does seem to be impending, we are going to have to handle migrating blockerbugs to it. also all our other repos like fedora-qa and os-autoinst-distri-fedora and qa-misc and so on, but those should be straightforward (@adamwill:fedora.im, 15:32:45)
* INFO: https://fedoraproject.org/wiki/Changes/BootLoaderUpdatesPhase1 will obviously need close attention (@adamwill:fedora.im, 15:35:10)
* INFO: https://fedoraproject.org/wiki/Changes/DisableSTI is worth being aware of (@adamwill:fedora.im, 15:36:07)
* INFO: https://fedoraproject.org/wiki/Changes/ModernizeLiveMedia is Conan Kudo 's latest attempt to sabotage us all for the greater glory of SUSE (@adamwill:fedora.im, 15:36:48)
* INFO: https://fedoraproject.org/wiki/Changes/RPM-6.0 could obviously break the world (@adamwill:fedora.im, 15:37:37)
* INFO: https://fedoraproject.org/wiki/Changes/Python3.14 will no doubt suck up a month of my time shortly (@adamwill:fedora.im, 15:37:51)
* TOPIC: Test Day / community event status (@adamwill:fedora.im, 15:47:07)
* INFO: kernel 6.14 test week went well: https://pagure.io/fedora-qa/issue/809#comment-963299 (@adamwill:fedora.im, 15:48:56)
* INFO: F42 upgrade test week also went off successfully: https://testdays.fedoraproject.org/events/212 (@adamwill:fedora.im, 15:49:22)
* INFO: GNOME 48 test week is ending soon, drop by and add some results if you can: https://testdays.fedoraproject.org/events/218 (@adamwill:fedora.im, 15:50:04)
* TOPIC: Open floor (@adamwill:fedora.im, 15:53:51)
Meeting ended at 2025-04-14 15:56:42
Action items
------------
* adamw to check in with anaconda team and co-ordinate plans for webui during f43 cycle
People Present (lines said)
---------------------------
* @adamwill:fedora.im (72)
* @bittin:matrix.org (14)
* @conan_kudo:matrix.org (8)
* @derekenz:fedora.im (7)
* @nirik:matrix.scrye.com (5)
* @boniboyblue:fedora.im (5)
* @kparal:matrix.org (4)
* @zodbot:fedora.im (4)
* @nielsenb:fedora.im (3)
* @meetbot:fedora.im (2)
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
Hi folks! I've gone ahead and updated the Basic release criteria to
specify that installing via 'RDP' must work, instead of 'VNC':
https://fedoraproject.org/w/index.php?title=Basic_Release_Criteria&diff=pre…
this is because anaconda switched from VNC to RDP as part of
https://fedoraproject.org/wiki/Changes/Anaconda_As_Native_Wayland_Applicati…
.
Since it seems like such a straightforward swap I figured I'd just do
it and ask for forgiveness, rather than drafting it and asking for
permission. If anyone sees any issues with this, please do yell. :D
I already updated the test case and matrix for this earlier in the
cycle, but forgot about the criteria.
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
Heya,
Fedora RISC-V F42 images[1] are almost ready to go GA; new images were
refreshed yesterday, 14Apr2025. (NB: RISC-V is an "alternative" arch.)
Even if you don't have the hardware, the below images should work on
QEMU:
• "Fedora-Server-Host-Generic"
• "Fedora-Cloud-Base-Generic"
Th F42 images[1] will move to "releas" directory soon.
If anyone wants to give them a spin, here[2] are the instructions. If
you're lucky enough to have the hardware that the Fedora RISC-V team
"supports" (e.g. SiFive P550 or VisionFive 2), follow this[3] guide.
Any issues, hit us up on the Fedora RISC-V Matrix channel[4], that's
where most of the Fedora/RISC-V activity happens :-)
[1] https://dl.fedoraproject.org/pub/alt/risc-v/testing/42/
[2] https://fedoraproject.org/wiki/Architectures/RISC-V/QEMU
[3] https://fedoraproject.org/wiki/Architectures/RISC-V/Hardware
[4] https://chat.fedoraproject.org/#/room/#riscv:fedoraproject.org
--
/kashyap
Hi Fedora users, developers, and friends!
It's time to start thinking about Test Days for Fedora 43.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/624 . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at
https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development
schedule, though, in deciding when you want to run your Test Day - for
some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific time frame due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or time frame you'd
like, and we'll figure it out from there.
If you don't want to run your own Test Day, but you are willing to
help with another, feel free to join one or more of already accepted
Test Days:
GNOME Test Day*
i18n Test Day*
Kernel Test Week(s)*
Upgrade Test Day*
IoT Test Week*
Cloud Test Day*
Fedora CoreOS Test Week*
And don't be afraid, there are a lot of more slots available for your
own Test Day!
[*] These are the test days we run generally to make sure everything
is working fine, the dates get announced as we move into the release
cycle.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on Libera[0]. Thanks!
[0] https://web.libera.chat/?channels=fedora-qa
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>