From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: proposal deadline Date: Tue, 6 Dec 2016 13:25:44 -0800 Message-ID: <20161206132544.720c8627@xeon-e3> References: <2826842.JE1PHBM7JX@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail-pg0-f49.google.com (mail-pg0-f49.google.com [74.125.83.49]) by dpdk.org (Postfix) with ESMTP id 7E862475E for ; Tue, 6 Dec 2016 22:25:54 +0100 (CET) Received: by mail-pg0-f49.google.com with SMTP id 3so153379906pgd.0 for ; Tue, 06 Dec 2016 13:25:54 -0800 (PST) In-Reply-To: <2826842.JE1PHBM7JX@xps13> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Sun, 04 Dec 2016 23:44:51 +0100 Thomas Monjalon wrote: > Hi all, > > There were a lot of patches v1 submitted these last days, just before the > proposal deadline (December 4). > It's good to have a lot of features for 17.02, but it means we are going > to have a hard time to review, rework and integrate them. > I think we should make an effort to send our v1 patches (or RFC) much before > the deadline. > Or we can make the proposal window shorter, but it would be less flexible. > Another way to manage this huge flow: start reviewing the oldest ones. > And if there is not enough time for proper review of the latest series, > some will be postponed. > > The statistics diagram of patches proposals (v1) per week are attached. > You can also find it at this URL: > https://s12.postimg.org/g9uluz9u5/patchesv1.png > In case the diagram of v1 patches needs some comments, these were the > deadlines for feature proposal: > 2015 October 2 > 2016 January 31 > 2016 May 9 > 2016 August 28 > 2016 December 4 I would separate new features/infrastructure from new drivers. In Linux, Linus still takes new driver after the merge window, but not new features.