patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: bluca@debian.org, ktraynor@redhat.com
Cc: stable@dpdk.org
Subject: [dpdk-stable] [PATCH] Add accumulated list of missing patches to release announce
Date: Fri, 18 Jan 2019 16:31:38 -0800	[thread overview]
Message-ID: <20190119003138.38007-1-yskoh@mellanox.com> (raw)

Stable maintainers sholud keep an accumulated list of missing patches. And
this will be notified in the release announce.

Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
---
 6-announce-release | 21 +++++++++++++++++++++
 README             | 13 ++++++++-----
 2 files changed, 29 insertions(+), 5 deletions(-)

diff --git a/6-announce-release b/6-announce-release
index 4cd5b05..619065c 100755
--- a/6-announce-release
+++ b/6-announce-release
@@ -2,6 +2,14 @@
 
 source ./lib.sh
 
+if [ $# -lt 1 ] || [ ! -f "$1" ]
+then
+	echo "Usage: $0 failed_list"
+	exit 1
+fi
+failed_list="/tmp/.list-$$"
+grep -v "^#" $1 > $failed_list
+
 get_diffs()
 {
 	$GIT diff v${last_release}..v${stable_release} --stat
@@ -35,3 +43,16 @@ EOF
 }
 
 compose_release_note
+
+cat << EOF
+---[ List of missing patches ]---
+The following is the accumulated list of skipped patches. Authors/maintainers
+have not yet responded to backport requests. Actions to take per each patch,
+
+	a) say "it is not relevant to ${RTE_VER_MAJOR}"
+	b) send out a backport to stable@dpdk.org
+
+EOF
+while read commit patch; do
+	describe_commit $commit
+done < $failed_list | sort -k 2
diff --git a/README b/README
index fc1bc5d..25f09d5 100644
--- a/README
+++ b/README
@@ -88,10 +88,12 @@ base could have been changed that it needs a manual backport.
 
 The usage is:
 
-    $ 3-request-backport failed-list
-
-Where, the failed-list is generated from "1-import".
+    $ 3-request-backport accumulated-failed-list
 
+A failed-list for a release is generated from "1-import" but maintainer
+should keep an accumulated list for the stable tree and send out this
+request multiple times with the accumulated list of failed patches. This
+list will also be used by "6-announce-release".
 
 4-final-review
 ==============
@@ -158,8 +160,9 @@ and finally suggest that change to the web team at web@dpdk.org
 6-announce-release
 
 The last step is to announce it. The usage is also simpler: just type the
-command without any options. Again, it will generate a email, and you have
-to edit it (since it's way too short and simple so far :).
+command with the accumulated failed list mentioned in "3-request-backport".
+Again, it will generate an email, and you have to edit it (since it's way
+too short and simple so far :).
 
 
 That's all.
-- 
2.11.0

             reply	other threads:[~2019-01-19  0:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19  0:31 Yongseok Koh [this message]
2019-01-21 11:00 ` 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=20190119003138.38007-1-yskoh@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=bluca@debian.org \
    --cc=ktraynor@redhat.com \
    --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).