From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>,
dev@dpdk.org, john.mcnamara@intel.com,
marko.kovacevic@intel.com
Cc: stable@dpdk.org, yskoh@mellanox.com
Subject: Re: [dpdk-dev] [PATCH] doc: update DPDK LTS versions
Date: Fri, 22 Mar 2019 13:29:33 +0000 [thread overview]
Message-ID: <231d0d9cf908e87ce118262626367493b56b8ca3.camel@debian.org> (raw)
Message-ID: <20190322132933.QLzzWyDvPdQE_riwncdK2hGeCwvlrMhRBjvyapHMhvw@z> (raw)
In-Reply-To: <20190322112935.3056-1-ktraynor@redhat.com>
On Fri, 2019-03-22 at 11:29 +0000, Kevin Traynor wrote:
> 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
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-03-22 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 11:29 Kevin Traynor
2019-03-22 11:29 ` Kevin Traynor
2019-03-22 13:29 ` Luca Boccassi [this message]
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=231d0d9cf908e87ce118262626367493b56b8ca3.camel@debian.org \
--to=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.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).