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 0E7D244C3 for ; Tue, 12 Mar 2019 21:51:41 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AB1892211F; Tue, 12 Mar 2019 16:51:40 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 12 Mar 2019 16:51:40 -0400 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=U0tAYP3DxzzBsXF972ucmDikTdS+S55/6xgk8CAu+Bg=; b=KKn0SthzjRDs vjnUkd+j6oiCVl7Zi1FIyeoYTjILdygDtQjl9nTLXyPNhmw0TiSPrY619rftFGfK 2HuTjRZYuQk102I0Si+j0C1EL3UkSCUhxTqxUEIKy6p1ziJpfa515EA1ZVge29Ux +RidzsRMODOKXsbX1LsmhdAAi86Xguo= 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=fm2; bh=U0tAYP3DxzzBsXF972ucmDikTdS+S55/6xgk8CAu+ Bg=; b=AqtM17jg2Rcpc7BCzxOa9V8ZFxWl51dx9Ymiwjoj9r69RIAmyahpwemyW eFmmDA7YMW/hQrdASU39cQVLVWRnUG3WEbWKmNvUbM6MQC0Y4eh60ixaGW8pn4xp hFGW/WHbfexPFvtwdySdw28MrOIPEDJN0Gi4GB/opXeic8IfAkEWG89/smbgM3+y U1ZToQQzm95crZu2mOkRDgdmuh7YdrSCTFBN4fAYQwl8giWcdSYA7/mY+89RDtyw /pqHj6p8XBsd/KxczDalYozfdke0p/ly07IiBZmEUfoNUs1NsQ9q5riq7aUOhN0J F1xUSiy4s2tfB1BWlYl41o4FEiSaw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrgeekgddugeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedu X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 75A1EE4752; Tue, 12 Mar 2019 16:51:38 -0400 (EDT) From: Thomas Monjalon To: Luca Boccassi , Kevin Traynor Cc: "dev@dpdk.org" , Yongseok Koh , Ferruh Yigit , John McNamara , Aaron Conole , "Walker, Benjamin" , Jay Rolette Date: Tue, 12 Mar 2019 21:51:37 +0100 Message-ID: <4664304.LLR2pzfpgk@xps> In-Reply-To: <834f085314caae4091cfc02c5c904a6efaed3141.camel@debian.org> References: <0989b56a-f480-416c-e0a7-3e562c9b990b@redhat.com> <834f085314caae4091cfc02c5c904a6efaed3141.camel@debian.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] DPDK short term stable maintenance 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: Tue, 12 Mar 2019 20:51:41 -0000 12/03/2019 21:46, Luca Boccassi: > On Tue, 2019-03-12 at 19:12 +0000, Kevin Traynor wrote: > > So what to do with short term stables? Some choices could be: > > > > - continue with short term stables for n.02/05/08 > > - ad-hoc support for short term stables where community have an > > interest > > in a particular one > > - have a maintainer to backport fixes on a public branch, but have no > > releases, or have unvalidated/best effort validated releases > > - no short term stable branches/releases > > > > Probably there's other ideas too. Obviously most of the above would > > need > > resources from the community to proceed. One advantage of not having > > short term stables is that there might be more resources available > > for > > maintenance/validation of master and LTS DPDK releases. [...] > > My 2c is that, unless someone steps up not only for the maintainer role > but also for the validation effort, we should cancel the short term > releases. Yes it looks reasonnable. So we must question the community at each major release to know if it will maintained, how long, or not. If there are volunteers, we must clearly state in the stable release notes which areas are validated.