From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Nirmoy Das <ndas@suse.de>
Cc: dev@dpdk.org, Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: RFC: DPDK Long Term Support
Date: Mon, 6 Jun 2016 22:16:55 +0800 [thread overview]
Message-ID: <20160606141655.GF10038@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <57557E4F.4060808@suse.de>
On Mon, Jun 06, 2016 at 03:44:47PM +0200, Nirmoy Das wrote:
>
> > LTS Version
> > ------------
> >
> > The proposed initial LTS version will be DPDK 16.07. The next versions, based
> > on a 2 year cycle, will be DPDK 18.08, 20.08, etc.
>
> Hi,
>
> I can see 16.07's release due date is 18th July. Is it possible to know
> the timeline for RC versions of dpdk-16.07 ? This might be helpful for
> SUSE to decide the supported product(SLE12 SP*/Leap) for dpdk-lts.
You can get it from http://dpdk.org/dev/roadmap:
16.07
Proposal deadline: May 8
Integration deadline: June 16
Release: July 18
In another word, we're gona have 1st RC release in less then 2 weeks.
--yliu
next prev parent reply other threads:[~2016-06-06 14:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 15:07 RFC: DPDK Long Term Support Mcnamara, John
2016-06-03 16:05 ` Thomas Monjalon
2016-06-06 11:49 ` Yuanhan Liu
2016-06-06 13:31 ` Thomas Monjalon
2016-06-06 14:14 ` Yuanhan Liu
2016-06-06 14:23 ` Thomas Monjalon
2016-06-07 13:17 ` Mcnamara, John
2016-06-03 18:17 ` Matthew Hall
2016-06-07 12:53 ` Mcnamara, John
2016-06-05 18:15 ` Neil Horman
2016-06-06 9:27 ` Thomas Monjalon
2016-06-06 13:47 ` Neil Horman
2016-06-06 14:21 ` Thomas Monjalon
2016-06-06 15:07 ` Neil Horman
2016-06-07 16:21 ` Mcnamara, John
2016-06-07 15:55 ` Mcnamara, John
2016-06-06 13:44 ` Nirmoy Das
2016-06-06 14:16 ` Yuanhan Liu [this message]
2016-06-07 12:36 ` Christian Ehrhardt
2016-06-07 19:39 ` Martinx - ジェームズ
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=20160606141655.GF10038@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=ndas@suse.de \
--cc=thomas.monjalon@6wind.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.