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.
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.
This bug tracks an update for the DPDK packages in:
- Lunar (-proposed) 22.11.2 -> 22.11.3
- Jammy (-proposed) 21.11.4 -> 21.11.5
This update includes bugfixes only following the SRU policy exception defined at https:/ /wiki.ubuntu. com/StableRelea seUpdates/ 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. /bugs.launchpad .net/ubuntu/ +source/ dpdk/+bug/ 1784816 /bugs.launchpad .net/ubuntu/ +source/ dpdk/+bug/ 1817675 /bugs.launchpad .net/ubuntu/ +source/ dpdk/+bug/ 1836365 /bugs.launchpad .net/ubuntu/ +source/ dpdk/+bug/ 1912464 /bugs.launchpad .net/ubuntu/ +source/ dpdk/+bug/ 1940913 /bugs.launchpad .net/ubuntu/ +source/ dpdk/+bug/ 2002404 /bugs.launchpad .net/ubuntu/ +source/ dpdk/+bug/ 2026351
For Reference - former cases are here:
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
[Major Changes]
Listed by upstream in detail
Lunar - 22.11.3: /doc.dpdk. org/guides- 22.11/rel_ notes/release_ 22_11.html# id3
https:/
Jammy - 21.11.5: /doc.dpdk. org/guides- 21.11/rel_ notes/release_ 21_11.html# id13
https:/
[Test Plan]
See https:/ /wiki.ubuntu. com/StableRelea seUpdates/ 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.