From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: dev@dpdk.org
Subject: Re: 17.02 Roadmap
Date: Wed, 31 Aug 2016 14:07:40 +0200 [thread overview]
Message-ID: <2859434.lVGgMqpo08@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA675B672A@IRSMSX108.ger.corp.intel.com>
2016-08-31 10:31, O'Driscoll, Tim:
> Below are the features that we're planning to submit for the 17.02
> release. We'll submit a patch to update the roadmap page with this info.
>
> Some things will obviously change during planning/development, so we'll
> provide a more detailed update in late September/early October.
> After that, things should hopefully be relatively stable.
>
> It would be good if others are also willing to share their plans so
> that we can build up a complete picture of what's planned for 17.02
> and make sure there's no duplication.
Thanks Tim. I would like to stress that it would be really better to
know the intents of the other contributors.
next prev parent reply other threads:[~2016-08-31 12:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 10:31 17.02 Roadmap O'Driscoll, Tim
2016-08-31 12:07 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-10 16:13 O'Driscoll, Tim
2016-10-10 20:42 ` Thomas Monjalon
2016-10-11 5:32 ` Yuanhan Liu
2016-10-11 9:09 ` O'Driscoll, Tim
2016-10-11 10:25 ` Pattan, Reshma
2016-10-11 22:36 ` De Lara Guarch, Pablo
2016-10-13 3:15 ` Tan, Jianfeng
2016-10-13 14:18 ` Hunt, David
2016-10-13 14:39 ` Thomas Monjalon
2016-10-14 17:29 ` Stephen Hemminger
2016-10-14 20:18 ` Thomas Monjalon
2016-10-16 20:21 ` O'Driscoll, Tim
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=2859434.lVGgMqpo08@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=tim.odriscoll@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.