From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
 [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 8C60A5F21;
 Fri,  9 Mar 2018 14:49:44 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 15C17211C4;
 Fri,  9 Mar 2018 08:49:44 -0500 (EST)
Received: from frontend1 ([10.202.2.160])
 by compute1.internal (MEProxy); Fri, 09 Mar 2018 08:49:44 -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=+alhs5eCqbsRSlmp+6GQFf4o9d
 tvPTpexjN3q+Ycm6w=; b=g9aaVvbLNtX8GOB6d3M7eWNgkwihRtzpmART2n7Eoe
 tqVTys3DDi1AG8JD3k7gqbBuFFqiURVwq9Ta4+Vv7iDN3Sri3NZ92rFsp9+1wbyh
 ldhU19F4ZlHL8dogjWKlJwMI+4m/F6p9jjzbCxeGbHveqJOQOo5tvzabQ7Ry85ux
 k=
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=+alhs5
 eCqbsRSlmp+6GQFf4o9dtvPTpexjN3q+Ycm6w=; b=cSpiUbkbsJjGs7G91+60f6
 3JdSLbQSOfhqGi+GVefvLkTBQUFZSM4WLfi+LsDGTR0ZJ4nfWU+ej9K24HCMU4Ce
 D8hTgL45v89vHJ5JvLE82XTcrTMWHIvnSb0r5BQl74qRbXt2TADrYo53e5SH24Sh
 dC6P5Yo15eQUAiOP2t2Gbt86TemyufVYUdCpRFBpJ+FyijT0AN1aLspRNw/+RPQ2
 ud86x4PjB32cNgcnVWw+uNFxATUoIaa2cGha4Bkz2/LdgJUC1q9RdYVx0lBYmefj
 lkUE6HzzPbNE+aIEvHmgPXrkPgB12kK+QRd/PIUkhY049GGuvoK2b7xQ1Uy97tGA
 ==
X-ME-Sender: <xms:-JCiWpOrNq6-6Dv63_acqV9zcoRPfjAuV17PtOPCSu15p7lm2-hqvw>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id C347E7E622;
 Fri,  9 Mar 2018 08:49:41 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Boccassi <bluca@debian.org>
Cc: web@dpdk.org, yliu@fridaylinux.org, ktraynor@redhat.com, techboard@dpdk.org
Date: Fri, 09 Mar 2018 14:49:27 +0100
Message-ID: <5601805.V4YcVmhU8q@xps>
In-Reply-To: <1520603091.5685.8.camel@debian.org>
References: <20180309133612.19927-1-thomas@monjalon.net>
 <1520603091.5685.8.camel@debian.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-web] [PATCH] update stable releases roadmap
X-BeenThere: web@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK website maintenance <web.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/web>,
 <mailto:web-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/web/>
List-Post: <mailto:web@dpdk.org>
List-Help: <mailto:web-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/web>,
 <mailto:web-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2018 13:49:44 -0000

09/03/2018 14:44, Luca Boccassi:
> On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote:
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > 
> > ---
> > 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.