> No, those are two different exceptions. If you're doing hardware enablement, then this bug should be titled something like "hardware X not supported", and then the impact to users would be self-evident. If you're fixing bugs, then https://documentation.ubuntu.com/sru/en/latest/reference/requirements/#new- upstream-microreleases applies, and you should document how it is that upstream meets the requirements documented there. Which is it?
It is both. According to the upstream changelog [1], it contains the following HWE features: > Added support for OVS-DOCA live upgrade of virtual switch > ... https://docs.nvidia.com/doca/archive/2-9-1/changes+and+new+features/index.html And the following bug fixes: > Description: rte_eth_dev_start() performs unnecessary recreation of mlx5 > control flow rules, resulting in increased delay of rte_eth_dev_start(). > ... https://docs.nvidia.com/doca/archive/2-9-1/bug+fixes+in+this+version/index.html I am using this paragraph from the requirements: > For Long Term Support releases we sometimes want to introduce new features. They must not change the behaviour on existing installations (e. g. entirely new packages are usually fine). If existing software needs to be modified to make use of the new feature, it must be demonstrated that these changes are non-intrusive, have a minimal regression potential, and have been tested properly. To avoid regressions on upgrade, any such feature must then also be added to any newer supported Ubuntu release. Once a new feature/package has been introduced, subsequent changes to it are subject to the usual requirements of SRUs to avoid regressions. Regarding upstream microrelease: > The upstream QA process must be documented/demonstrated and linked from the SRU tracking bug. In other cases where such upstream automatic testing is not available, exceptions must still be approved by at least one member of the Ubuntu Technical Board. To my knowledge the upstream QA process is not public and we are applying our own (private) QA testing on Noble cloud machines as explained. If this needs TC exception, then so be it. The impact is so low as the package was first published into oracular-updates ~2 weeks ago. I think it would be a waste of the TC's time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100003 Title: backport mofed-modules-24.10 24.10.1.1.4.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mofed-modules-24.10/+bug/2100003/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
