From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: releases scheduling Date: Sun, 13 Dec 2015 20:22:59 +0100 Message-ID: <1667533.heuKAiE6KB@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-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 9DBD937A6 for ; Sun, 13 Dec 2015 20:24:17 +0100 (CET) Received: by mail-wm0-f46.google.com with SMTP id p66so18160970wmp.0 for ; Sun, 13 Dec 2015 11:24:17 -0800 (PST) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id t3sm25996691wjz.11.2015.12.13.11.24.16 for (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Dec 2015 11:24:16 -0800 (PST) List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi all, We need to define the deadlines for the next releases. During 2015, we were doing a release every 4 months. If we keep the same pace, the next releases would be: 2.3: end of March 2.4: end of July 2.5: end of November However, things move fast and it may be a bit long to wait 4 months for a feature. That's why I suggest to progressively shorten release terms: 2.3: end of March 2.4: mid July 2.5: end of October and continue with a release every 3 months: 2.6: end of January 2.7: end of April 2.8: end of July This planning would preserve some of the major holiday periods (February, May, August, December). The first period, for the first submission of a feature, was 2 months long. Then we had 2 other months to discuss, merge and fix. We should shorten only the first period. Anyway, the next deadlines should be unchanged: - January 31: end of first submission phase - March 31: release 2.3 Opinions are welcome.