From: Saul Wold <sgw@linux.intel.com>
To: Yocto Discussion <yocto@yoctoproject.org>,
OpenEmbedded List <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW32
Date: Fri, 05 Aug 2016 09:30:50 -0700 [thread overview]
Message-ID: <1470414650.3175.420.camel@linux.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
Current Dev Position: YP 2.2 M3
Next Deadline: YP 2.2 M3 which will be Aug 29th (5:00pm GMT)
SWAT team rotation: Randy -> Leo
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
* We decided to release M2 with known issues. We have a good handle on some of them, there are others which are unknown but there is no one specific cause of the bugs.
* We will run another full QA pass before M3 to try and make sure we are dealing with the known bugs.
* Merging of patches continues to be slow as it is proving hard to work out which patches are causing which breakage. The test matrix continues to increase with people being upset if their personal favourite set of options breaks yet we can’t expect to test and catch every regression. We’re not sure what to do about this, the scope of the testing is greater than it ever has been but it does seem to be slowing things down.
* A patch for performance issues with pseudo when using xattrs have was merged
* 2.1.1 is currently in QA and is expected to be completed early next week, this update contains numerous fixes for for a variety of areas including CVEs, GCC 6.x on Host OS and updated SRC_URIs
Key YP 2.2 Dates:
* YP 2.2 M1 release would be: 6/24/16
* YP 2.2 M2 cut off would be: 7/18/16
* YP 2.2 M2 release would be: 7/29/16
* YP 2.2 M3 cut off would be: 8/29/16
* YP 2.2 M3 release would be: 9/9/16
* YP 2.2 M4 cut off would be: 10/3/16
* YP 2.2 M4 release would be: 10/28/16
Tracking Metrics:
WDD 2714 (last week 2744)
(https://wiki.yoctoproject.org/charts/combo.html)
Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
[-- Attachment #2: Type: text/html, Size: 11823 bytes --]
next reply other threads:[~2016-08-05 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 16:30 Saul Wold [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-07 14:54 Yocto Project Status WW32 Jolley, Stephen K
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=1470414650.3175.420.camel@linux.intel.com \
--to=sgw@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox