From: "Jolley, Stephen K" <stephen.k.jolley@intel.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW09’17
Date: Mon, 27 Feb 2017 16:59:06 +0000 [thread overview]
Message-ID: <9ADD3FDE8B189B4AA2F8A3C711F8155E573720C5@fmsmsx111.amr.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2332 bytes --]
Current Dev Position: YP 2.3 M3
Next Deadline: YP 2.3 M3 by Feb. 27, 2017
*** FEATURE FREEZE for 2.3 is now in effect. ***
SWAT team rotation: Anibal -> Todor on Feb. 24, 2017.
SWAT team rotation: Todor -> Tracy on Mar. 4, 2017.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
· We’re now into feature freeze for 2.3.
· We need to decide which recently submitted items should be merged. Some major items In particular:
o rpm v4/dnf to replace rpm v5/smart?
o Merging go into OE-Core?
o Separate out elderly GPLv2 into a separate layer?
o Graphics stack vulkan changes?
o Large queue of wic changes?
I am leaning towards trying to take these even if they do delay the M3 release slightly as we do have some time left in M4 to stabilize.
· Unfortunately we continue to have stability issues in testing. There appear to be some intermittent failures which have crept into master and M3 merging will likely be delayed until those issues have been tracked down. They seem to affect sdk image size, breaking the 4GB limit and eSDKs stopping containing libxml2 under unknown circumstances, possibly amongst other issues.
· YP 2.2.1 has been released
Proposed upcoming dot releases:
YP 2.1.3 Cut off May 15, 2017
YP 2.1.3 Release by May 26, 2017
YP 2.2.2 Cut off May 29, 2017
YP 2.2.2 Release by June 9, 2017
Key YP 2.3 Dates:
YP 2.3 M3 Cutoff is Feb 27, 2017
YP 2.3 M3 Release is Mar. 10, 2017
YP 2.3 M4 Cutoff is April 10, 2017
YP 2.3 M4 Release is May 5, 2017
Tracking Metrics:
WDD 2747 (last week 2682)
(https://wiki.yoctoproject.org/charts/combo.html)
Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
• Work Telephone: (503) 712-0534
• Cell: (208) 244-4460
• Email: stephen.k.jolley@intel.com
[-- Attachment #2: Type: text/html, Size: 22767 bytes --]
next reply other threads:[~2017-02-27 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 16:59 Jolley, Stephen K [this message]
2017-02-28 2:09 ` [OE-core] Yocto Project Status WW09’17 akuster808
2017-02-28 2:09 ` akuster808
2017-02-28 8:55 ` [OE-core] " Alexander Kanavin
2017-02-28 8:55 ` Alexander Kanavin
2017-02-28 9:20 ` [OE-core] " Burton, Ross
2017-02-28 9:20 ` Burton, Ross
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-all 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=9ADD3FDE8B189B4AA2F8A3C711F8155E573720C5@fmsmsx111.amr.corp.intel.com \
--to=stephen.k.jolley@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.