DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nirmoy Das <ndas@suse.de>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] RFC: DPDK Long Term Support
Date: Mon, 6 Jun 2016 15:44:47 +0200	[thread overview]
Message-ID: <57557E4F.4060808@suse.de> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20257B8E3@IRSMSX103.ger.corp.intel.com>


> 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.

regards,
Nirmoy
-- 
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB
21284 (AG Nürnberg) Maxfeldstr. 5
D-90409 Nürnberg / Phone: +49-911-740 18-4

  parent reply	other threads:[~2016-06-06 13:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 15:07 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 [this message]
2016-06-06 14:16   ` Yuanhan Liu
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=57557E4F.4060808@suse.de \
    --to=ndas@suse.de \
    --cc=dev@dpdk.org \
    --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 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).