Comment 0 for bug 1647945

DPDK finally has established a stable release process.
The first update out of this is the 16.07.2 release which this shall make available on Yakkety.

Upstream maintenance of the stable release is at http://dpdk.org/browse/dpdk-stable/
The summary "changelog" of the stable release(s) is at http://dpdk.org/doc/guides-16.07/rel_notes/release_16_07.html#fixes-in-stable-release

I'd consider this well tested for an MRE release from Upstream:
- upstream integrated Autotest suite
- Upstream has a CI Lab driven by Intel running on RC&Releases (Link FYI https://dpdksummit.com/Archive/pdf/2016Userspace/Day02-Session10-QianXu-Userspace2016.pdf)
- the purpose of the (rather new) stable branch is to provide an API/ABI stable set of fixes to downstreams
- These tests run on commit (verification) and larger tests on RC/Releases

In addition I on the packaged-into-ubuntu side we have:
- autopkgtests, but due to the nature of DPDK those can only really test the runtime bits (like service invocation)
- a testing project at https://code.launchpad.net/~ubuntu-server/ubuntu/+source/dpdk-testing/+git/dpdk-testing which I ran against new uploads as a gating check
  - this runs the package autotests (in a manner knowing about the remaining false positives)
  - this also runs some of the bundled examples l2fwd, testpmd and finally the only "in archive
    exploiter" we have so far in OpenvSwitch-DPDK (functional and performance checks)

I'll attach the log of the testing once it completes against a ppa with the proposed changes, but wanted to start the MRE discussion/process already.