From: David Marchand <david.marchand@redhat.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: web@dpdk.org, Luca Boccassi <bluca@debian.org>,
Thomas Monjalon <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] release 18.11.11
Date: Wed, 20 Jan 2021 16:01:28 +0100 [thread overview]
Message-ID: <CAJFAV8zbFeLGwLs8AbKsr2Bn_gp52edEv948bQAicQsfQFWmqg@mail.gmail.com> (raw)
In-Reply-To: <20210120144451.385232-1-ktraynor@redhat.com>
On Wed, Jan 20, 2021 at 3:45 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> content/download/_index.md | 2 +-
> content/roadmap/_index.md | 1 -
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/content/download/_index.md b/content/download/_index.md
> index 2965a4f76..b7284fcb5 100644
> --- a/content/download/_index.md
> +++ b/content/download/_index.md
> @@ -34,5 +34,5 @@ weight = "2"
> | [DPDK 19.05.0](//fast.dpdk.org/rel/dpdk-19.05.tar.xz) | [2019 May 13](//doc.dpdk.org/guides-19.05/rel_notes/release_19_05.html) | fe22ad1bab1539945119047b0fdf1105 |
> | [DPDK 19.02.0](//fast.dpdk.org/rel/dpdk-19.02.tar.xz) | [2019 February 1](//doc.dpdk.org/guides-19.02/rel_notes/release_19_02.html) | 23944a2cdee061aa4bd72ebe7d836db0 |
> -| [DPDK 18.11.10 (LTS)](//fast.dpdk.org/rel/dpdk-18.11.10.tar.xz) | [2020 September 28](//doc.dpdk.org/guides-18.11/rel_notes/release_18_11.html) | a97a33bda610feb891dc9e1e418a8fe6 |
> +| [DPDK 18.11.11 (LTS)](//fast.dpdk.org/rel/dpdk-18.11.11.tar.xz) | [2021 January 20](//doc.dpdk.org/guides-18.11/rel_notes/release_18_11.html) | 2d3c3c107ff93ce0d7dd149d3b633b28 |
> | [DPDK 18.08.1](//fast.dpdk.org/rel/dpdk-18.08.1.tar.xz) | [2019 April 1](//doc.dpdk.org/guides-18.08/rel_notes/release_18_08.html) | 391116ff3012ffd33bb63ed5feb3375c |
> | [DPDK 18.05.1](//fast.dpdk.org/rel/dpdk-18.05.1.tar.xz) | [2018 Sept 7](//doc.dpdk.org/guides-18.05/rel_notes/release_18_05.html) | 5e278012506c76d981e4283a92adec1c |
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index cbdf432e6..0d6dbfbb8 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -124,5 +124,4 @@ by 1-2 weeks, depending on the test results.
> | Current version | Next version | Next version Date | End of life | Maintainer |
> |----------|----------|-------------------|---------------------|--------------------|
> -| 18.11.10 | 18.11.11 | December 2020 | December 2020 (LTS) | Kevin Traynor |
> | 19.11.6 | 19.11.7 | March 2021 | November 2021 (LTS) | Luca Boccassi |
> | - | 20.11.1 | March 2021 | November 2022 (LTS) | Kevin Traynor |
> --
> 2.26.2
>
Acked-by: David Marchand <david.marchand@redhat.com>
Thanks Kevin!
--
David Marchand
prev parent reply other threads:[~2021-01-20 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 14:44 Kevin Traynor
2021-01-20 14:50 ` [dpdk-stable] [dpdk-web] " Richardson, Bruce
2021-01-20 14:57 ` Thomas Monjalon
2021-01-20 15:19 ` Kevin Traynor
2021-01-20 15:01 ` David Marchand [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=CAJFAV8zbFeLGwLs8AbKsr2Bn_gp52edEv948bQAicQsfQFWmqg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=web@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).