Major known features and milestones may be noted here. This list is obviously neither complete nor guaranteed.
A typical release should be done after 3 months.
It is designed to allow DPDK to keep evolving at a rapid pace while giving enough opportunity to review, discuss and improve the contributions.
The merge window will open once the previous release is complete. First version of a new feature must be submitted before the proposal deadline. Features that miss this first period will be deferred until the next release.
Updated versions of patches (v2, v3, etc.) will be submitted to address comments. The new features must be properly reviewed, tested and accepted before the integration deadline. Otherwise, they will be postponed to the next releases.
At the end of the merge window, the first release candidate is out.
The last period is 1 month long and is dedicated to bug fixing.
There is a documentation page describing the guidelines of the stable releases.
Stable point releases follow mainline releases.
After each -rc tag and after the final version, relevant bug fixes get backported by the stable maintainers into the respective branches in "bursts".
Developers can provide stable-specific patches by sending them to firstname.lastname@example.org only (avoiding email@example.com).
After all the relevant bugfixes have been backported, regression tests are ran, and if clear, the stable release is announced.
Typically a new stable release version follows a mainline release by 1-2 weeks, depending on the test results.
|Next version||Date||End of life||Maintainer|
|16.11.8||August 14, 2018||November 2018 (LTS)||Luca Boccassi|
|17.11.3||June 15, 2018||November 2019 (LTS)||Yuanhan Liu|
|18.02.2||June 15, 2018||June 2018||Luca Boccassi|
|18.05.1||August 24, 2018||August 2018||Christian Ehrhardt|
|18.08.1||November 16, 2018||November 2018||looking for volunteer|
|18.11.1||January 11, 2019||November 2020 (LTS)||Kevin Traynor|