From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] update roadmap after 18.02 release
Date: Mon, 26 Feb 2018 12:21:35 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23EEC4DD7@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20180222092854.8213-1-thomas@monjalon.net>
> -----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
prev parent reply other threads:[~2018-02-26 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 9:28 Thomas Monjalon
2018-02-26 12:19 ` Mcnamara, John
2018-02-26 14:18 ` Thomas Monjalon
2018-02-26 12:21 ` Mcnamara, John [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B27915DBBA3421428155699D51E4CFE23EEC4DD7@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).