#2764 F36 incomplete changes: 100% complete deadline
Closed: Accepted 2 years ago by churchyard. Opened 2 years ago by bcotton.

On Tuesday, 22 February we reached the Change Checkpoint: Completion deadline (100% complete). At this milestone all the F36 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 "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, if any, should be taken.

Self-Contained Changes


Metadata Update from @bcotton:
- Issue tagged with: meeting

2 years ago

Tagging for the next meeting since it will almost certainly require discussion.

Install only newly recommended packages on upgrades with dnf/PackageKit/microdnf
The feature is fully implemented and delivered
We also delivered patch that resolved recently discovered issue (Bug 2033130 - exclude_from_weak_autodetect=true effectively renders rich weak dependencies useless)
* I apology for not updating of tracking bugzilla to ON_QA status.

From yesterday's meeting:

#agreed (+5,0,-0) DNS over TLS - set ON_QA; LLVM 14 - is on track; java-17-openjdk as system JDK in F36 - set ON_QA; glibc32 build adjustments - defer to f37; No ifcfg by default - OK if it makes the beta release, defer to f37 otherwise

I'll untag this with meeting but leave it open until after the F36 Beta to see if the "No ifcfg by default" Change lands.

Metadata Update from @bcotton:
- Issue untagged with: meeting

2 years ago

No ifcfg by default - OK if it makes the beta release, defer to f37 otherwise

The tracker bug is set at ON_QA. The update went stable before the Beta release.

Metadata Update from @churchyard:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata