From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44]) by dpdk.org (Postfix) with ESMTP id BA63A3195 for ; Sat, 19 Dec 2015 10:48:32 +0100 (CET) Received: by mail-wm0-f44.google.com with SMTP id l126so13567359wml.1 for ; Sat, 19 Dec 2015 01:48:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:organization:user-agent :in-reply-to:references:mime-version:content-transfer-encoding :content-type; bh=laxTgl3gYATuX5GVW5XE9tR55O3iakS029xdHdJL8+Q=; b=qwDQ0DDAgBjcaLnzfvGiK0nf9pxz93aiaEhp0ZC6tv1t9H7yRIpzBhtCMLPJg14KT+ OTSbYlGI4iMA5sWqJh1SqgIqaJRenGfUeVKPThaMmwqxBUUQyJWWoWbB2gAADYuiJCX4 PUgBPIQKtPy+bY0Atvb4C9RU1BcI0+nZ7rRpI/rp0kkflN+cSq+B8f6AmOOZALZdx+c6 Zjnszt5lYqda/V20boDFS8rhF3efUYZj9Fh5ecbZbekGuihKDnQLMb4PSNlj0uo2fDCv a+xOYtN0i3n62mSrKDq7pMBlexYqnWoPnx3ge8ZpskSId/gr6FFIjo9QiYtfRC1K0ceR 6mgA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=laxTgl3gYATuX5GVW5XE9tR55O3iakS029xdHdJL8+Q=; b=Sk0mCiiXWocoRyXFpTT0RPBaTrNxbLUPYnlSKHGZvBO2sbi5mKpLnzqYh42KGmaigA r8ckwRg1iw2renQPK30tsLTxwvs8XG7GVjBpes5Gt4SdCtjMs3+e+RsBWO7O3qlmWuh/ cO2ebhprX9nGQONAkmfg+1CmKHQHFmUuBVmCTlaRkuhvRg+/S0wWoJv6QUr52pswg9JQ tA6sJjoyy4cVANMzYwqYiPvCX1p0EexCM77tvrd5eX35LbsJun7eGhEaAtWdVTLwGii3 BuA4QV9vnh/Q/82i31N9g/TgGZapfEaQPVKMvh+1k/+9Ol62nCFzzczXAoM09LcEoeET A2yw== X-Gm-Message-State: ALoCoQlcaTA7cNpP9CuwVu7n569DRl7ba3hnGt6DwuE0lgH7Yq/VHipiIzMYPZFGfePQDf12dMX9r05UwmRlIzNAeSc6z5qaOg== X-Received: by 10.28.53.130 with SMTP id c124mr7892893wma.16.1450518512593; Sat, 19 Dec 2015 01:48:32 -0800 (PST) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id vu4sm18419705wjc.2.2015.12.19.01.48.31 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 19 Dec 2015 01:48:31 -0800 (PST) From: Thomas Monjalon To: "Wiles, Keith" Date: Sat, 19 Dec 2015 10:47:17 +0100 Message-ID: <7182786.znu7DeD4EU@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: <1667533.heuKAiE6KB@xps13> <50018666.SlgxGSL9dQ@xps13> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] releases scheduling X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2015 09:48:32 -0000 2015-12-19 02:16, Wiles, Keith: > On 12/18/15, 6:01 PM, "dev on behalf of Thomas Monjalon" wrote: > > >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. > > I think we need to decide on the YY.MM.PP format then select > the dates for release now. This way we have it out of the way. > > The date of the release is the first day of the month for the release. > > March 1st - 15th is 16.03 Patches for 16.03 are from now to Feb 15th > Try to get the release out as close to the 1st as possible. > This one is a short release. > June 1st - 15th is 16.06 For 16.06 March 1st to May 15th > Sept 1st - 15th is 16.09 For 16.09 June 1st to Aug 15th > Dec 1st - 15th is 16.12 For 16.12 Sept 1st to Nov 15th. > > The 15th just before the release month is the deadline for patches, gives up 2 weeks before the release date and to the 15th of the release month to get the release out, but we should try for the 1st. The deadline is just a suggestion here or example, we can adjust it to something else. > > Tag 2.2.0 in the repo also as 15.12 plus I would suggest we tag it as LTS Long Term Support as well. Hi Keith, I'm confused. Have you read the proposal above and the patch above? I add it here again to make it more visible: http://dpdk.org/ml/archives/web/2015-December/000008.html And I copy-paste here: The release cycles are progressively shorten during 2016. Release 16.04 Proposal deadline: January 31 Integration deadline: March 10 Release: April 7 Release 16.07 Proposal deadline: May 8 Integration deadline: June 16 Release: July 18 Release 16.11 Proposal deadline: August 28 Integration deadline: September 30 Release: November 2 Release 17.02 Release: February 1 Release 17.05 Release: May 2 Release 17.08 Release: August 1 Release 17.11 Release: November 2