Roadmap

Version 18.11 (2018 November)

• new device specification (devargs) syntax
• ability to use externally allocated memory
• power management: traffic pattern aware power control
• add MPLS to rte_flow encapsulation API
• add metadata matching in rte_flow API
• mlx5: add BlueField representors
• mlx5: support VXLAN and MPLS encapsulations
• failure handler for PCIE hardware hotplug
• virtual device hotplug
• tap and failsafe support in multi-process
• classification and metering in SoftNIC
• IPsec library
• crypto in Packet Framework
• FIPS test suite
• AES-CMAC in QAT
• QAT compression enhancements
• compression performance test app
• eventdev ordered and atomic queues for DPAA2
• extended table in hash library
• telemetry API
• libedit integration
• noisy VNF forward mode in testpmd
• vDPA sample application

Nice to have - Future

• multi-process rework
• automatic UIO/VFIO binding
• infiniband driver class (ibdev)
• default configuration from files
• generic white/blacklisting

Cycle model

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.

Scheduling

18.11 (LTS)

• Proposal deadline: September 7, 2018
• Integration deadline: October 5, 2018
• Release: November 2, 2018

Stable Releases

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 stable@dpdk.org only (avoiding dev@dpdk.org).

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.