From: David Marchand <david.marchand@redhat.com>
To: Luca Boccassi <bluca@debian.org>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [PATCH 1/2] release 19.11.2
Date: Mon, 18 May 2020 15:37:36 +0200 [thread overview]
Message-ID: <CAJFAV8zZ9p93HA_9kvSG=cnRoOzJ0L2jbTFhwM=yb5ALhYUeRg@mail.gmail.com> (raw)
In-Reply-To: <20200518132834.27531-1-bluca@debian.org>
On Mon, May 18, 2020 at 3:28 PM Luca Boccassi <bluca@debian.org> wrote:
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
> ---
> content/download/_index.md | 2 +-
> content/roadmap/_index.md | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/content/download/_index.md b/content/download/_index.md
> index 6f3c3c9..ceeb218 100644
> --- a/content/download/_index.md
> +++ b/content/download/_index.md
> @@ -26,7 +26,7 @@ weight = "2"
> | file | date/changelog | md5 |
> |---------------------------------------------------------------|------------------------------------------------------------------------------|----------------------------------|
> | [DPDK 20.02.0](//fast.dpdk.org/rel/dpdk-20.02.tar.xz) | [2020 February 25](//doc.dpdk.org/guides-20.02/rel_notes/release_20_02.html) | e20171462d6b2252dfbae1de8c45ba10 |
> -| [DPDK 19.11.1 (LTS)](//fast.dpdk.org/rel/dpdk-19.11.1.tar.xz) | [2020 March 17](//doc.dpdk.org/guides-19.11/rel_notes/release_19_11.html) | 43b691f830e47a84b20c716ccc7aff40 |
> +| [DPDK 19.11.1 (LTS)](//fast.dpdk.org/rel/dpdk-19.11.2.tar.xz) | [2020 May 18](//doc.dpdk.org/guides-19.11/rel_notes/release_19_11.html) | cd59c6577073b0a7bdf038f2658df1f2 |
19.11.2 (LTS)*
> | [DPDK 19.08.2](//fast.dpdk.org/rel/dpdk-19.08.2.tar.xz) | [2019 November 15](//doc.dpdk.org/guides-19.08/rel_notes/release_19_08.html) | 97e71f5fed2e5fa21aae16cae82f9e04 |
> | [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 |
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index 8950f5d..41830ef 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -114,4 +114,4 @@ by 1-2 weeks, depending on the test results.
> | Current version | Next version | Next version Date | End of life | Maintainer |
> |----------|----------|-------------------|---------------------|--------------------|
> | 18.11.7 | 18.11.8 | June 2020 | November 2020 (LTS) | Kevin Traynor |
> -| 19.11.1 | 19.11.2 | June 2020 | November 2021 (LTS) | Luca Boccassi |
> +| 19.11.2 | 19.11.3 | June 2020 | November 2021 (LTS) | Luca Boccassi |
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
prev parent reply other threads:[~2020-05-18 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 13:28 Luca Boccassi
2020-05-18 13:28 ` [dpdk-web] [PATCH 2/2] release 20.02.1 Luca Boccassi
2020-05-18 13:38 ` David Marchand
2020-05-18 13:38 ` Ferruh Yigit
2020-05-18 13:43 ` Kevin Traynor
2020-05-18 13:47 ` Luca Boccassi
2020-05-18 13:32 ` [dpdk-web] [PATCH 1/2] release 19.11.2 Ferruh Yigit
2020-05-18 13:37 ` Ferruh Yigit
2020-05-18 13:37 ` 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='CAJFAV8zZ9p93HA_9kvSG=cnRoOzJ0L2jbTFhwM=yb5ALhYUeRg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--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).