From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH] version: 19.02-rc0 Date: Wed, 28 Nov 2018 11:16:41 +0000 Message-ID: References: <20181128104430.22669-1-thomas@monjalon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: john.mcnamara@intel.com, marko.kovacevic@intel.com To: Thomas Monjalon , dev@dpdk.org Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 7180F1B440 for ; Wed, 28 Nov 2018 12:16:44 +0100 (CET) In-Reply-To: <20181128104430.22669-1-thomas@monjalon.net> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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? Reviewed-by: Ferruh Yigit