From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id AE3121C0EB; Fri, 13 Apr 2018 00:01:23 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 04A7B1C0E6 for ; Fri, 13 Apr 2018 00:01:21 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6023E21A78; Thu, 12 Apr 2018 18:01:19 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 12 Apr 2018 18:01:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=ufGOUt3m4gJj4u4fMdIWBRS0kUdpdk8Ai92oodFJLSE=; b=cMqta QHnqdaFsaWBqbWq7tSwxNXaE1z0EHgzQhyZL+kt0MyANmnX+8UtQiEWJp0AoYc/C PjCBgiun8JKh7vgsxCaquL3XzLPoZ6e7ww29sFTZBL+FQSpks4f4RGAbxetGMVTb FUlHETNxnv9g5/CohfOucp5HZtx2JNphNazP8g= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=ufGOUt3m4gJj4u4fMdIWBRS0kUdpd k8Ai92oodFJLSE=; b=UsuJJd7skkZ91j0rwwVvc0PnJU5L4jikEvII8/NjELl6U SW7atWSrMe9XcRWMcTNWxow9DHEnFD/Dr5a5MXd7ZTUtaqsKpzltD7qosvYSdu3s qG7OGnyVGiaG6WgM/PhO/zGhZFAmUlwHVxDR1OfBgOfLcoJ6SYEppNb8rD+lppqP 6nhOPxNPp0G+SWXRtxP9BCFr5n/Uvoig1Qy/C4GwFeolMj+l9hkyqdxqLQOvMS1d uxcgeLumOx4MIYDk59yp3m4gc9Fvj6pJQBdCmR831BAWWq5SDgideDC4S+aTmhtU /VTWyy58grWXD3+wMhwcFbCkHV21RofAbtk24htKQ== 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 D4524E43EC for ; Thu, 12 Apr 2018 18:01:18 -0400 (EDT) From: Thomas Monjalon To: announce@dpdk.org Date: Fri, 13 Apr 2018 00:01:17 +0200 Message-ID: <16743280.PYHFFin0V3@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: announce@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Errors-To: announce-bounces@dpdk.org Sender: "announce" Subject: [dpdk-dev] [dpdk-announce] release 18.05 delayed X-BeenThere: dev@dpdk.org List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 22:01:23 -0000 Hi, 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. 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. 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. If you are not involved in reviews or last minute adjustments, you can start working on new stuff for 18.08, because the preparation period before the proposal deadline will be tight. We can think about delaying the proposal deadline for 18.08 by one week (June, 8th). We should also accept that the 18.08 release might be smaller than usual. Thanks for understanding and helps