From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 02355F6D; Wed, 28 Nov 2018 07:45:22 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 28 Nov 2018 07:45:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=WNweU02VoRNkqsZmRqB6AYqFxgK3laEMDmn57j8T+c0=; b=fXCcOVjhQUMI rdqtwBwm9y/rmeWXEsOchRQmLx4DnBN0cf83siscA81j2hAsoGwlPgVCiotavHzg Q18PPioVqdzC1LUb1t3mVg5X7WbYl+XlAbrtEKDT2VLH37hKxb7LEbbZHLSCqA3H 7wyXp6We7VysAJuOE0ZaAfKfZO7BrOw= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=WNweU02VoRNkqsZmRqB6AYqFxgK3laEMDmn57j8T+ c0=; b=DZEIlsaOEEHpFpJ8Xae64owiNYaP9ZcnPssO58YtfegqUh3J2TyKUSKSD 7eMjFVbsLWhelHpaWFNSOUDlnpB1msxbUhN2uNkIer+dY8mcPFKr9qFqlB0D4IW5 UEKPVSSSopAkIADHAzzRmFEUd24uKHuZwH7KLZbm+3RsAuaIRfr9ZhdDL3ClgjWm z9KsMISOR6Y9Z1/j6DEfRwyWJqGzbeh+ClNWWGKTlUNpXLKTzpOddtAf66+8+9Dv 7nZf+tTmHxeGQGAoU3BykiNHOqqmhtSP+YS56ZW8HoGrl9YcE2s9NLphXlFtIi/r daPeErtPP57IJMhdjk73Oujf6c0OQ== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 487CAE49DF; Wed, 28 Nov 2018 07:45:21 -0500 (EST) From: Thomas Monjalon To: Ferruh Yigit Cc: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com Date: Wed, 28 Nov 2018 13:45:19 +0100 Message-ID: <1566760.PIYmtsEk27@xps> In-Reply-To: References: <20181128104430.22669-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] version: 19.02-rc0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2018 12:45:24 -0000 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.