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 A20787E24; Wed, 18 Apr 2018 15:28:47 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B380420FF8; Wed, 18 Apr 2018 09:28:46 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 18 Apr 2018 09:28:46 -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=E8x/ALaoRwpFpyErPpcimiW5b5 03OUDuQZ0JIou9liU=; b=cHCqqXafJaHJWGYIVwNspQUTCIOwzxqHTxYxRBBcde XEWeHegWqNg9XV01zI6ZGfoJeRL4TDkrf9nhmuMjUME8eiXQ0vrYNb9lL65NGqn1 ZSIZtTCoGhtPfKVILck0/JXGu7OWs7z+jV9k/VQfFOtftFp7LWPg4HiUexFC2JU2 4= 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=E8x/AL aoRwpFpyErPpcimiW5b503OUDuQZ0JIou9liU=; b=BatMvWNMJk8DEUwPi680Qb h3efI3Y5G47OmbFDSrhWW2y04rgqIgo5q0KzelCbv89mYE3BfH87uU4a6Eqj0M3x uri9UpOduBVVC6TdqAg7lfs88CoS+Si/QA1DoCC6penptDtZLT70HKgB7FFupkJl jZvuy3me/5WB+Yc2LSH6JoKfLbQojWXCijZYRhUoGa9Ex7sBgyTxzLqGS1VDIwhl 2c3pYkJSqKpSDQnzJnVti84NqzbyINJhhSASsFyX5KvHMl3EfpbarDMDJ/0UNqt7 jRwinu7sZvTj1W1Qs5LxhHHhSBL6rxJxGq7ohrYDh52dPlBXSDPPh+3uCUjZQBKg == 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 76623E5088; Wed, 18 Apr 2018 09:28:45 -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 15:28:44 +0200 Message-ID: <2289123.B0I2yLRMB9@xps> In-Reply-To: References: <20180309133612.19927-1-thomas@monjalon.net> <2746771.jHPYkc9GPR@xps> 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 13:28:47 -0000 18/04/2018 14:28, Ferruh Yigit: > On 4/18/2018 10:14 AM, Thomas Monjalon wrote: > > 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? > > This has been discussed in tech-board, what I remember the decision was to wait > the release to backport patches into stable tree. It was not so clear to me. I thought post-rc1 was acceptable. The idea is to speed-up stable releases pace, especially first release of a series.