From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>, stable@dpdk.org, yskoh@mellanox.com
Subject: Re: [dpdk-stable] [PATCH 2/2] 5-make-release-commit: Update release notes
Date: Fri, 21 Jun 2019 18:16:31 +0100 [thread overview]
Message-ID: <c0329357b227562026e81d75c16f7e2be11c9617.camel@debian.org> (raw)
In-Reply-To: <20190621144015.8749-2-ktraynor@redhat.com>
On Fri, 2019-06-21 at 15:40 +0100, Kevin Traynor wrote:
> Add a seperate section in the release notes for each
> LTS/stable minor release. It will include the fixes/validation
> information along with newly added sections for known issues
> and skipped patches.
>
> Signed-off-by: Kevin Traynor <
> ktraynor@redhat.com
> >
> ---
> 5-make-release-commit | 22 +++++++++++++++++-----
> README | 2 ++
> 2 files changed, 19 insertions(+), 5 deletions(-)
>
> diff --git a/5-make-release-commit b/5-make-release-commit
> index 84e8a21..522b46b 100755
> --- a/5-make-release-commit
> +++ b/5-make-release-commit
> @@ -22,9 +22,7 @@ update_release_note()
> {
>
> - if [ $RTE_VER_MINOR -eq 1 ]; then
> - echo
> - echo "Fixes and Validation in $RTE_VER_MAJOR Stable
> Release"
> - echo "--------------------------------------------"
> - fi
> + echo
> + echo "$stable_release Release Notes"
> + echo "---------------------"
>
> echo
> @@ -42,4 +40,18 @@ update_release_note()
> echo "$(cat $stable_release/validation)"
>
> + echo
> + echo "$stable_release Known Issues"
> + echo "~~~~~~~~~~~~~~~~~~~~"
> + echo
> +
> + echo "$(cat $stable_release/known_issues)"
> +
> + echo
> + echo "Fixes skipped and status unresolved"
> + echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"
> + echo
> +
> + echo "$(cat $stable_release/failed_list)"
> +
> } >>
> $DPDK_DIR/doc/guides/rel_notes/release_${RTE_VER_MAJOR/./_}.rst
> }
> diff --git a/README b/README
> index ec9c899..5eaefd2 100644
> --- a/README
> +++ b/README
> @@ -142,4 +142,6 @@ does:
> - update the release note with the bug fixing commits
> - update the release note with the validation from the 'validation'
> file
> +- update the release note with known issues from the 'known_issues'
> file
> +- update the release note with skipped patches from the
> 'failed_list' file
> - commit above changes with a short commit log ("release
> $stable_release")
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-06-21 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 14:40 [dpdk-stable] [PATCH 1/2] compose-notice: update compose-notice text Kevin Traynor
2019-06-21 14:40 ` [dpdk-stable] [PATCH 2/2] 5-make-release-commit: Update release notes Kevin Traynor
2019-06-21 17:16 ` Luca Boccassi [this message]
2019-06-21 17:16 ` [dpdk-stable] [PATCH 1/2] compose-notice: update compose-notice text 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=c0329357b227562026e81d75c16f7e2be11c9617.camel@debian.org \
--to=bluca@debian.org \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--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).