Comment 0 for bug 2067480

Revision history for this message
Miriam EspaƱa Acebal (mirespace) wrote : MRE updates 23.11.1 (Noble)/22.11.5(Mantic)/21.11.7(Jammy)/

23.11.1 for Oracular is in -proposed and nearly to be completed. Therefore the MREs for Noble, Mantic and Jammy can be handled now (Mantic EOL will occur at the end of July, so we're trying to update it before it happens, but it might be optional at the end).

This bug tracks an update for the DPDK packages in:
- Noble 23.11 -> 23.11.1
- Mantic 22.11.4 -> 22.11.5
- Jammy 21.11.6 -> 21.11.7

This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/StableReleaseUpdates/DPDK.

No new features added; a classic stable release with a bunch of fixes aggregated and enhanced testing by the companies being part of the DPDK community.

[Impact]

Stable release update so not directly applicable; see the exception policy document linked above.
For Reference - former cases are here:
- https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1784816
- https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1817675
- https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1836365
- https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1912464
- https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1940913
- https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2002404
- https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2026351

[Major Changes]

Listed by upstream in detail

Noble - 23.11.1:
https://doc.dpdk.org/guides-23.11/rel_notes/release_23_11.html#release-notes

Mantic - 22.11.5:
https://doc.dpdk.org/guides-22.11/rel_notes/release_22_11.html#id11

Jammy - 21.11.6:
https://doc.dpdk.org/guides-21.11/rel_notes/release_21_11.html#id17
[Test Plan]

See https://wiki.ubuntu.com/StableReleaseUpdates/DPDK#SRU_TestVerify

[Regression Potential]

Upstream performs extensive testing before release, giving us a high degree of confidence in the general case. There problems are most likely to manifest in Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters.
Therefore that is what our verification focuses on.