All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Yocto Project Status WW34
Date: Fri, 19 Aug 2016 08:23:05 -0700	[thread overview]
Message-ID: <1471620185.6975.191.camel@linux.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2844 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: Juro -> Anibal
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:
 * We’re drawing close to the M3 deadline and feature freeze for 2.2. There is still a significant number of features outstanding with several looking to be at risk at this point.
 * The bitbake multi-config build series has now merged. 
 * We’ve re-enabled prelink on x86/mips. ppc/arm was disabled whilst we investigated test failures but will likely be enabled since the issues are looking to be a binutils bug.
 * We upgraded to gcc 6.2rc1 (we will track 6.2 through to our release)
 * Uninative 1.3 was released to deal with some locale problems. This will need to be backported to krogoth as a 1.0.1 release of uninative.
 * Current master is going to go through a full QA pass before M3 to try and make sure we are dealing with all the known bugs.
 * We are starting to see significant ‘random’ autobuilder failures again:
    * Mips machine ‘failure to start’ despite booting the kernel: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10136
    * Systemd logging failure: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10128
    * Unknown ppc failure: https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/910/steps/Running%20Sanity%20Tests/logs/stdio
    * Uvesa timeout issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=8245
    * Busybox parallel make race: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10116
We need to get to grips with these as a matter of urgency as they do keep recurring and several occurred during our QA build, sadly. I am getting quite concerned about these.
 * 2.1.1 has been released, finally!
 * We will be moving to the 4.7 kernel before M3 closes, and evaluating a move to 4.8 in mid-September.  We will be keeping both the 4.1 (as LTSI) and 4.4 (as LTS) kernels.  GregKH has announced that 4.9 will be the next LTS for a Dec/Jan release, therefore our 4.7 (or 4.8) will be short lived kernels.

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 2706  (last week 2712)
(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: 17641 bytes --]

             reply	other threads:[~2016-08-19 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 15:23 Saul Wold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-21 15:23 Yocto Project Status WW34 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=1471620185.6975.191.camel@linux.intel.com \
    --to=sgw@linux.intel.com \
    --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.