From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 3B97E2BE1 for ; Thu, 28 Jul 2016 14:34:36 +0200 (CEST) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga101.jf.intel.com with ESMTP; 28 Jul 2016 05:34:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,434,1464678000"; d="scan'208";a="146871445" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by fmsmga004.fm.intel.com with ESMTP; 28 Jul 2016 05:34:33 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.204]) by IRSMSX108.ger.corp.intel.com ([169.254.11.71]) with mapi id 14.03.0248.002; Thu, 28 Jul 2016 13:33:18 +0100 From: "Mcnamara, John" To: "dev@dpdk.org" Thread-Topic: DPDK Stable Releases and Long Term Support Thread-Index: AdHozCK90suRO+SgTY2M/KjRdaoUPQ== Date: Thu, 28 Jul 2016 12:33:18 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZDc0NjgxZDMtMGY4MC00OWEzLWI4MTUtYjJkMzFkNTM1YzNjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6InNrRzJPbVhHZG5lUWtNWTBEdVNjazhYa2YzdUhuSlwvdFRlN0E5eHpObXZzPSJ9 x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [dpdk-dev] DPDK Stable Releases and Long Term Support 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: Thu, 28 Jul 2016 12:34:36 -0000 This document sets out the guidelines for DPDK Stable Releases and Long Ter= m Support releases (LTS) based on the initial RFC and comments: http://dpdk.org/ml/archives/dev/2016-June/040256.html. In particular it incorporates suggestions for a Stable Release structure as well as a Long Term Support release. Introduction ------------ The purpose of the DPDK Stable Releases will be to maintain releases of DPD= K with backported fixes over an extended period of time. This will provide downstream consumers of DPDK with a stable target on which to base applications or packages. The Long Term Support release (LTS) will be a designation applied to a Stab= le Release to indicate longer support. Stable Releases --------------- Any major release of DPDK can be designated as a Stable Release if a maintainer volunteers to maintain it. A Stable Release will be used to backport fixes from a N release back to a = N-1 release, for example, from 16.11 to 16.07. The duration of a stable release should be one complete release cycle. It c= an be longer, up to 1 year, if a maintainer continues to support the stable branch, or if users supply backported fixes, however the explicit commitmen= t should be for one release cycle. The release cadence can be determined by the maintainer based on the number= of bugfixes and the criticality of the bugs. However, releases should be coordinated with the validation engineers to ensure that a tagged release h= as been tested. LTS Release ----------- A stable release can be designated as an LTS release based on community agreement and a commitment from a maintainer. An LTS release will have a maintenance duration of 2 years. It is anticipated that there should be at least 4 releases per year of the = LTS or approximately 1 every 3 months. However, the cadence can be shorter or longer depending on the number and criticality of the backported fixes. Releases should be coordinated with the validation engineers to ensu= re that a tagged release has been tested. Initial Stable Release ---------------------- The initial DPDK Stable Release will be 16.07. It will be viewed as a trial= of the Stable Release/LTS policy to determine what are the best working practi= ces for DPDK. The maintainer for the initial release will be Yuanhan Liu . It is hoped that other community members wil= l volunteer as maintainers for other Stable Releases. The initial targeted release for LTS is proposed to be 16.11 based on the results of the work carried out on the 16.07 Stable Release. A list has been set up for Stable Release/LTS specific discussions: . This address can also be used for CCing maintainers on b= ug fix submissions. What changes should be backported --------------------------------- The backporting should be limited to bug fixes. Features should not be backported to stable releases. It may be acceptable,= in limited cases, to back port features for the LTS release where: * There is a justifiable use case (for example a new PMD). * The change is non-invasive. * The work of preparing the backport is done by the proposer. * There is support within the community. Testing ------- Stable and LTS releases should be tested before release/tagging. Intel will provide validation engineers to test the 16.07 Stable Release an= d the initial LTS tree. Other community members should provide testing for ot= her stable releases. The validation will consist of compilation testing on the range of OSes supported by the master release and functional/performance testing on the current major/LTS release of the following OSes: * Ubuntu * RHEL * SuSE * FreeBSD Releasing --------- A Stable Release will be released by: * Tagging the release with YY.MM.nn (year, month, number) or similar. * Uploading a tarball of the release to dpdk.org. * Sending an announcement to the list. ABI --- The Stable Release should not be seen as a way of breaking or circumventing the DPDK ABI policy. Review of the Stable Release/LTS guidelines ------------------------------------------- This document serves as a set of guidelines for the planned Stable Releases/LTS activities. However, the actual process can be reviewed and amended over time, based on experiences and feedback.