On Tuesday, 11 February we reached the Change Checkpoint: Completion deadline (testable). At this milestone all the F321 Changes should be testable, which is indicated by "MODIFIED" status of a tracking bug. A Bugzilla query shows all the tracking bugs which are not in "MODIFIED" state and are not considered testable.
These changes are presented for FESCo review to determine what action should be taken. The next deadline is 25 February when all changes should be 100% code complete.
System-Wide Changes
Self-Contained Changes
Updated Changes
Metadata Update from @bcotton: - Issue tagged with: F32, self contained change, system wide change
(Updated the description to correct a few places I forgot to update the copypasta)
GCC 10 is ready to test for some time.
Modules in Non-Modular Buildroot were not enbaled during the mass rebuild.
Django 3 is testable for months, will update the bugzilla to ON_QA, sorry about that.
Retire Python 2 has happened, will update the bugzilla to ON_QA, sorry about that.
Freeze after branching until compose is ready was done, will mark MODIFIED to update the docs.
The Comp_Neuro_Lab change is also code-complete. The necessary tickets/pull requests with releng and kickstarts etc have already been closed/merged. Only the bits required for the website remain. I too forgot to update the status of the tracker bug. Apologies.
DNF Better Counting
I saw countme=1 in rawhide's modular repo. So is it actually complete?
countme=1
GCC 10 The GNU C Library version 2.31 LLVM 10
I think these are done.
Updated the description to reflect change in BZ status.
DNF Better Counting I saw countme=1 in rawhide's modular repo. So is it actually complete?
The sending of countme is complete (I think it may have shipped in F31), but the server-side counting is not implemented AFAIK.
GCC 10 The GNU C Library version 2.31 LLVM 10 I think these are done.
Set GCC 10 and glibc 2.31 to ON_QA because I know they got included in the mass rebuild. Leaving LLVM 10 because I don't know one way or the other. I'd like the change owner to weigh in.
Okay, sounds like this should be pushed back to F33, then.
Modules in Non-Modular Buildroot were not enbaled during the mass rebuild. Okay, sounds like this should be pushed back to F33, then.
Confirmed with sgallagh
Metadata Update from @psabata: - Issue tagged with: meeting
* DNF Better Counting: Non-blocking, client-side done, let's give the server-side part more time. (contyk, 16:02:59) * Free Pascal Compiler 3.20: Appears to be done, bug status should be updated. (contyk, 16:05:03) * LLVM 10: Appears to be done, bug status should be updated. (contyk, 16:06:02) * Restart services at end of rpm transaction: Status unclear; if no action is taken before the deadline, let's move this to F33. (contyk, 16:16:40) * Stop shipping individual component libraries in clang-libs package: Appears to be done, bug status should be updated. (contyk, 16:18:28) * Use update-alternatives for /usr/bin/cc and /usr/bin/c++: Moved to F33, any changes should be reverted. (contyk, 16:20:28) * Haskell package to Stackage LTS 14: Done. (contyk, 16:22:12) * Ship BerkeleyDB backend as a module: Moved to F33. (contyk, 16:23:03) * Limit scriptlet usage of core packages: An ongoing change, status unknown. No action needed. (contyk, 16:25:18)
Metadata Update from @psabata: - Issue untagged with: meeting - 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
Log in to comment on this ticket.