From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org, bluca@debian.org, yskoh@mellanox.com
Cc: thomas@monjalon.net, ferruh.yigit@intel.com,
Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-stable] [PATCH v2] lib: update LTS releases
Date: Tue, 9 Apr 2019 16:30:09 +0100 [thread overview]
Message-ID: <20190409153009.29324-1-ktraynor@redhat.com> (raw)
In-Reply-To: <20190409152306.28880-1-ktraynor@redhat.com>
This updates so "LTS" vs. "stable" will be used where appropriate.
Also update 6-announce-release to use it in the body.
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
v2: removed local changes from lib.sh
(that's what I get for testing the patch)
6-announce-release | 2 +-
lib.sh | 5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/6-announce-release b/6-announce-release
index 619065c..0a7a4fc 100755
--- a/6-announce-release
+++ b/6-announce-release
@@ -29,5 +29,5 @@ Subject: DPDK $(describe_release) released
Hi all,
-Here is a new stable release:
+Here is a new $(stable_or_lts) release:
https://fast.dpdk.org/rel/dpdk-${stable_release}.tar.xz
diff --git a/lib.sh b/lib.sh
index cf02d92..42d0669 100644
--- a/lib.sh
+++ b/lib.sh
@@ -45,5 +45,6 @@ get_last_release()
describe_release()
{
- if [ "${stable_release%.*}" == "16.11" ]; then
+ if [ "${stable_release%.*}" == "17.11" ] ||
+ [ "${stable_release%.*}" == "18.11" ] ; then
echo "$stable_release (LTS)"
else
@@ -55,5 +56,5 @@ stable_or_lts()
{
# TODO: let it be data-file driven
- if [ "${stable_release%.*}" == "16.11" ] ||
+ if [ "${stable_release%.*}" == "18.11" ] ||
[ "${stable_release%.*}" == "17.11" ] ; then
echo "LTS"
--
2.20.1
next prev parent reply other threads:[~2019-04-09 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 15:23 [dpdk-stable] [PATCH] " Kevin Traynor
2019-04-09 15:30 ` Kevin Traynor [this message]
2019-04-09 16:09 ` [dpdk-stable] [PATCH v2] " Luca Boccassi
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=20190409153009.29324-1-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--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).