From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] version: 19.02-rc0 Date: Wed, 28 Nov 2018 13:45:19 +0100 Message-ID: <1566760.PIYmtsEk27@xps> References: <20181128104430.22669-1-thomas@monjalon.net> 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 Return-path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 6060B1B2AC for ; Wed, 28 Nov 2018 13:45:24 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 > > --- > > 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.