From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id:organization:user-agent:in-reply-to :references:mime-version:content-transfer-encoding:content-type; bh=HEFzal6eClU8/QJkbN+xbc5FEKkDyajHIwM3Mmk43To=; b=0b+K+8yMlqROs/PYdu+CMrI7/aR08z4Y2kG81ihgmauN7EoRB8ytAxuMKhX3AV/PnY gMexItzyh4zhJ/iQIturk0gRB1Jd87RpBUssrG0yKEIKNW8gxSoew0pr/yt9aD2uek2M y6LxmH7WnCoi2Pt+MqryjuI4eviM/cqwdT1GRNXS63PLykk08rH729D5OfKibQSFWdWx 18dK535loSd28sJpen8M3xS3EKVV/BI5UB4/Vy36cgJP3Je+XZeRjuyXJTkt6r84P4VS rDYi0HGYEcXNoJJfybKBrE9mcq7QCHxSgb0nRM7U1pIj3JsbpUSb9WCSfjSUT6rRrvvn JcoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=HEFzal6eClU8/QJkbN+xbc5FEKkDyajHIwM3Mmk43To=; b=V3SUTQz+WbWLY1kCnx7MdQlIQXZa2il4/XERKNP7zQmnLtVgzlbqRyiQ2VeHKwgOVm An3sQm1b/FpWzzd0ZFQACfu9+k2sVxC1MoWzAGD+PXxF4osU6tTkEB/yLBi/dyU8TdZX Cvc3xZNq8+GLUzLXQAIynjKf5uNMp07i5W9/NZH6256Wi5x0LuZxbh7mgkmqnvkM8bY9 qDjzdt4EzTi9jp6JREFJYkx6nzBsuqna7VmPj+OZGBr9y34JxOG+Frj0TlxYYjxidlpw /utZFHU493wWJnc7JAuqY4Qg1tkLiIIsT29splJDFHuBQ4i7akOh85uFdnTJsz041VYN s+7w== X-Gm-Message-State: ALoCoQnp7RWFSQa3bUcBMjpGKy/ue73VHWYalzQRUpjhFP+hDnuONHHroCSS8xNnZrQqANIkNcjjkZwLyf/wVqQsB4jXlzv46Q== X-Received: by 10.28.135.1 with SMTP id j1mr5698071wmd.11.1450483359189; 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) From: Thomas Monjalon To: dev@dpdk.org Date: Sat, 19 Dec 2015 01:01:24 +0100 Message-ID: <50018666.SlgxGSL9dQ@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <1667533.heuKAiE6KB@xps13> References: <1667533.heuKAiE6KB@xps13> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 00:02:39 -0000 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.