From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: releases scheduling Date: Sat, 19 Dec 2015 01:01:24 +0100 Message-ID: <50018666.SlgxGSL9dQ@xps13> References: <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-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id 595B78DB3 for ; Sat, 19 Dec 2015 01:02:39 +0100 (CET) Received: by mail-wm0-f49.google.com with SMTP id p187so4362701wmp.1 for ; Fri, 18 Dec 2015 16:02:39 -0800 (PST) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id g127sm8655602wmf.24.2015.12.18.16.02.38 for (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Dec 2015 16:02:38 -0800 (PST) In-Reply-To: <1667533.heuKAiE6KB@xps13> 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" 2015-12-13 20:22, Thomas Monjalon: > 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. It seems everybody agree with this new scheduling. The web site will be updated accordingly: http://dpdk.org/ml/archives/web/2015-December/000008.html There were some discussions to change the numbering scheme and rename 2.3 to 16.04. The patch (with arguments) is welcome. I won't do the patch myself because I don't care :) Another discussion was about having a long term support, i.e. doing some backport maintenance during a given period for some selected releases.