From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: delay for 17.02-rc1 Date: Mon, 16 Jan 2017 17:02:53 +0100 Message-ID: <4833533.9kVdhXKYOk@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit To: dev@dpdk.org Return-path: Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) by dpdk.org (Postfix) with ESMTP id C4A81DE5 for ; Mon, 16 Jan 2017 17:02:55 +0100 (CET) Received: by mail-lf0-f52.google.com with SMTP id v186so86969348lfa.1 for ; Mon, 16 Jan 2017 08:02:55 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id s70sm7573031lfi.0.2017.01.16.08.02.54 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Jan 2017 08:02:54 -0800 (PST) List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi all, As you know, the integration deadline was on January 5th: http://dpdk.org/dev/roadmap#dates Unfortunately, a lot of patches are not ready yet. There are some delays in every areas, so neither the next-* trees, nor the mainline, are ready. We cannot have too much delay because: 1/ we must be on time for next releases 2/ there will be holidays in China very soon Which solutions do we have? 1/ close 17.02 features now and frustrate everyone 2/ postpone some patches to RC2 if they do not disturb validation too much 3/ hurry up Comments are welcome