From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org, bluca@debian.org, yskoh@mellanox.com
Cc: thomas@monjalon.net, Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-stable] [PATCH 2/2] 5-make-release-commit: add validation info to release note
Date: Tue, 2 Apr 2019 13:50:20 +0100 [thread overview]
Message-ID: <20190402125020.30383-2-ktraynor@redhat.com> (raw)
In-Reply-To: <20190402125020.30383-1-ktraynor@redhat.com>
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
5-make-release-commit | 15 +++++++++++----
README | 12 ++++++++++--
2 files changed, 21 insertions(+), 6 deletions(-)
diff --git a/5-make-release-commit b/5-make-release-commit
index 17aa535..84e8a21 100755
--- a/5-make-release-commit
+++ b/5-make-release-commit
@@ -24,15 +24,22 @@ update_release_note()
if [ $RTE_VER_MINOR -eq 1 ]; then
echo
- echo "Fixes in $RTE_VER_MAJOR Stable Release"
- echo "-----------------------------"
+ echo "Fixes and Validation in $RTE_VER_MAJOR Stable Release"
+ echo "--------------------------------------------"
fi
echo
- echo "$stable_release"
- echo "~~~~~~~"
+ echo "$stable_release Fixes"
+ echo "~~~~~~~~~~~~~"
echo
$GIT log --oneline v${last_release}..HEAD | cut -d ' ' -f 2- | sort | sed 's/^/* /'
+ echo
+ echo "$stable_release Validation"
+ echo "~~~~~~~~~~~~~~~~~~"
+ echo
+
+ echo "$(cat $stable_release/validation)"
+
} >> $DPDK_DIR/doc/guides/rel_notes/release_${RTE_VER_MAJOR/./_}.rst
}
diff --git a/README b/README
index 1616fe7..bef3762 100644
--- a/README
+++ b/README
@@ -117,14 +117,22 @@ email with the notification content. What you need to so it to edit it
when necessary (say, leaving more time for review) and send it out.
+At this point the vendors who have commited to test the release should do
+so and send a report back on what they have tested.
5-make-release-commit
=====================
+In order that there will be information about validation of each stable
+release in the release notes, add a file called 'validation' in the local
+stable release directory created in 0-set-stable-release. In that file
+write some notes about the validation that has been performed by the
+various vendors.
+
When all are ready, it's time to make the release commit, which basically
does:
- change the release version (say from v17.08 to v17.08.1)
-- update the release note (with the bug fixing commits listed in the release
- note)
+- update the release note with the bug fixing commits
+- update the release note with the validation from the 'validation' file
- commit above changes with a short commit log ("release $stable_release")
--
2.20.1
next prev parent reply other threads:[~2019-04-02 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 12:50 [dpdk-stable] [PATCH 1/2] README: add updates to stable roadmap table Kevin Traynor
2019-04-02 12:50 ` Kevin Traynor [this message]
2019-04-02 13:16 ` [dpdk-stable] [PATCH 2/2] 5-make-release-commit: add validation info to release note 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=20190402125020.30383-2-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--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).