From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com
Subject: Re: [dpdk-dev] [PATCH] version: 19.02-rc0
Date: Wed, 28 Nov 2018 13:45:19 +0100 [thread overview]
Message-ID: <1566760.PIYmtsEk27@xps> (raw)
In-Reply-To: <be17bb6f-d190-71ad-4984-9f5d15ba14ca@intel.com>
28/11/2018 12:16, Ferruh Yigit:
> On 11/28/2018 10:44 AM, Thomas Monjalon wrote:
> > Start version numbering for a new release cycle,
> > and introduce a template file for release notes.
> >
> > The release notes comments are updated to mandate
> > a scope label for API and ABI changes.
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
> > doc/guides/rel_notes/index.rst | 1 +
> > doc/guides/rel_notes/release_19_02.rst | 209 ++++++++++++++++++++
>
> What do you think about storing the release notes template in git repo, this
> helps creating new ones for next release also makes easier to track/view what
> has been changed in the release notes template?
If something is changed in the release notes, it should be updated
in the template, with a risk of forgetting.
And the list of libraries would need to be updated too.
I feel it would be more complications.
next prev parent reply other threads:[~2018-11-28 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 10:44 Thomas Monjalon
2018-11-28 11:16 ` Ferruh Yigit
2018-11-28 12:45 ` Thomas Monjalon [this message]
2018-11-28 13:24 ` Ferruh Yigit
2018-11-28 13:35 ` Thomas Monjalon
2018-11-28 13:20 ` Mcnamara, John
2018-11-28 14:52 ` [dpdk-dev] [PATCH v2 1/2] " Thomas Monjalon
2018-11-28 14:52 ` [dpdk-dev] [PATCH v2 2/2] doc: improve release notes template Thomas Monjalon
2018-11-30 17:01 ` [dpdk-dev] [PATCH v2 1/2] version: 19.02-rc0 Ferruh Yigit
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=1566760.PIYmtsEk27@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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).