From: Kevin Traynor <ktraynor@redhat.com>
To: web@dpdk.org
Cc: bluca@debian.org, thomas@monjalon.net, david.marchand@redhat.com,
ferruh.yigit@intel.com, Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-web] [PATCH] release 18.11.3
Date: Fri, 25 Oct 2019 13:39:53 +0100 [thread overview]
Message-ID: <20191025123953.19273-1-ktraynor@redhat.com> (raw)
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
content/download/_index.md | 6 +++---
content/roadmap/_index.md | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/download/_index.md b/content/download/_index.md
index 2220339..aa92ae2 100644
--- a/content/download/_index.md
+++ b/content/download/_index.md
@@ -11,8 +11,8 @@ weight = "2"
19.08
</a>
-<a class="dwnld-btn" href="https://fast.dpdk.org/rel/dpdk-18.11.2.tar.xz">
+<a class="dwnld-btn" href="https://fast.dpdk.org/rel/dpdk-18.11.3.tar.xz">
{{< icon name="glyphicon glyphicon-download-alt" size="large" >}}
Latest Stable\
- 18.11.2
+ 18.11.3
</a>
<a class="dwnld-btn" href="/roadmap">
@@ -29,5 +29,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.2 (LTS)](//fast.dpdk.org/rel/dpdk-18.11.2.tar.xz) | [2019 June 11](//doc.dpdk.org/guides-18.11/rel_notes/release_18_11.html) | 0ad396d18be01db57b6de8270ebdf651 |
+| [DPDK 18.11.3 (LTS)](//fast.dpdk.org/rel/dpdk-18.11.3.tar.xz) | [2019 October 25](//doc.dpdk.org/guides-18.11/rel_notes/release_18_11.html) | e42ca3c8773557720af8db21c7d374cc |
| [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 f27847c..a13d370 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -114,5 +114,5 @@ by 1-2 weeks, depending on the test results.
|----------|----------|-------------------|---------------------|--------------------|
| 17.11.7 | 17.11.8 | December 2019 | December 2019 (LTS) | Luca Boccassi |
-| 18.11.2 | 18.11.3 | September 2019 | November 2020 (LTS) | Kevin Traynor |
+| 18.11.3 | 18.11.4 | January 2020 | November 2020 (LTS) | Kevin Traynor |
| - | 19.05.1 | September 2019 | September 2019 | ? |
| - | 19.08.1 | December 2019 | December 2019 | ? |
--
2.21.0
next reply other threads:[~2019-10-25 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 12:39 Kevin Traynor [this message]
2019-10-25 12:51 ` David Marchand
2019-10-25 13:15 ` Thomas Monjalon
2019-10-25 16:13 ` Kevin Traynor
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=20191025123953.19273-1-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--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).