Hi FESCo members,
This change is intended for F42 https://fedoraproject.org/wiki/Changes/Copilot_Runtime_Verification_Framework. It missed the self-contained deadline by a few weeks and I came across it in the queue yesterday when processing other changes for F43. I've reached out to the change proposal owners to discuss re-targeting it to F43. The owners @petersen @fdedden have explained they forgot to move it to the ReadyForWranger queue in time and the work is already done. Im wondering if this change could still be submitted for F42 and pulled in for Final? I think its too close for Beta by the time it goes through the change announcement process.
cc @adamwill @kparal for QA feedback too would be helpful.
I'm +1 since this is a net-new feature, so I see this as very low risk
+1 with me, it's just a net add of things.
+1 with my Quality hat on, this looks self-contained and safe
+1
yeah, I see no Quality concerns here, it's just a new thing.
(The naming conflict with Github's AI thing might confuse people, but that's nothing to do with Quality).
After over a week, APPROVED (5, 0, 0)
Actually, as this change is not announced yet, I will announce it now and if there has been no significant feedback that will change the proposal I can go ahead and mark it as approved from FESCo as the proposal is already been reviewed. If there are any changes made to the proposal, I will resubmit it for FESCo voting at the end of the community feedback period.
Metadata Update from @amoloney: - Issue set to the milestone: Fedora Linux 42 - Issue tagged with: pending announcement, self contained change
Metadata Update from @amoloney: - Issue untagged with: self contained change
Metadata Update from @fale: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.