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 4A35A1B3FC for ; Wed, 28 Nov 2018 14:35:56 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 47F60102B; Wed, 28 Nov 2018 08:35:55 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 28 Nov 2018 08:35:55 -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=Uhn7WqEEd+cuuzdJyLdYGqOATqRrzZxRwuf8e595nM8=; b=XRwa4Vk5wHSS dSlxqwX8s/or2eRgZ3MKfNhbavkSh98pj1O7x4iEERMMejxD0i8kZQezgYIS69yK x5ij1mU3sxgGDB/kpiraJFDfDpQrJMFck7FtaggwBrM5zZHDUk1FKLWzqBwlLhyM r4R/iNisqo2fLux7Djcq4JHg9kCxhYA= 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=Uhn7WqEEd+cuuzdJyLdYGqOATqRrzZxRwuf8e595n M8=; b=eB7TPrRVon4zJgyAvX68lDRIQkzzs+VCC615KHzfW4eT0WuqJWXp2dpN0 GoGY3hGxBlFFFBP+3O3rFqWMF4dY0brvxubXB+ph1aFQoMKzEqxb+qhsIc39ll38 8A42DMxfahYKZf9iOquhdbOP8LV8p+7DL4Heaae4F2+1tnLkPcsKxsw8FAdTeB+f OLRGHb+BOSZNF0K6XQ5c628eTgZPcBPwvHO9xoM1TN03kZBLD+qCqNHfvh4rQnp+ ExC5PCTPr0jy+uvneyfv3uR5HAQo16K9XBXyLyDFG/MeQXKMRXVb5zTYS5uo6NqV AA7UYBZdYrWdsrftLnoVgDra4XK9g== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (238.17.136.77.rev.sfr.net [77.136.17.238]) by mail.messagingengine.com (Postfix) with ESMTPA id 355B2E405B; Wed, 28 Nov 2018 08:35:52 -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 14:35:48 +0100 Message-ID: <1748475.NzZbMNKASk@xps> In-Reply-To: <0d3e8541-8e17-8d0e-3a22-06695c346d1b@intel.com> References: <20181128104430.22669-1-thomas@monjalon.net> <1566760.PIYmtsEk27@xps> <0d3e8541-8e17-8d0e-3a22-06695c346d1b@intel.com> 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 13:35:56 -0000 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 > >>> --- > >>> 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.