[F45 test days] RPM #917
Labels
No labels
agile
anacondawebui
arm
blockerfe
Closed As
Duplicate
Closed As
Fixed
Closed As
Invalid
Closed As
Wontfix
Closed As
Worksforme
coreos
criteria
defect
easyfix
enhancement
iot
meeting
meta
onboarding call
proventesters
retrospective
silverblue
sponsor
test cases
test days
wiki
ai-review-please
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
pr2jira
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#916 Plan F45 test days (Changes, usual events)
quality/tickets
Reference
quality/tickets#917
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
RPM has multiple F45 changes which seem impactful:
It might be a good idea to organize test days for them.
If you take this ticket, please make the change owners subscribed to this ticket, talk to them whether organizing test days makes sense and whether they can participate (write test cases and other instructions), and help them handle the event preparation.
Ping @pmatilai @ngompa @mdomonko for feedback
We haven't done an RPM test day before (or at least not during my tenure) but the concept does sound useful. There's a couple of new features in RPM 6.1 but they're mostly interesting to packagers. Would that count?
As for the enforced signature policy thing, it's ideally a non-event for the vast majority of users, but of course there can be use cases that we haven't thought about.
The repo config relocation is perhaps also relevant to the DNF folks (@egoode), though, so consider looping them in for that, too.
Either way, I'll need to sync up with @pmatilai who's currently on PTO (for the rest of July) so will get back to you then if that's fine.
Thanks!
Thanks, Michal, for your update.
Let me give a quick summary first. The purpose of Test Days is to provide a little more test coverage for important features and changes in Fedora. You can see past events at https://testdays.fedoraproject.org . There are some unknowns, e.g. how many community testers we can attract for a particular topic. Usually the test cases must be simple enough for people to do, or if it targets some specific group (like packagers, sysadmins, etc) they can be more involved, but there's a smaller pool of potential contributors. The tests should ideally not mimic an existing test suite, but leverage people input for things where there's some benefit - e.g. testing various hardware, personalized user configuration, unexpected workflows, or just blank spots and hard-to-automate parts in your existing test suite. But it's really up to the team what they want to see covered.
We don't have to have a test day for RPM. But we identified these Changes as potentially important, and just want to reach out to you and discuss with you whether it makes sense to you or not. If it does, we can help set everything up. Making it a combined RPM+DNF test day also sounds like a good idea.
Let's wait for Panu and let's also hear from Evan, thanks!
Meanwhile, one realization: We have recently changed our release model (and schedule) that allows us to deliver feature releases more often than once per year, similar to how the Linux kernel does it.
That means, a single RPM minor release like we've known it becomes less "special", and Fedora will eventually see more frequent minor updates of RPM as well. We are yet to decide on the cadence and/or the Fedora change process associated with it, but that's the plan. See also: https://rpm.org/2026/05/11/release-cycle.html.
I feel like this change has some effect on whether such a one-off test day focused on 6.1 would be a meaningful use of resources, since there's always the next release in the works. Maybe it would make more sense after 6.3 or so? Dunno. We can discuss this when Panu is back, indeed.
@kparal wrote in #917 (comment):
Indeed, a combined test day sounds like a good idea (but see my previous comment also).
We included RPM 6.1 just because it's listed as one of the F45 changes. But the test days are not tied to just upcoming Fedora release and their schedule. If you appreciate it, we can definitely also create test days for RPM 6.2, 6.3, etc in the future. It's really up to you, whether you want to gather some community testing feedback, and when.
Hi @mdomonko and @pmatilai , have you discussed whether a test day for the RPM (maybe plus DNF) changes make sense to you?