On Tuesday, 25 February we reached the Change Checkpoint: Completion deadline (100% complete). At this milestone all the F32 Changes should be testable, which is indicated by "ON_QA" status of a tracking bug. A Bugzilla query shows all the tracking bugs which are not in "ON_QA" state and are not considered complete.
These changes are presented for FESCo review to determine what action should be taken. Assignees have been NEEDINFO'ed in Bugzilla. Normally I would give them a day to respond, but due to personal reasons I'm late getting to this.
System-Wide Changes
Updated Changes
Rebase apt package from apt-rpm to Debian's apt
This has been completely done for a while.
Additional buildroot to test x86-64 micro-architecture update
this is "rawhide only" and can simply happen any time regardless our release processes and deadlines
Build Python with -fno-semantic-interposition for better performance
This is still the same. 100% complete on anything but 2 arches and blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1795575 where the gcc maintainers ignore me. We won't revert the change just for those 2 architectures and we are happy to ship it on some arches only. Also, I'm confident to flip the switch on those arches even after beta.
Update: We are ready to ship this on all arches. Should we do that?
Build Python with -fno-semantic-interposition for better performance Update: We are ready to ship this on all arches. Should we do that?
You will need a FE to get it in past freeze now, but if you plan on doing so, sooner is much better... ie, do it now. ;)
You will need a FE to get it in past freeze now
I know, see our options at https://bugzilla.redhat.com/show_bug.cgi?id=1779341#c6
https://bugzilla.redhat.com/show_bug.cgi?id=1808651
My apologies. I totally forgot to change the status even though it has already been done. updated for https://bugzilla.redhat.com/show_bug.cgi?id=1792463
Systemd presets for user units
This one is done too: https://bugzilla.redhat.com/show_bug.cgi?id=1468501
After all, this is a fix for a bug that I myself reported :thumbsup:
At this point the only thing left is DNF Better Counting. Since the work is entirely server-side at this point, do we want to consider the change completed for the purposes of the change process, or continue tracking it?
I'd continue tracking it, would be good to have it ready for GA.
@bcotton Do you want to have this in the meeting agenda for Monday?
@churchyard not unless there's something FESCo members want to discuss about this. I'll be at ~9km AGL during the meeting. I'm fine with closing this ticket. The server side implementation of DNF Better Counting may not happen before the F32 release so if it's not done by then, I'll just move it forward to F33 for tracking.
Metadata Update from @churchyard: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Metadata Update from @bcotton: - Issue untagged with: F32 - Issue set to the milestone: Fedora 32
Login to comment on this ticket.