From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org, bluca@debian.org
Cc: Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-stable] [PATCH 1/2] 4-final-review: Update email message
Date: Fri, 18 Oct 2019 11:25:11 +0100 [thread overview]
Message-ID: <20191018102512.32548-1-ktraynor@redhat.com> (raw)
Update to ask that validation reports to be sent
to all involved in validating LTS releases and
mention they will be added to the release notes.
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
4-final-review | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/4-final-review b/4-final-review
index 5041564..d44b824 100755
--- a/4-final-review
+++ b/4-final-review
@@ -69,11 +69,11 @@ get_cc_val_list
Hi all,
-Here is a list of patches targeted for $(stable_or_lts) release $stable_release. Please
-help review and test. The planned date for the final release is __,
-__ Before that, please shout if anyone has objections with these
-patches being applied.
+Here is a list of patches targeted for $(stable_or_lts) release $stable_release.
-Also for the companies committed to running regression tests,
-please run the tests and report any issue before the release date.
+The planned date for the final release is DAY MONTH.
+
+Please help with testing and validation of your use cases and report
+any issues/results with reply-all to this mail. For the final release
+the fixes and reported validations will be added to the release notes.
A release candidate tarball can be found at:
--
2.21.0
next reply other threads:[~2019-10-18 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 10:25 Kevin Traynor [this message]
2019-10-18 10:25 ` [dpdk-stable] [PATCH 2/2] 5-make-release-commit: Add version to skipped fixes header Kevin Traynor
2019-10-18 15:12 ` Luca Boccassi
2019-10-18 15:11 ` [dpdk-stable] [PATCH 1/2] 4-final-review: Update email message 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=20191018102512.32548-1-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=stable@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).