Re: [dpdk-web] [PATCH 1/2] remove 17.08 from roadmap

[Maxime Coquelin <maxime.coquelin@redhat.com>]

On 08/30/2017 11:43 PM, Thomas Monjalon wrote:
> Some features non implemented in 17.08 are moved to 17.11.
> A new section "Future" is created to add things which would
> be nice to have but no one committed to work on it.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>   dev/roadmap.html | 33 ++++++---------------------------
>   1 file changed, 6 insertions(+), 27 deletions(-)

For vhost-user IOMMU support:
Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime

> diff --git a/dev/roadmap.html b/dev/roadmap.html
> index b72230d..6c9d85b 100644
> --- a/dev/roadmap.html
> +++ b/dev/roadmap.html
> @@ -41,37 +41,22 @@
>   	<h2>Development roadmap</h2>
>   	<p>Major known features and milestones may be noted here.
>   	This list is obviously neither complete nor guaranteed.
> -	<h3 id="1708">Version 17.08 (2017 August)</h3>
> +	<h3 id="1711">Version 17.11 (2017 November)</h3>
>   	<ul>
> -		<li>Hotplug Notification
>   		<li>Vhost-user IOMMU support
> -		<li>Xen Netfront Driver
> -		<li>Fail Safe driver
> -		<li>Enhance bnxt driver and update the HWRM version
> -		<li>Enic flow API support
> -		<li>Interrupt Mode for mlx4 Rx
> -		<li>RSS via Flow API for mlx5
> -		<li>New mlx5 data path for SSE
> -		<li>Generic Flow Enhancements for Intel drivers
> -		<li>Packet Type Recognition in ixgbe for SSE
> -		<li>NXP DPAA2 PMD Performance and Feature Enhancements
> -		<li>NXP DPAA2 Eventdev Driver
>   		<li>NXP DPAA1 Bus, Mempool and PMD
>   		<li>ARM Architecture support in Atomic Rules Arkville Driver
>   		<li>VF Restore after PF Reset
> -		<li>Isolated mode in Flow API
> -		<li>Generic QoS API
> -		<li>Generic Receive Offload
> -		<li>Cryptodev Multi-Core SW Scheduler
> -	</ul>
> -	<h3 id="1711">Version 17.11 (2017 November)</h3>
> -	<ul>
> -		<li>Automatic Device Binding
>   	</ul>
>   	<h3 id="1802">Version 18.02 (2018 February)</h3>
>   	<ul>
>   		<li>
>   	</ul>
> +	<h3 id="future">Nice to have - Future</h3>
> +	<ul>
> +		<li>Hotplug Notification
> +		<li>Automatic Device Binding
> +	</ul>
>   	<h3 id="cycle">Cycle model</h3>
>   	<p>A typical release should be done after 3 months.
>   	<p>It is designed to allow DPDK to keep evolving at a rapid pace while
> @@ -85,12 +70,6 @@
>   	<p>At the end of the merge window, the first release candidate is out.
>   	<p>The last period is 1 month long and is dedicated to bug fixing.
>   	<h3 id="dates">Scheduling</h3>
> -	<p>17.08
> -	<ul>
> -		<li>Proposal deadline: May 28
> -		<li>Integration deadline: June 29
> -		<li>Release: August 1
> -	</ul>
>   	<p>17.11
>   	<ul>
>   		<li>Proposal deadline: August 25, 2017
>