Mint’s monthly post shows a simpler kernel policy, but it explicitly introduces upcoming work. The available HWE installation images and the previewed administration features have different statuses.
Read the preview label first
The July monthly news published in August says the described improvements are work in progress. HWE images with kernel 7.0 are separately announced as available. The planned administration tool brings kernel-series tracking to Mint and LMDE, weekly cleanup and a removal history. Protected kernels are excluded from cleanup; tracking an unknown custom series does not give the tool knowledge of how to update it.
These distinctions matter more than simply moving a button out of Update Manager. Check the installed tool’s version and documentation before assuming the preview is present on a current machine.
Protect a tested fallback, not an arbitrary count
The cover is a decision map: a protected kernel remains protected; a known tracked series gets the documented update path; a custom tracked series still needs its own update arrangement. An untracked, unprotected series is eligible for the cleanup described in the announcement.
Imagine two older kernels, one verified with the machine’s storage and networking and another never booted. Retaining two versions by count does not by itself establish which is a working fallback. Record a successful boot and the important devices before relying on it. The running kernel and the newest installed kernel can differ until a reboot, so record both states when diagnosing an update.
There is no universal safe retention count for every boot partition and regression history. The useful outcome is recoverability within available space, not collecting versions or deleting them indiscriminately.
An environment setting is inherited at process launch
The preview also offers environment variables for graphical and/or console sessions. Consider a fictional editor already running when a setting changes. Its existing process does not automatically inherit a replacement environment from a file edited later. A terminal started through a different session path may therefore behave differently without either observation being invented.
Test a newly started application in the intended session and compare the variable it actually receives. This is more informative than declaring the page a universal fix for every desktop environment issue. It also avoids copying shell syntax into configuration whose parser may use different rules.
September 8: identify the monthly post as a development preview; add protected-kernel and custom-series distinctions and remove blanket purge advice.