From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 5538A2C01; Fri, 9 Mar 2018 15:19:26 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A4B7620CCB; Fri, 9 Mar 2018 09:19:25 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 09 Mar 2018 09:19:25 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=roKR79oeHzMFJS68u9O0XaOLkF 4yaSm8qd9GRlWo1eA=; b=SezgPAEnzp3THY1RvDRlfu6K7ZseP5I3kxIV1TE6k3 DuGeadIxDB83KM9IyBXAB66jHy5DPbSHk7xn09SXHpQDTkWkxUwWwIfFlB0vtKIH llIFw1jWhjyGCGjnc+BTKxDRqSnPFWoaGW2DAMmqSwkxhlvIcGxkEBC4uxsRSJva 8= 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-sender:x-me-sender:x-sasl-enc; s=fm2; bh=roKR79 oeHzMFJS68u9O0XaOLkF4yaSm8qd9GRlWo1eA=; b=nZwripATc4m0J0HT8ujs+E OaanYg/xcsIFSswKUFdZgHckO1t2y9X8ik4qMBaWJ0qus1GG63TXGDgyI/9bY2Iq 6M2RQlYeT+w3SYGqhXx8Ba968zh2sgSmIjQMgxQVPackU+jTj2WfVMk8ewtc5LuR WdEa4RXxruVRiadSLJGhXQrMqOn2Xv3IcfdyE7EIRDji0u7i2B4qdd15AufATuBW 5QKW+7+wREVCbxtKwc5DY9k4HdJa6cJ3lGs5cHrSULgXEmu4TWioMiGxx9dJ/5Yb JP1b5e2WPi30oYO+9lIt37GnpDzLJAr1NeI917OHsm3aZaRow/sAClAMiHUXXBgw == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id C6621244E7; Fri, 9 Mar 2018 09:19:24 -0500 (EST) From: Thomas Monjalon To: "Ananyev, Konstantin" Cc: Luca Boccassi , "web@dpdk.org" , "yliu@fridaylinux.org" , "ktraynor@redhat.com" , "techboard@dpdk.org" Date: Fri, 09 Mar 2018 15:19:10 +0100 Message-ID: <138268661.yuZPGn2xFY@xps> In-Reply-To: <2601191342CEEE43887BDE71AB97725890F22385@irsmsx105.ger.corp.intel.com> References: <20180309133612.19927-1-thomas@monjalon.net> <5601805.V4YcVmhU8q@xps> <2601191342CEEE43887BDE71AB97725890F22385@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 14:19:26 -0000 09/03/2018 15:03, Ananyev, Konstantin: > From: Thomas Monjalon > > 09/03/2018 14:44, Luca Boccassi: > > > On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > > > > Signed-off-by: Thomas Monjalon > > > > > > > > --- > > > > This is at the same time, a call for volunteer, > > > > and a proposed change to shorten the wait for the first stable > > > > releases > > > > from at least 3 months to 2 months. > > > > > > > > Let's add this discussion to the agenda of the next techboard > > > > meeting. > > > > > > The issue is how to decide what goes into a stable release, if it does > > > not follow a main release. > > > > > > Right now we follow the main release as that means there is a list of > > > accepted and merged commits that can be backported - if the stable > > > release is anticipated, what is going to be backported? > > > > If we pull patches more regularly in master, there can be a lot of fixes > > accumulated during 2 months. > > But these patches need to be properly tested before going into LTS, right? > So it means extra effort for the validation teams? Exact The stable release must be validated anyway. The proposal is to validate the .1 release before starting RC1 validation, instead of doing it after the .0 release.