Retired packages should close rawhide bugzilla as WONTFIX or EOL #8478
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
release-process
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 milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets#8478
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?
When a package gets retired, all the bugzilla filed for rawhide should be closed as WONTFIX or EOL.
Any time.
Once we don't retire packages or use bugzilla.
A lot of open bugzillas for retired components. I think this used to happen automatically before, but maybe it was done by a human.
Metadata Update from @mohanboddu:
I have a prototype script that closes all bugzillas for retired components.
However, when trying to get list of all rawhide bugzillas, bugzilla API crashes with Proxy error.
For 31 it seems to work (apparently, less 31 than rawhide Fedora bugzillas). Will do more testing and post something soon.
It could use some concurrency of
is_retiredcalls (now it takes ~1 hour), but otherwise appears to work.I cannot longer close Bugzillas as EOL, so I went with WONTFIX.
This is unfortunately already causing confusion: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4554GEM6XE3ZBAE53SU26GV2HLTU7S4O/
So... why do we need this? The bugs should get EOLed as fedora EOL's releases.
If someone unretires a package, it won't be easy for them to see what things were outstanding when it was retired.
Is there some advantage to doing this?
Some bugzillas are forever rawhide and never EOLed.
Wouldn't they get moved to branched at branching time? unless they have FutureFeature or whatever... in which case, wouldn't they still be of use to the package in case it's ever unretired?
From our releng meeting today, we decided to implement this as part of toddlers but when someone unretires we will send them a list of bugs that got closed due to retirement and let them handle it however they want to.
But we need help as this is something that we can live with, if someone from community would like to pick it up for us, that would be great.
This still seems to be the plan, it needs someone working on writing the code in toddlers
I'd like to help with this, but I have no idea what toddlers means. I recently discovered that we have more than 400 open bugs from release monitoring for retired packages.
toddlers is a 'app' , where the source is: https://pagure.io/fedora-infra/toddlers
We run that application in the fedora-infrastructure openshift cluster.
It listens for messages on our message bus and then has various workers that do things based on them.
So, for this case we would I think to adjust an existing one that handles when we get retirement events and have it go out and close bugs.
I've found this toddler that runs every time a branch is retired and blocks the package in Koji. This shares a lot of logic, and it might make sense to extend this one to also close bugzillas reported by "Upstream Release Monitoring" for the retired branch/version and the package.
What do you think?
@humaton, do you plan to work on this? Do I understand the labels added last month correctly?
@lbalhar Hey, those labels were added as part of grooming old tickets. I'll bring this ticket up during the releng weekly meeting, and we will see how we would like to proceed with it. You are welcome to join the meeting happening at 4 pm CEST time in the #meeting-3:fedoraproject.org matrix channel