On Tuesday, 10 August we reached the Change Checkpoint: Completion deadline (testable). At this milestone all the F35 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. System-Wide Changes with the contingency date in bold are past the stated contingency date.
These changes are presented for FESCo review to determine what action should be taken. The next deadline is 24 August when all changes should be 100% code complete.
I see "Fedora Linux" in /etc/os-release.
Yes, I implemented that months ago. I'm not the Change owner though, so I didn't touch the BZ. I'll do so now.
CompilerPolicy Change Owner: @law, @tstellar Contingency plan: It seems like we could institute the policy change anytime we choose. But it also seems like once the policy change is in place, packages that are going to convert should do so before beta freeze.
CompilerPolicy Change
Owner: @law, @tstellar Contingency plan: It seems like we could institute the policy change anytime we choose. But it also seems like once the policy change is in place, packages that are going to convert should do so before beta freeze.
I'm waiting on this pull request to be merged: https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/138 Which is blocking the documentation update: https://pagure.io/packaging-committee/pull-request/1066#
LLVM 13 Owner: @tstellar Contingency mechanism: (What to do? Who will do it?): If there are major problems with LLVM 13, the compatibility package provide a way for other packages to continue using LLVM 12. Contingency deadline: Final Freeze
LLVM 13
Owner: @tstellar Contingency mechanism: (What to do? Who will do it?): If there are major problems with LLVM 13, the compatibility package provide a way for other packages to continue using LLVM 12. Contingency deadline: Final Freeze
I have 13 of the 16 packages built in f35-build-side-43964, and I expect to finish the rest this week.
Golang 1.17 Owner: @alexsaezm @jcajka Contingency mechanism:Reverting to golang version 1.16.X if significant issues are discovered. Contingency deadline: Beta Freeze(?) Note: owner is planning on doing a build on rawhide and then try it on f35 before the freeze unless FESCo objects.
I'm currently doing rawhide testing in a COPR project
Hello, according to the size of this change and the possible breakage of multiple packages before f35 mass rebuild, we decided (team working on this change) to postpone this change to early lifecycle of f36, where we will have enough time to resolve any problems until f36 mass rebuild.
Postponed to F36 by the owners.
It's mostly done, but needs action from maintainers of redhat-rpm-config and the FPC. Folks, let's get this done finally!!
In progress.
It seems to be all done, we have gcc-11.2, glibc-2.34, binutils-2.37, gdb-10.2 in rawhide.
In progress, nearing completion.
I still see llvm-12.0.1-2.fc35. Bump to F36?
llvm-12.0.1-2.fc35
No idea…
There has been no progress on this. And I think the changelog part has been obsoleted by rpmautospec.
PROPOSAL: - "Patches in Forge macros - Auto macros - Detached rpm changelogs" is cancelled and should be resubmitted on top of rpmautospec if desired.
For the other changes, I think we should still wait a bit.
This will be discussed during today's meeting at 21:00 CEST. @dwmw2, @asosedkin, @tstellar, @dmach, @nim you're all invited.
Sorry, I don't think I own any F35 changes, was that a miscast?
Yep, this was about 2659.
Golang 1.17 Owner: @alexsaezm @jcajka Contingency mechanism:Reverting to golang version 1.16.X if significant issues are discovered. Contingency deadline: Beta Freeze(?) Note: owner is planning on doing a build on rawhide and then try it on f35 before the freeze unless FESCo objects. I'm currently doing rawhide testing in a COPR project
Now that we have Go 1.17.0 (until now we only had 1.17rc2) I made a build in COPR again: https://copr.fedorainfracloud.org/coprs/alexsaezm/go-rawhide/
As you can see, 225 packages of ~1800 failed to build.
What should be the next step? perhaps do a scratch build? Yesterday I upload Go 1.17.0 to rawhide and already made a build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1820645
This issue will be discussed in tomorrow's FESCo meeting. @tstellar @alexsaezm @jcajka @codonell @dmach @mcurlej @pnemade @mfabian You're invited to join in and provide an update on the current state of your change (either during the meeting and/or in this ticket)
@defolos I have already replied to personal email from @zbyszek that "Enhanced Inscript as default Indic IM" Change implementation has been completed and moved the bug to ON_QA. The bug tracker for this Change bug did not include me in CC list hence I missed any initial needinfo's on that bug. I have also replied to this Change bug that the implementation has been completed in Fedora 35 and its testable.
@pnemade Yes, thanks for the confirmation and sorry for the double/tripple pings. Thanks for your swift replies!
@bcotton We have agreed on deferring the golang 1.17 and modular obsoletes and EOL change to F36. The remaining ones have already been implemented or are deferred/rejected.
Metadata Update from @defolos: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Just for clarity, yes the GNU Toolchain update for F35 was complete, we have GCC 11.2, GLIBC 2.34, GDB 10.2 and BINUTILS 2.37 all in F35 as expected. I was out for a few days so I'm responding late here, but we're all good t go for F35.
Login to comment on this ticket.