From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] version: 19.02-rc0
Date: Wed, 28 Nov 2018 14:35:48 +0100
Message-ID: <1748475.NzZbMNKASk@xps>
References: <20181128104430.22669-1-thomas@monjalon.net>
 <1566760.PIYmtsEk27@xps> <0d3e8541-8e17-8d0e-3a22-06695c346d1b@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com
To: Ferruh Yigit <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com
 [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 4A35A1B3FC
 for <dev@dpdk.org>; Wed, 28 Nov 2018 14:35:56 +0100 (CET)
In-Reply-To: <0d3e8541-8e17-8d0e-3a22-06695c346d1b@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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.