From: "Richardson, Brian" <brian.richardson@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: Is the UDK2017 branch stable?
Date: Mon, 30 Jan 2017 22:00:08 +0000 [thread overview]
Message-ID: <80AC2BAA3152784F98F581129E5CF5AF6654A6A0@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <715fa336-4963-840f-d3da-38b5cfab7568@cmlab.biz>
UDK2017 is the current development branch. There is a stable release of UDK2017 planned for Q2'17 based on items scheduled for the next UEFI specification update and other improvements (HTTP/HTTPS Boot, SignedCapsulePkg, bug fixes, ...).
We're working on getting a feature list to publish on the wiki. Unfortunately, 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
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of David A. Van Arnem
Sent: Monday, January 30, 2017 4:29 PM
To: edk2-devel@lists.01.org <edk2-devel@ml01.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 UDK2015 (probably too new), so I wanted to check here before I use it as a starting 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
next prev parent reply other threads:[~2017-01-30 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 21:29 Is the UDK2017 branch stable? David A. Van Arnem
2017-01-30 22:00 ` Richardson, Brian [this message]
2017-01-30 22:22 ` David A. Van Arnem
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80AC2BAA3152784F98F581129E5CF5AF6654A6A0@ORSMSX114.amr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox