On Tuesday, 23 August we reached the Change Checkpoint: Completion deadline (100% complete). At this milestone all the F37 Changes should be fully complete, 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. 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, if any, should be taken.
Golang 1.19 Owner: @alexsaezm @jcajka Contingency mechanism: Reverting to golang version 1.18.X Contingency deadline: Beta freeze
I believe this has already been completed. golang was updated to 1.19 before the mass rebuild.
golang
Enable read only /sysroot for Fedora Silverblue & Kinoite Owner: @siosm @tpopela @jkonecny
Moved to ON_QA. Complete for Silverblue & Kinoite. IoT has some issues under investigation.
Make Fedora CoreOS a Fedora Edition Owner: @cverna Contingency mechanism: Delay promotion until F38 Contingency deadline: Final release date
Moved to ON_QA. We are still closely working the Fedora QA on the release criteria but this should not be blocking us at this stage.
Metadata Update from @churchyard: - Issue tagged with: meeting
agreed LegacyXorgDriverRemoval, Drop NIS(+) support from PAM, Retire the NIS(+) user-space utility programs and Build all JDKs in Fedora against in-tree libraries and with static stdc++lib system-wide changes are defered to F38. Return Cloud Base to Edition Status and LLVM 15 still have time to land in F37. Build Fedora IoT artifacts with osbuild and Preset all systemd units on first boot can land in Fedora 37 only if they make it to the beta release, otherwise they are deferred to Fedora 38. (+5,0,0)
Metadata Update from @kevin: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Hello! I just now learned that https://fedoraproject.org/wiki/Changes/JdkInTreeLibsAndStdclibStatic was deferred . We can not afford it, and the feature is done. My apologise for unexpected delay, I would really like to not revert the patches, it was not eassy to put them togehter for all jdks safely. And the buils were finsihed yesterday, and udpate filled today. Unluckily, during filling of the update I found this comment. Thought
The change was approved with "Contingency deadline: before f37 Beta freeze". Why have you pushed an updated after the Beta release then?
Metadata Update from @churchyard: - Issue status updated to: Open (was: Closed)
Reopening for visibility.
I've edited https://bodhi.fedoraproject.org/updates/FEDORA-2022-8cc5b13278 to disable autopush until this is resolved here. Do not push the update to stable manually.
Becasue we had severe troubles to do in time
anyway.. it was my bad that I overlooked the timing, and simialrly it was my bad that I overloked the issue as derrefered and thus pushed changes. The communication between jdk maintainers were quite broknje due to random vacation, but that do not exuse me from doing this. IS there some way to move forward?
yet agian, may apologise for missing both super important parts
I personally think is should be OK, to land now as long as the QA folks are fine with that. But let's wait for others.
ok. Thank you. Sure.
I've included this in the meeting agenda for tomorrow. @jvanek It might help if you show up and have some confirmation from the QA folks that they are OK with shipping it.
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/JXDLRU673J5XUCXAVTE5BKTGKDVY3RKG/
Hello!
TY. Will do my best to appear here.
Actully, if it can be as close to 17:00 as possible, eg as first thing to discuss, would be very helpfull). TYVM!
That is the plan. It is 17:00 UTC, hence 19:00 CEST.
Thanx, I'm actually in London now. Thus 18:00 UK if I count correctly. Still will do my best to connect somehow somewhen
The update may be shipped after Fedora 37 Beta release, before the Fedora 37 Final Freeze. (+7,0,-0)
https://meetbot.fedoraproject.org/fedora-meeting/2022-09-20/fesco.2022-09-20-17.00.html
Metadata Update from @churchyard: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.