From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 48A8A7EE0; Wed, 18 Apr 2018 11:14:29 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C425F2109D; Wed, 18 Apr 2018 05:14:28 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 18 Apr 2018 05:14:28 -0400 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=7Xm40DU0HMO5n5K3bp665MVy8/ KNdI2+l1HlnufWIUA=; b=HW+TLS96QXUhRv5CcQi4rXw5AhDoPYmtGjjjpshNUE Rnbxqio+d379x4worri5dAsGtrwfsErdrzvPQthjGV1MLf02aAIdKX2MePK6Dxss eOahvo4NGvbTF1jI96ML8LYdrOHiYrx65TqSXbQMmbQkwipbaBc50HYB+OXW2EDI w= 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=7Xm40D U0HMO5n5K3bp665MVy8/KNdI2+l1HlnufWIUA=; b=btF63DgRoi0nsIR/iolfZm YdQdqsJrqhcwKPnuGVSikEtXL3J6IY2DCCqhfwfFLh0BWdvf2M19RYXHcDhHfK7w 4+hbqYwOXd5z6619DzUmoEKYXN/z+TSj/T7q9K5kCqD0qYVDuYiRh9EHD8515thr cDpsM5Et3KCHX88iDQVc63CX03S3VkFG2RkyzT+dOVgn2VgzXstvuk2lsi7jrj+H i8aKYJeIejcsnup3Uj7dwYESwkwq6HXLWXpONMmq238iyMfUIsayAcB5xGfbxWjC ogmY1JVKPdY+qJLKstUbeJHz8jqQOsOGs8ElFSMpvywrA/G4jDvJOov5XMscRdsg == 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 6985BE4120; Wed, 18 Apr 2018 05:14:27 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: web@dpdk.org, dev@dpdk.org, techboard@dpdk.org, bluca@debian.org, yliu@fridaylinux.org, ktraynor@redhat.com, christian.ehrhardt@canonical.com, yskoh@mellanox.com Date: Wed, 18 Apr 2018 11:14:26 +0200 Message-ID: <2746771.jHPYkc9GPR@xps> In-Reply-To: <776b230f-215a-8fec-1f2f-0b19064ba004@intel.com> References: <20180309133612.19927-1-thomas@monjalon.net> <20180410232813.2534-1-thomas@monjalon.net> <776b230f-215a-8fec-1f2f-0b19064ba004@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-web] [PATCH v2] update stable releases roadmap 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, 18 Apr 2018 09:14:29 -0000 18/04/2018 11:05, Ferruh Yigit: > On 4/11/2018 12:28 AM, Thomas Monjalon wrote: > > -

Typically a new stable release version follows a mainline release > > - by 1-2 weeks, depending on the test results. > > +

The first stable release (.1) of a branch should follow > > + its mainline release (.0) by at least two months, > > + after the first release candidate (-rc1) of the next branch. > > Hi Thomas, > > What this change suggest? To be able to backport patches from rc1? Yes, it is the proposal we discussed earlier. We can wait one week after RC1 to get some validation confirmation. Do you agree?