It sounds like this type of update would qualify under the same principle that MAAS (were it still in the archive) adds new features to stable releases.
However, please see the requirements at https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases. Specifically: I see no upload for Hirsute, but this is a requirement for new features in an LTS so that there isn't a regression and lack of ability to receive updates if users upgrade from the updated Focal to Hirsute. Please provide an upload for Hirsute. It must be demonstrated that the changes you propose are unintrusive, have a minimal regression potential, and have been tested properly. You could cherry-pick the required features, or you could update to a newer upstream release wholesale as you're proposing. Please provide an analysis and explanation as to why you think the latter approach is better in this case with respect to these requirements, and what you're doing to meet them. For example, I see nothing in your Test Plan that seeks to ensure that unrelated behaviour in this package has not regressed; nor do I see any analysis of the upstream changes to ensure that functional/behavioural changes have not been made. And what about other non-MAAS use cases for this package that users might have established? How do you intend to mitigate regressing such use cases? ** Changed in: zhmcclient (Ubuntu Focal) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919451 Title: Update (python-)zhmcclient to latest release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
