From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: proposal deadline Date: Tue, 06 Dec 2016 13:45:01 -0800 (PST) Message-ID: <1919219.0mG3jzDeNO@xps13> References: <2826842.JE1PHBM7JX@xps13> <20161206132544.720c8627@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Stephen Hemminger Return-path: Received: from mail-wj0-f171.google.com (mail-wj0-f171.google.com [209.85.210.171]) by dpdk.org (Postfix) with ESMTP id 4367E4A65 for ; Tue, 6 Dec 2016 22:45:02 +0100 (CET) Received: by mail-wj0-f171.google.com with SMTP id v7so338692180wjy.2 for ; Tue, 06 Dec 2016 13:45:02 -0800 (PST) In-Reply-To: <20161206132544.720c8627@xeon-e3> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-12-06 13:25, Stephen Hemminger: > 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. You're right. We are more tolerant with drivers patches after RC1. But significant/risky patches are not taken in last week(s).