From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id C5C905F16; Thu, 22 Mar 2018 12:25:15 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B7E4120FFF; Thu, 22 Mar 2018 07:25:14 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 22 Mar 2018 07:25:14 -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=KZi4G3esP+RLUiWHZ9oSjR24rs oyrgzUThqHkLXaOcM=; b=BwNmPX0lndUAKt+gJkhMoEJjjCtPtqTSdsPSzgVtfm 07hqi5PKyrPjcXXWkTGPAaopRKjYr65Bj+jTGAbzJemJLvuAffUo/EUK/ooWN+ih au7dsWVoBzYRszsbaIQQXpeg1HMsq0lnjXBgAnKmuAQy/KzrD0GlfqKv4zVQAPoV U= 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=KZi4G3 esP+RLUiWHZ9oSjR24rsoyrgzUThqHkLXaOcM=; b=CzPEi2rWKpi9o9CNpBvMRG 0wG/8vYzXOmLKW8hMxVg7h621/djO+Msu8eQjO0gIB7uGuP63cvin52befa21IcY Lt+RiFmpCcjvPEhpsSbMS/iLndPQbOxoFBHXKUiCBpaWRBFHVnKhcPl/iIrgKRu3 9V3ogq5yIMZ83dJ4BvrUoEq8Zmqkqd4N7erqq3or5DcJ2XUjBysFtRw/5YF+F/kY GEPuYKKv9ONf7G+t6SOiHx7edA4YJKJsf0yEqmY1TcTM5oQfTuvlaAfueFD/b9ra V8SFhpRNjRDHQLH+BbaFyZTfl4uExPXgDd0eIpHq/riSyPL5u9lr/R8DkCMPLV9A == 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 BC7EB7E17B; Thu, 22 Mar 2018 07:25:13 -0400 (EDT) From: Thomas Monjalon To: Luca Boccassi Cc: web@dpdk.org, yliu@fridaylinux.org, ktraynor@redhat.com, techboard@dpdk.org, john.mcnamara@intel.com Date: Thu, 22 Mar 2018 12:25:12 +0100 Message-ID: <101469652.poQfFCCKWp@xps> In-Reply-To: <1521716595.14111.56.camel@debian.org> References: <20180309133612.19927-1-thomas@monjalon.net> <1521716595.14111.56.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 11:25:16 -0000 22/03/2018 12:03, Luca Boccassi: > Hi, > > I'm happy to help with 18.02.1. Thanks a lot. For next stable branches, we must find more volunteers. > Given it will be based on 18.05-rc2, which is due out on approximately > April 20th, I think we can be ambitious and target April 27th as the > tentative release date. I think 18.02.1 should be based on 18.05-rc1, so April 20th would be a tentative release date for 18.02.1 (before 18.05-rc2). I will send a v2 of this schedule. > Note that ATT won't be able to help with regression tests this time > around. John, may we count on help from Intel to run the usual batch of > regression tests between the 20th and the 27th? Or one week before :) It would be good to have more companies involved in testing stable releases. We need to explicitly ask to some of the members. Can be done privately.