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 610612965 for ; Mon, 23 Apr 2018 04:00:00 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A2FEC21174; Sun, 22 Apr 2018 21:59:59 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 22 Apr 2018 21:59:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= 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=Yxral+MofGrX6rP12xE31C5JTR HNJ+7ytLT+mk0jlQY=; b=WuD4UpR/W9ONmZo2MqxwTmP5vYvWjlAcD8a9gVU0TY xLRDIzyASrA0Nh9wdmyMakhh4qbkMz9PGyLN6z9QGr+mlaQJA3hW9kYp1LCuJBkw jRfYutVofK4q1G8AR87+WK5sjhhRYdPsEuI+s4IgY6eVMxq8Y8OH563/NE5Ne7YH o= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=Yxral+ MofGrX6rP12xE31C5JTRHNJ+7ytLT+mk0jlQY=; b=iarVERYT4WRfpM74CKePxf kSNBx0mAZhsJZb7tfy1dbG6JlDm7wVyFFut9LwUYvlfZz+xwfOuce+PdZD2FQQoJ bsmLVjCE3xpogDnPMk4FtKewFJDfyqMUQzArs4rXZ+ntsgimsdXd4Z33ZjQSyAWd X6ETafTgFCB+C8A7Afr9hE8WlaJArYgcwG99GE59E5SJG+aTiASStI/Rh+rjhBE3 dL1pG3ouWFGbWRVj3yeUWA7EytLwX4qHNgqzGDOQ95mBD7l6G4y2FgB7BSWjPJVZ /l/8CX2gRwY2SQp0SF8avq+5KDJ8IsrT7FlHW2ePt3zZ5OgegGdX8ilULqchAt9Q == 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 342B9E47A0 for ; Sun, 22 Apr 2018 21:59:59 -0400 (EDT) From: Thomas Monjalon To: announce@dpdk.org Date: Mon, 23 Apr 2018 03:59:57 +0200 Message-ID: <4331565.BVefF9EF6h@xps> In-Reply-To: <16743280.PYHFFin0V3@xps> References: <16743280.PYHFFin0V3@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-announce] release 18.05 delayed X-BeenThere: announce@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2018 02:00:00 -0000 Hi, Please find an update of the release status, inline below. 13/04/2018 00:01, Thomas Monjalon: > The integration deadline is passed by one week, and the first > release candidate is still far from being ready. > This time it is really, really late. > We will try to do this RC1 on the 20th of April, but no guarantee. .. no guarantee, indeed. There are 742 patches in master, 56 in next-net, 68 in next-crypto, and a lot more not yet merged. List of remaining significant patches for RC1: missing in next-net - runtime queue setup - new VXLAN and MPLS tunnels - generic IP/UDP tunnel offloads - tunnel encap/decap - flow API related fixes - flow API overhaul for switch offloads - rte_flow extension for vSwitch - switching devices representation missing in master: - secondary vdev - replace calls to rte_panic - control threads - symbolic log levels - devargs cleanup - device querying - mbuf external - mempool bucket driver > Then we may have a lot of new drivers or features to integrate > in the next release candidate. So we need to plan two weeks of work > before releasing the RC2 around the 4th of May, which was the date > initially targeted for the release 18.05. List of major patches for RC2: - compressdev - DPAA2 QDMA raw driver - DPAA2 Command Interface raw driver - Hyper-V bus and NetVSC PMD - Intel FPGA - BPF > Usually we need two more weeks of bug fixing in RC3 and RC4, > and few more days of validation before the release. > It means the release will happen on the 23rd of May in the "best case". > > During this time, we need everybody's help to finish the reviews.