From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=k/6rMf8YLZwmdBC4wisAvkC3p3lae+9b5SIu2is9ZFw=; b=B7TTKJbMfSJEw/AxmvDuzcaB995dUveKdiYiR+gthtJg5ndaZC5nSgqSBDQiCL3Io0 xe7wJP1tQrlrgBvr7+a5zzmEsNSjxyj+X4Q/o6skHF7PHvrs9KPGajxt+jsaCVnxQQZ+ tzAu042MSBTjli9X694dtOYLEskWQFZpU1x67A1NNpNe41huZIBfgEiYF/eNJrum1Su/ scv8dd92stpzeUPVo37r0TShijLLTMLjREH50tqCxvS+BQabNZSodj+/3eDCeQiErXNB 8R8PfvOb0MdwWwomBU4y4pNG9ZV2yLpFyeo1ATRjMa7B9kaXnUvuum/GBO5FJct474lH 0Aug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=k/6rMf8YLZwmdBC4wisAvkC3p3lae+9b5SIu2is9ZFw=; b=LtN8M1pUPvliAJATlJyt+WczR/di9FtUuPH7d0izHnEFeINYPeVDixWS7HwppZBajx EDWKSQAu+W5ms3CH0cNTEcqyMseV8B7Bhr2cShn+CjH8j0Lr+1+gGdoDr59cV/5qnevi BvUWwDa3CjXfbyqwRvL/L8eqc1iGAd0leOs0UNm1itMDjGCB+te4xlrMo2JmH7XSqJpA fL5Ghth1oZY2qmFNcW2YffRkB3d8DaVmTmkOB9S9+OgP5DaVbDFiRSTpZ7Oy3pMWs6RN mSaBn/0txo3oof0W/52B9oDcq0FVt+xh6NRlr9zPuKugKWI7G7WpYzbCBoi9UPxQr/EZ pEkw== X-Gm-Message-State: AKaTC03j35ntSPFWWSa4wf8FHU43EWmCN2kn8fdXSviHnsrQBCLyUSVdmbvmELuB/EGDkg== X-Received: by 10.99.244.17 with SMTP id g17mr115783562pgi.80.1481059553722; Tue, 06 Dec 2016 13:25:53 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id n17sm36880733pfg.80.2016.12.06.13.25.51 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 06 Dec 2016 13:25:52 -0800 (PST) Date: Tue, 6 Dec 2016 13:25:44 -0800 From: Stephen Hemminger To: Thomas Monjalon Cc: dev@dpdk.org Message-ID: <20161206132544.720c8627@xeon-e3> In-Reply-To: <2826842.JE1PHBM7JX@xps13> References: <2826842.JE1PHBM7JX@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] proposal deadline X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2016 21:25:54 -0000 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.