From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.93; helo=mga11.intel.com; envelope-from=star.zeng@intel.com; receiver=edk2-devel@lists.01.org Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 15F44221786D5 for ; Thu, 30 Nov 2017 18:24:25 -0800 (PST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Nov 2017 18:28:51 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,343,1508828400"; d="scan'208";a="14018645" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga002.jf.intel.com with ESMTP; 30 Nov 2017 18:28:51 -0800 Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 30 Nov 2017 18:28:51 -0800 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by fmsmsx120.amr.corp.intel.com (10.18.124.208) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 30 Nov 2017 18:28:50 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.175]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.159]) with mapi id 14.03.0319.002; Fri, 1 Dec 2017 10:28:48 +0800 From: "Zeng, Star" To: "Gao, Liming" , Felix Poludov , "afish@apple.com" CC: "edk2-devel@lists.01.org" , "Zeng, Star" Thread-Topic: [edk2] edk2 interface deprecation policy Thread-Index: AdNp4pfr7+u/EK+jQZukLW6fR9eGA///rSQAgABYJgD//z16IP/+cLbQ Date: Fri, 1 Dec 2017 02:28:48 +0000 Message-ID: <0C09AFA07DD0434D9E2A0C6AEB0483103B9BE738@shsmsx102.ccr.corp.intel.com> References: <9333E191E0D52B4999CE63A99BA663A00302B63C30@atlms1.us.megatrends.com> <9333E191E0D52B4999CE63A99BA663A00302B64F9B@atlms1.us.megatrends.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E188BBE@SHSMSX104.ccr.corp.intel.com> In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E188BBE@SHSMSX104.ccr.corp.intel.com> Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: edk2 interface deprecation policy X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 02:24:26 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The negative impact is there will be more and more deprecated codes in the = project. We'd better have an exit mechanism for them although some of them may need = to be kept for compatibility case by case. Thanks, Star -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Gao,= Liming Sent: Friday, December 1, 2017 9:51 AM To: Felix Poludov ; afish@apple.com Cc: edk2-devel@lists.01.org Subject: Re: [edk2] edk2 interface deprecation policy Felix: I agree to define the tag to specify the deprecated definition, library a= nd drivers. If so, user can easily know which one is not used any more. But= , I think we can still keep them in edk2 project, because they have no nega= tive impact.=20 Thanks Liming >-----Original Message----- >From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of=20 >Felix Poludov >Sent: Friday, December 01, 2017 6:12 AM >To: afish@apple.com >Cc: edk2-devel@lists.01.org >Subject: Re: [edk2] edk2 interface deprecation policy > >I agree. It would be beneficial to have a mailing list discussion on=20 >how to deal with the deprecated item. >In some cases it would make sense to tag an interface as deprecated,=20 >but keep in the code base for a while (6 month?) before actually deleting = it. > >-----Original Message----- >From: afish@apple.com [mailto:afish@apple.com] >Sent: Thursday, November 30, 2017 11:57 AM >To: Felix Poludov >Cc: edk2-devel@lists.01.org >Subject: Re: [edk2] edk2 interface deprecation policy > >Felix, > >I don't think we have one.... > >Adding new interfaces does not impact the downstream projects, but=20 >depreciating interface can break stuff. Seems like it might at least be=20 >a good idea to have a depreciation discussion on the mailing list. I'm=20 >open to other suggestions.... > >Thanks, > >Andrew Fish > >> On Nov 30, 2017, at 6:00 AM, Felix Poludov wrote: >> >> Does edk2 have a policy regarding deprecation of interface definition >headers? >> I can see that definition of the UgaDraw protocol that was deprecated=20 >> years >ago (I believe in UEFI 2.0) is still part of the code base; yet,=20 >definition of the SMM Communication ACPI Table that was deprecated this=20 >year in UEFI 2.6B has already been removed. >> >> Please consider the environment before printing this email. >> >> The information contained in this message may be confidential and >proprietary to American Megatrends, Inc. This communication is=20 >intended to be read only by the individual or entity to whom it is=20 >addressed or by their designee. If the reader of this message is not=20 >the intended recipient, you are on notice that any distribution of this=20 >message, in any form, is strictly prohibited. Please promptly notify=20 >the sender by reply e-mail or by telephone at 770-246-8600, and then delet= e or destroy all copies of the transmission. >> _______________________________________________ >> edk2-devel mailing list >> edk2-devel@lists.01.org >> https://lists.01.org/mailman/listinfo/edk2-devel > > >Please consider the environment before printing this email. > >The information contained in this message may be confidential and=20 >proprietary to American Megatrends, Inc. This communication is=20 >intended to be read only by the individual or entity to whom it is=20 >addressed or by their designee. If the reader of this message is not=20 >the intended recipient, you are on notice that any distribution of this=20 >message, in any form, is strictly prohibited. Please promptly notify=20 >the sender by reply e-mail or by telephone at 770-246-8600, and then delet= e or destroy all copies of the transmission. >_______________________________________________ >edk2-devel mailing list >edk2-devel@lists.01.org >https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel