Re: [dpdk-dev] [PATCH] version: 19.02-rc0

[Thomas Monjalon <thomas@monjalon.net>]

28/11/2018 14:24, Ferruh Yigit:
> On 11/28/2018 12:45 PM, Thomas Monjalon wrote:
> > 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.
> 
> OK, I see the concern.
> 
> What about doing rc0 release notes in two patches:
> 1- Copy-paste from previous release notes, strip the context.

It is not only strip the context, I change version number
and add back the removed section.

> 2- Update the template as desired.
> 
> Overall I think this is good to have, if you think this is just extra overhead,
> forget about it.

I understand you want to track the changes done in the template.
I will send a v2 with changes split.