From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 7B34B81FBC for ; Mon, 30 Jan 2017 14:00:10 -0800 (PST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga102.fm.intel.com with ESMTP; 30 Jan 2017 14:00:09 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,312,1477983600"; d="scan'208";a="1089054914" Received: from orsmsx104.amr.corp.intel.com ([10.22.225.131]) by orsmga001.jf.intel.com with ESMTP; 30 Jan 2017 14:00:09 -0800 Received: from orsmsx155.amr.corp.intel.com (10.22.240.21) by ORSMSX104.amr.corp.intel.com (10.22.225.131) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 30 Jan 2017 14:00:09 -0800 Received: from orsmsx114.amr.corp.intel.com ([169.254.8.253]) by ORSMSX155.amr.corp.intel.com ([169.254.7.181]) with mapi id 14.03.0248.002; Mon, 30 Jan 2017 14:00:08 -0800 From: "Richardson, Brian" To: "edk2-devel@lists.01.org" Thread-Topic: [edk2] Is the UDK2017 branch stable? Thread-Index: AQHSez/0iuU8hmvQPEaLRx/ET3a0a6FRkP/A Date: Mon, 30 Jan 2017 22:00:08 +0000 Message-ID: <80AC2BAA3152784F98F581129E5CF5AF6654A6A0@ORSMSX114.amr.corp.intel.com> References: <715fa336-4963-840f-d3da-38b5cfab7568@cmlab.biz> In-Reply-To: <715fa336-4963-840f-d3da-38b5cfab7568@cmlab.biz> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2U2ZWFjOWItMGZlYi00N2MxLTlkMDEtMTZhYWY2NTc4YTA0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6InIwSWRkeFJteVpiNWx1bWxHdzBIU3VpOHJsMFBCSlVDOU4yQkE5S09uUWc9In0= x-originating-ip: [10.22.254.140] MIME-Version: 1.0 Subject: Re: Is the UDK2017 branch stable? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 22:00:10 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable UDK2017 is the current development branch. There is a stable release of UDK= 2017 planned for Q2'17 based on items scheduled for the next UEFI specifica= tion update and other improvements (HTTP/HTTPS Boot, SignedCapsulePkg, bug = fixes, ...).=20 We're working on getting a feature list to publish on the wiki. Unfortunate= ly, some of this depends on UEFI spec info that we can't publish until the = spec is finalized. I'll keep you posted. Thanks ... br --- Brian Richardson, Senior Technical Marketing Engineer, Intel Software brian.richardson@intel.com -- @intel_Brian (Twitter & WeChat) https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian= -richardson=20 -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Davi= d A. Van Arnem Sent: Monday, January 30, 2017 4:29 PM To: edk2-devel@lists.01.org Subject: [edk2] Is the UDK2017 branch stable? Hi all, On a fresh clone of the EDK2 repo, I noticed there is a "UDK2017" branch. Is this currently a stable branch, like UDK2015 before it? I did = not find any notes about a UDK2017 release on the tianocore website, only U= DK2015 (probably too new), so I wanted to check here before I use it as a s= tarting point. -- Regards, David Van Arnem Development Engineer IV Computer Measurement Laboratory, LLC _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel