[dpdk-web] [PATCH] update roadmap after 18.02 release

[dpdk-web] [PATCH] update roadmap after 18.02 release

[Thomas Monjalon]

Some features not implemented in 18.02 are kept in the 18.05 roadmap.

The dates are adjusted to be more realistic:
- more time before the proposal deadline
- 4 weeks for for integration in RC1
- 4 weeks for bugs fixing after RC1
- more time in July/August summer

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---

PLEASE CONFIRM the features which are kept in 18.05 roadmap,
and ADD new features by sending description or RFC to dev@dpdk.org
plus a roadmap patch to web@dpdk.org.

Thanks

---
 dev/roadmap.html | 29 +++++++----------------------
 1 file changed, 7 insertions(+), 22 deletions(-)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index a2fea2f..569d8b8 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -41,27 +41,18 @@
 	<h2>Development roadmap</h2>
 	<p>Major known features and milestones may be noted here.
 	This list is obviously neither complete nor guaranteed.
-	<h3 id="1802">Version 18.02 (2018 February)</h3>
+	<h3 id="1805">Version 18.05 (2018 May)</h3>
 	<ul>
-		<li>meson/ninja build system
 		<li>memory management rework
-		<li>hotplug, notifications and device ownership
+		<li>hotplug
 		<li>new device specification (devargs) syntax
 		<li>secondary process support in virtual devices
 		<li>ethdev port representor driver
-		<li>adaptive virtual function (AVF) driver
 		<li>ARM support for ark
-		<li>qede tunneling offloads
 		<li>mlx5 IPsec offload
-		<li>security protocol offload support for DPAA
-		<li>virtual address support for DPAA2
 		<li>virtio-crypto driver
-		<li>eventdev driver for DPAA
 		<li>eventdev ordered and atomic queues for DPAA2
-		<li>eventdev optimized packet distribution library (OPDL) driver
 		<li>eventdev crypto adapter
-		<li>base band device class (bbdev)
-		<li>raw device class
 		<li>libedit integration
 	</ul>
 	<h3 id="future">Nice to have - Future</h3>
@@ -87,28 +78,22 @@
 	<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>18.02
-	<ul>
-		<li>Proposal deadline: November 30, 2017
-		<li>Integration deadline: January 10, 2018
-		<li>Release: February 5, 2018
-	</ul>
 	<p>18.05
 	<ul>
-		<li>Proposal deadline: February 28, 2018
-		<li>Integration deadline: March 30, 2018
+		<li>Proposal deadline: March 9, 2018
+		<li>Integration deadline: April 6, 2018
 		<li>Release: May 4, 2018
 	</ul>
 	<p>18.08
 	<ul>
-		<li>Proposal deadline: May 25, 2018
+		<li>Proposal deadline: June 1, 2018
 		<li>Integration deadline: June 29, 2018
 		<li>Release: August 1, 2018
 	</ul>
 	<p>18.11
 	<ul>
-		<li>Proposal deadline: August 31, 2018
-		<li>Integration deadline: September 28, 2018
+		<li>Proposal deadline: September 7, 2018
+		<li>Integration deadline: October 5, 2018
 		<li>Release: November 2, 2018
 	</ul>
 </section>
-- 
2.15.1

Re: [dpdk-web] [PATCH] update roadmap after 18.02 release

[Mcnamara, John]

> -----Original Message-----
> From: web [mailto:web-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, February 22, 2018 9:29 AM
> To: web@dpdk.org
> Subject: [dpdk-web] [PATCH] update roadmap after 18.02 release
> 
> Some features not implemented in 18.02 are kept in the 18.05 roadmap.
> 
> The dates are adjusted to be more realistic:
> - more time before the proposal deadline
> - 4 weeks for for integration in RC1
> - 4 weeks for bugs fixing after RC1
> - more time in July/August summer
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>

Acked-by: John McNamara <john.mcnamara@intel.com>

Re: [dpdk-web] [PATCH] update roadmap after 18.02 release

[Mcnamara, John]

> -----Original Message-----
> From: web [mailto:web-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, February 22, 2018 9:29 AM
> To: web@dpdk.org
> Subject: [dpdk-web] [PATCH] update roadmap after 18.02 release
> 
> Some features not implemented in 18.02 are kept in the 18.05 roadmap.
> 
> The dates are adjusted to be more realistic:
> - more time before the proposal deadline
> - 4 weeks for for integration in RC1
> - 4 weeks for bugs fixing after RC1
> - more time in July/August summer


Hi Thomas,

The Hotplug feature has also been added in the patch from Brian Archbold (with a slightly longer description).

John

> ---
> 
> PLEASE CONFIRM the features which are kept in 18.05 roadmap, and ADD new
> features by sending description or RFC to dev@dpdk.org plus a roadmap
> patch to web@dpdk.org.
> 
> Thanks
> 
> ---
>  dev/roadmap.html | 29 +++++++----------------------
>  1 file changed, 7 insertions(+), 22 deletions(-)
> 
> diff --git a/dev/roadmap.html b/dev/roadmap.html index a2fea2f..569d8b8
> 100644
> --- a/dev/roadmap.html
> +++ b/dev/roadmap.html
> @@ -41,27 +41,18 @@
>  	<h2>Development roadmap</h2>
>  	<p>Major known features and milestones may be noted here.
>  	This list is obviously neither complete nor guaranteed.
> -	<h3 id="1802">Version 18.02 (2018 February)</h3>
> +	<h3 id="1805">Version 18.05 (2018 May)</h3>
>  	<ul>
> -		<li>meson/ninja build system
>  		<li>memory management rework
> -		<li>hotplug, notifications and device ownership
> +		<li>hotplug
>  		<li>new device specification (devargs) syntax
>  		<li>secondary process support in virtual devices
>  		<li>ethdev port representor driver
> -		<li>adaptive virtual function (AVF) driver
>  		<li>ARM support for ark
> -		<li>qede tunneling offloads
>  		<li>mlx5 IPsec offload
> -		<li>security protocol offload support for DPAA
> -		<li>virtual address support for DPAA2
>  		<li>virtio-crypto driver
> -		<li>eventdev driver for DPAA
>  		<li>eventdev ordered and atomic queues for DPAA2
> -		<li>eventdev optimized packet distribution library (OPDL)
> driver
>  		<li>eventdev crypto adapter
> -		<li>base band device class (bbdev)
> -		<li>raw device class
>  		<li>libedit integration
>  	</ul>
>  	<h3 id="future">Nice to have - Future</h3> @@ -87,28 +78,22 @@
>  	<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>18.02
> -	<ul>
> -		<li>Proposal deadline: November 30, 2017
> -		<li>Integration deadline: January 10, 2018
> -		<li>Release: February 5, 2018
> -	</ul>
>  	<p>18.05
>  	<ul>
> -		<li>Proposal deadline: February 28, 2018
> -		<li>Integration deadline: March 30, 2018
> +		<li>Proposal deadline: March 9, 2018
> +		<li>Integration deadline: April 6, 2018
>  		<li>Release: May 4, 2018
>  	</ul>
>  	<p>18.08
>  	<ul>
> -		<li>Proposal deadline: May 25, 2018
> +		<li>Proposal deadline: June 1, 2018
>  		<li>Integration deadline: June 29, 2018
>  		<li>Release: August 1, 2018
>  	</ul>
>  	<p>18.11
>  	<ul>
> -		<li>Proposal deadline: August 31, 2018
> -		<li>Integration deadline: September 28, 2018
> +		<li>Proposal deadline: September 7, 2018
> +		<li>Integration deadline: October 5, 2018
>  		<li>Release: November 2, 2018
>  	</ul>
>  </section>
> --
> 2.15.1

Re: [dpdk-web] [PATCH] update roadmap after 18.02 release

[Thomas Monjalon]

> > Some features not implemented in 18.02 are kept in the 18.05 roadmap.
> > 
> > The dates are adjusted to be more realistic:
> > - more time before the proposal deadline
> > - 4 weeks for for integration in RC1
> > - 4 weeks for bugs fixing after RC1
> > - more time in July/August summer
> > 
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> 
> Acked-by: John McNamara <john.mcnamara@intel.com>

Applied