From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dpdk stable <stable@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Next Stable Release?
Date: Tue, 23 May 2017 17:19:47 +0800 [thread overview]
Message-ID: <20170523091947.GT2276@yliu-dev> (raw)
In-Reply-To: <AM2PR04MB0753EA8499C79C4ED1DAF54089F90@AM2PR04MB0753.eurprd04.prod.outlook.com>
On Tue, May 23, 2017 at 09:05:38AM +0000, Hemant Agrawal wrote:
> Which is the next DPDK LTS release?
There is no answer yet. It could be v18.11. There was also a request for
proposing v17.11 to be the next LTS.
> Is 17.05 a DPDK LTS release?
Nope, it's not in the plan.
> Do we need to send a copy to stable@dpdk.org for any fixes on 17.05?
What you just need to do is to put following tag in the commit log.
Cc: stable@dpdk.org
--yliu
prev parent reply other threads:[~2017-05-23 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 9:05 Hemant Agrawal
2017-05-23 9:19 ` Yuanhan Liu [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=20170523091947.GT2276@yliu-dev \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=stable@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).