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 B28388E60 for ; Sat, 19 Dec 2015 00:51:24 +0100 (CET) Received: by mail-wm0-f49.google.com with SMTP id p187so4513149wmp.0 for ; Fri, 18 Dec 2015 15:51:24 -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:in-reply-to:references; bh=qdhQb2VtlAHDOe3IEIdMlQs6jJuvDXofketAfKP6Ouc=; b=hKq+r6AYx7RzMufo5QZ2YOXi7hJS62zkgO2eeGcMzNt+Qxzc697tBX73fyNk90SPke RuByDz7OlKsXR19GnzB2senaCEpRNyVR2OxLS1cbk+OAcKSt4q8LKl/4juP8NH1/bxfF whAo9Q+pB9Gm0YprrYyeZ8zdjcQfD5bdnoYhqz6D+FYFWKnhdXDPLoWTbla/9mGr6AS+ 8CtGYg4YLWekTO49wiGEuYncjCxEbIivgtCNn9zQiFgP73mIAHMC/ZKnhdXi87hHD6st 3Viclzl20JNpeTA5gi6sGczOXPcxe2vOYSC3EZRm3YyJKhpW0xvrYIikaLKQliuYPZPK fMkg== 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:in-reply-to :references; bh=qdhQb2VtlAHDOe3IEIdMlQs6jJuvDXofketAfKP6Ouc=; b=XHjpDVKW9aCRazYTPj3YGoy8yz/jLxT5EanSUnWVpOecdvy4nAxYoX3cbMg4t/3OtQ XUIIgJgTYFI3I3HvfAoHwbFQ1XDQgqrNpk0dlAGZceG/k+nXnX1wQsB7iB5N/y3iq10Z rpli5nEdwF9UO+6FpKISTQoediap772I6R/hETWHaWg60A5k2QpfC5exQtgOpWXb9QFa g74bxQDbYgPw1CTc/IyrGuDpbhDVCpgMh9x3yurqJMB6fhlMxnHDJgLEtXV9hLgL0nVj ZAMtLOf4Jtei66fwupQrlex42YAKYBzm+gsPcq7Z2VKWsSeVY+U0DCV/x2xwPz9D3bLR bq4g== X-Gm-Message-State: ALoCoQmaA6VqUzr6A0kTSFGoh5HsEI70lJ+Bcn6/J/NlInJb07WxtoDqaZ+8CqhIzJJM3DEeFtoptlBlSPAQpajUW6jqIaC0sA== X-Received: by 10.28.126.84 with SMTP id z81mr6087356wmc.95.1450482684487; Fri, 18 Dec 2015 15:51:24 -0800 (PST) Received: from localhost.localdomain (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id v195sm8624679wmv.1.2015.12.18.15.51.23 for (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Dec 2015 15:51:23 -0800 (PST) From: Thomas Monjalon To: web@dpdk.org Date: Sat, 19 Dec 2015 00:50:06 +0100 Message-Id: <1450482606-6753-1-git-send-email-thomas.monjalon@6wind.com> X-Mailer: git-send-email 2.5.2 In-Reply-To: <1450482221-6404-1-git-send-email-thomas.monjalon@6wind.com> References: <1450482221-6404-1-git-send-email-thomas.monjalon@6wind.com> Subject: [dpdk-web] [PATCH 2/2] update release scheduling for 2016 X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2015 23:51:24 -0000 It may be a bit long to wait 4 months for a feature. Shorten release cycle progressively from 4 months to 3 months and try to preserve some of the major holiday periods (February, May, August, December). --- dev/roadmap.html | 87 ++++++++++++++++++++++++++----------------------------- dev/schedule.png | Bin 27965 -> 0 bytes 2 files changed, 41 insertions(+), 46 deletions(-) delete mode 100644 dev/schedule.png diff --git a/dev/roadmap.html b/dev/roadmap.html index 5c73d85..37a8d88 100644 --- a/dev/roadmap.html +++ b/dev/roadmap.html @@ -68,57 +68,52 @@
  • IPsec example
  • packet framework enhancements for edge router -

    The 3 major release cycles per annum system is designed to allow DPDK - to keep evolving at a rapid pace while giving enough opportunity - to implement and evolve contributions. -

    A minor version x.y.1 may be released to integrate some fixes or - minor changes without waiting several monthes for the next major version.

    Cycle model

    - schedule -

    The Merge Window will open once the previous release is complete, - and will close 8 weeks before the release date. - First version of a new feature can be submitted only during this period. - Features that miss the Merge Window will be deferred until the next release. -

    Following this, there is a Review Period to allow finishing reviews, - reworks and test patches. - Updated versions of patches (v2, v3, etc.) will be submitted to address comments. - For patches that are submitted early in the Merge Window, - this Review Period actually begin as soon as the v1 patchset is submitted. - For simplicity, this overlap is not shown in the diagram. -

    At the end of the Review Period, the first Release Candidate is out. - New features which were not properly reviewed and acknowledged at this time - will be postponed to the next releases. -

    A period of testing will follow, with bug fixes submitted to fix issues - found during testing, and additional Release Candidates built as required. -

    A final Release Candidate will be built 2 weeks before the release date, - and will undergo a final Regression Test period. - In order to ensure the stability of the release, - only fixes to high priority issues will be accepted during this time. - Fixes to lower priority issues will be deferred to a subsequent release. -

    Planning

    -

    Applying this model to the 2015 releases, the following are the major milestones: -

    Release 2.0 +

    A typical release should be done after 3 months (was 4 months during 2015). +

    It is designed to allow DPDK to keep evolving at a rapid pace while + giving enough opportunity to review, discuss and improve the contributions. +

    The merge window will open once the previous release is complete. + First version of a new feature must be submitted before the proposal deadline. + Features that miss this first period will be deferred until the next release. +

    Updated versions of patches (v2, v3, etc.) will be submitted to address comments. + The new features must be properly reviewed, tested and accepted before the + integration deadline. Otherwise, they will be postponed to the next releases. +

    At the end of the merge window, the first release candidate is out. +

    The last period is 1 month long and is dedicated to bug fixing. +

    Scheduling

    +

    The release cycles are progressively shorten during 2016. +

    Release 16.04

      -
    • Merge Window: 1st December 2014 to 30th January 2015 -
    • Review Period: 2nd February to 20th February -
    • RC Testing: 23rd February to 13th March -
    • Regression Test: 16th March to 27th March -
    • Release: 31st March +
    • Proposal deadline: January 31 +
    • Integration deadline: March 10 +
    • Release: April 7
    -

    Release 2.1 +

    Release 16.07

      -
    • Merge Window: 1st April to 5th June -
    • Review Period: 8th June to 26th June -
    • RC Testing: 29th June to 17th July -
    • Regression Test: 20th July to 31st July -
    • Release: 31st July +
    • Proposal deadline: May 8 +
    • Integration deadline: June 16 +
    • Release: July 18
    -

    Release 2.2 +

    Release 16.11

      -
    • Merge Window: 1st August to 2nd October -
    • Review Period: 5th October to 30th October -
    • RC Testing: 2nd November to 13th November -
    • Regression Test: 16th November to 27th November -
    • Release: 30th November +
    • 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
    diff --git a/dev/schedule.png b/dev/schedule.png deleted file mode 100644 -- 2.5.2