The Jammy update can only be released after the fix is also present in Mantic, Noble (LTS), and Oracular.
It is a requirement[1][2] of the SRU process that all releases up to the development one (currently Oracular) have the fix, to prevent users who upgrade to the next ubuntu release experience a regression. In particular, in the case of a fingerprint reader, such an upgrade could even prevent login if the support for that reader is suddenly gone in the next ubuntu release.
Regarding this comment:
> @Andreas, The main reason is that the fix is for oem hardware enablement and those target LTS series.
I understand the focus on the LTS releases (noble became one after this bug was filed). Note the updated package is landing in the ubuntu archive, not some oem-specific repository, so it will be available to all ubuntu users. Therefore, I believe the do-not-regress-on-release-upgrades principle still applies.
The Jammy update can only be released after the fix is also present in Mantic, Noble (LTS), and Oracular.
It is a requirement[1][2] of the SRU process that all releases up to the development one (currently Oracular) have the fix, to prevent users who upgrade to the next ubuntu release experience a regression. In particular, in the case of a fingerprint reader, such an upgrade could even prevent login if the support for that reader is suddenly gone in the next ubuntu release.
Regarding this comment:
> @Andreas, The main reason is that the fix is for oem hardware enablement and those target LTS series.
I understand the focus on the LTS releases (noble became one after this bug was filed). Note the updated package is landing in the ubuntu archive, not some oem-specific repository, so it will be available to all ubuntu users. Therefore, I believe the do-not- regress- on-release- upgrades principle still applies.
1. https:/ /wiki.ubuntu. com/StableRelea seUpdates# Newer_Releases /wiki.ubuntu. com/StableRelea seUpdates# General_ Requirements
2. https:/