All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yocto@yoctoproject.org
Subject: Yocto Project Status WW27
Date: Fri, 01 Jul 2016 16:29:06 +0100	[thread overview]
Message-ID: <1467386946.8590.178.camel@linuxfoundation.org> (raw)

Current Dev Position: YP 2.2 M2
Next Deadline: YP 2.2 M2 cut off would be: 7/18/16

SWAT team rotation: Armin -> Bill
(https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team)

Key Status/Updates:

* QA test report for 2.2 M1 is looking reasonable. There are some issues in toaster, 
  wic and eclipse but nothing that looks like it would block the milestone.

* The release is very “front loaded” with many things being targeted for M1, 
  then slipping to M2 and not many things targeted for M2/M3. We need to 
  get better at load balancing bugs.

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 2718 (last week 2745)
(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!]


             reply	other threads:[~2016-07-01 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-01 15:29 Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-03 17:03 Yocto Project Status WW27 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=1467386946.8590.178.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.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.