[dpdk-stable] [PATCH 1/2] README: add updates to stable roadmap table

[dpdk-stable] [PATCH 1/2] README: add updates to stable roadmap table

[Kevin Traynor]

Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
 README | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README b/README
index 25f09d5..1616fe7 100644
--- a/README
+++ b/README
@@ -155,5 +155,9 @@ Modify the file content/download/_index.md
    git push output
  - add that new md5 to the file
-and finally suggest that change to the web team at web@dpdk.org
+
+Modify the file content/roadmap/_index.md
+ - update the stable releases table for the new versions and dates
+
+and finally suggest the dpdk-web changes to the web team at web@dpdk.org
 
 
-- 
2.20.1

[dpdk-stable] [PATCH 2/2] 5-make-release-commit: add validation info to release note

[Kevin Traynor]

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

Re: [dpdk-stable] [PATCH 2/2] 5-make-release-commit: add validation info to release note

[Luca Boccassi]

On Tue, 2019-04-02 at 13:50 +0100, Kevin Traynor wrote:
> Signed-off-by: Kevin Traynor <
> ktraynor@redhat.com
> >
> ---
>  5-make-release-commit | 15 +++++++++++----
>  README                | 12 ++++++++++--
>  2 files changed, 21 insertions(+), 6 deletions(-)

Acked-by: Luca Boccassi <bluca@debian.org>

-- 
Kind regards,
Luca Boccassi