DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com,
	bluca@debian.org
Cc: stable@dpdk.org, yskoh@mellanox.com, Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-dev] [PATCH] doc: update DPDK LTS versions
Date: Fri, 22 Mar 2019 11:29:35 +0000	[thread overview]
Message-ID: <20190322112935.3056-1-ktraynor@redhat.com> (raw)
Message-ID: <20190322112935.Of5qNyOtFPAGklsScQQZ3-1kBI3EieboPZk-2JjiWiE@z> (raw)

Support for 16.11 has ended. 17.11 and 18.11 are the current LTSs.

Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
 doc/guides/contributing/stable.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst
index 2ac4f0a88..4214103b3 100644
--- a/doc/guides/contributing/stable.rst
+++ b/doc/guides/contributing/stable.rst
@@ -49,5 +49,5 @@ agreement and a commitment from a maintainer. The current policy is that each
 year's November release will be maintained as an LTS for 2 years.
 
-The current DPDK LTS releases are 16.11 and 17.11.
+The current DPDK LTS releases are 17.11 and 18.11.
 
 It is anticipated that there will be at least 4 releases per year of the LTS
-- 
2.20.1


             reply	other threads:[~2019-03-22 11:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 11:29 Kevin Traynor [this message]
2019-03-22 11:29 ` Kevin Traynor
2019-03-22 13:29 ` Luca Boccassi
2019-03-22 13:29   ` Luca Boccassi
2019-03-27 11:23   ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-03-27 11:23     ` Thomas Monjalon

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=20190322112935.3056-1-ktraynor@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=stable@dpdk.org \
    --cc=yskoh@mellanox.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).