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>
Hey folks,
QA is hosting a series of Fedora 42 test days this week, and we could
really use your help to make sure things don’t explode in the hands of
unsuspecting users later. If you have a little time and a bit of curiosity
(or a lot of both), please consider participating:
*Kernel 6.14 Test Week*📅 April 6–12
Details : Test Day: Kernel 6.14
<http://fedoraproject.org/wiki/Test_Day:2025-04-06_Kernel_6.14_Test_Week>
*Fedora 42 IoT Edition Test Week*
📅 April 7–11
Details: Test Day: Fedora 42 IoT Edition
<http://fedoraproject.org/wiki/Test_Day:2025-04-07_Fedora_42_IoT_Edition>
*Fedora 42 Accessibility (A11y) Test Week*
📅 April 7–11
Details Test Day: Fedora 42 A11y
<http://fedoraproject.org/wiki/Test_Day:2025-04-07_Fedora_42_A11Y>
No special skills required — just a Fedora install, some spare time, and a
vague tolerance for minor chaos.
Thanks for helping make Fedora better (or at least, not worse)!
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>
As stated above, my dual-boot machine is legacy BIOS with MBR partitioning, so I can't simply choose "Reinstall Fedora" (which doesn't even appear when MBR partitioning is present). I'm attempting to follow the instructions at https://fedoraproject.org/wiki/QA:Testcase_partitioning_webui_guided_btrfs_… . Steps 1 to 4 are clear (though I have to resist the temptation to choose "Share disk with other operating system", since the wiki page clearly says to choose "Mount point assignment"). I find Step 5 to be as clear as mud. On the page "Manual disk configuration: Mount point mapping", in the "Mount point" column, there is / (Required) and /boot (Recommended). In the "Device" column, there are "Select a device" choices, the same set of choices for each of / and /boot, namely
sda1 ntfs
sda2 ntfs
sda3 ext4
home btrfs
root btrfs
root/var/lib/machines btrfs
(of course, sda1 and sda2 are Windows, the rest are Fedora). The right column is "Reformat" with a toggle for each of / and /boot. Presumably, I'm supposed to be able to toggle that on or off separately for each selected device, but I can't. If I toggle it off for "home" under either / or boot, it's toggled off for the rest, and if I toggle it on for one of the other devices, it's toggled on for all. Presumably, to not affect the Windows partitions, I would also want to toggle it off for sda1 and sda2, under both / and /boot. Am I doing something wrong, or is this broken? And do I have to duplicate all the settings for each of / and /boot, since the list of devices is identical under each of those? I do have the option of removing the anaconda-webui package and then running the installer in GTK mode, which I'm familiar with.
P.S. I'm using Adam's test image from https://bugzilla.redhat.com/show_bug.cgi?id=2353002#c55 .
# F42 Blocker Review meeting
# Date: 2025-04-07
# Time: 16:00 UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for a Fedora 42 blocker review meeting! We have 3
proposed blockers and 6 proposed freeze exceptions for Final.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker…
The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.
If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F42 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
Hello All,
Virtualization is a core feature used on a day-to-day basis by multiple
developers, testers
and users. Fedora QA is hosting a Virtualization Test Day[0], where we will
all be testing
the virtualization features for Fedora. The test day app[1] will help
people to record
results till the Monday 2025-04-07.
If you have any questions please reach out to me!
[0] http://fedoraproject.org/wiki/Test_Day:2025-04-05_Virtualization
[1] https://testdays.fedoraproject.org/events/215
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>