From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 798565A83 for ; Tue, 7 Jun 2016 18:21:25 +0200 (CEST) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga104.fm.intel.com with ESMTP; 07 Jun 2016 09:21:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,434,1459839600"; d="scan'208";a="117641645" Received: from irsmsx152.ger.corp.intel.com ([163.33.192.66]) by fmsmga004.fm.intel.com with ESMTP; 07 Jun 2016 09:21:23 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.240]) by IRSMSX152.ger.corp.intel.com ([169.254.6.247]) with mapi id 14.03.0248.002; Tue, 7 Jun 2016 17:21:22 +0100 From: "Mcnamara, John" To: Neil Horman , Thomas Monjalon CC: "dev@dpdk.org" , Christian Ehrhardt , Markos Chandras , "Panu Matilainen" Thread-Topic: [dpdk-dev] RFC: DPDK Long Term Support Thread-Index: AdG9qZjkO0DgyHDnRPC8xMkMMP+0dQBpDlKAAB/cTIAACRaFAAA5dc0g Date: Tue, 7 Jun 2016 16:21:21 +0000 Message-ID: References: <20160605181513.GA11762@neilslaptop.think-freely.org> <37570042.soqC7jPioi@xps13> <20160606134742.GA3867@hmsreliant.think-freely.org> In-Reply-To: <20160606134742.GA3867@hmsreliant.think-freely.org> 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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjI3YjM0N2EtYTc4OC00ODM1LTlkM2MtYWM4NzYxM2NkNDc1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjRBWlFVQUlyc3MxRXdrXC9SaldzS25NclkxcUhhNjZaeXdPb2wxc0lKTlBRPSJ9 x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] RFC: DPDK 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: Tue, 07 Jun 2016 16:21:26 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Neil Horman > Sent: Monday, June 6, 2016 2:48 PM > To: Thomas Monjalon > Cc: dev@dpdk.org; Mcnamara, John ; Christian > Ehrhardt ; Markos Chandras > ; Panu Matilainen > Subject: Re: [dpdk-dev] RFC: DPDK Long Term Support >=20 > While I don't disagree with that statement (LTS does provide both of thos= e > things if the maintainer does it properly), I'm forced to ask the > question, before we solve this problem in a new way, lets ask why the > existing way isn't being used. Do developers just not care about > backwards compatibility? Is the process to hard? Something else? I > really don't like the idea of abandoning what currently exists to replace > it with something else, without first addressing why what we have isn't > working. Hi Neil, I think these questions around why the current ABI policy isn't working=20 (or at least not working well) and how it can be fixed are worth raising as a new discussion. John. --=20