All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW09
Date: Fri, 26 Feb 2016 17:36:08 +0000	[thread overview]
Message-ID: <1456508168.11498.95.camel@linuxfoundation.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]

Current Dev Position: YP 2.1 M3
Next Deadline: YP 2.1 M3 Cutoff (Feature Freeze) February 29, 2016
 
SWAT team rotation: Tracy -> Alejandero
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
 
Key Status/Updates:
* 2.1 Feature Freeze is upon us. If there is any feature you want to 
  see in 2.1 which isn't going to make the deadline, talk to RP.
* We plan to release 2.1 M2 despite the sato glib issue, granting an
  exception for the high bug and then  concentrate on 2.1 M3.
* 2.1 M3 build won't happen until sato glib issue resolved.
* Also planning to merge the gobject-introspection changes 
* Pseudo connection issue appears to be addressed with increased retry 
  numbers. Tests ongoing.
* We're about to try and transition meta-yocto within meta-yocto to 
  meta-poky. The amount of pain this is causing is horrible :(.
* We're considering a bump in the minimum git version requirements 
  due to the requirements of various pieces of project tooling.
* We're rebuilding jethro 2.0.1 due to the glibc security issue, now 
  at -rc7.
 
Key YP 2.1 Dates:
YP 2.1 M2 Target release date is February 12, 2016 (Will slip a few
weeks.)
YP 2.1 M3 Cutoff (Feature Freeze) date is February 29, 2016 noon GMT
YP 2.1 M3 Target release date is March 18, 2016
YP 2.1 M4 / Final Cutoff: March 28, 2016 noon GMT - Stabilization only
milestone.
YP 2.1 Final Release Target: April 29, 2016
 
Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.1_Features
 
Tracking Metrics:
            WDD 2565 (last week 2585)
(https://wiki.yoctoproject.org/charts/combo.html)
 
[If anyone has suggestions for other information you’d like to see on
this weekly status update, let us know!]
 
Thanks,
 
Richard-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: [OE-core] Yocto Project Status WW09
Date: Fri, 26 Feb 2016 17:36:08 +0000	[thread overview]
Message-ID: <1456508168.11498.95.camel@linuxfoundation.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]

Current Dev Position: YP 2.1 M3
Next Deadline: YP 2.1 M3 Cutoff (Feature Freeze) February 29, 2016
 
SWAT team rotation: Tracy -> Alejandero
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
 
Key Status/Updates:
* 2.1 Feature Freeze is upon us. If there is any feature you want to 
  see in 2.1 which isn't going to make the deadline, talk to RP.
* We plan to release 2.1 M2 despite the sato glib issue, granting an
  exception for the high bug and then  concentrate on 2.1 M3.
* 2.1 M3 build won't happen until sato glib issue resolved.
* Also planning to merge the gobject-introspection changes 
* Pseudo connection issue appears to be addressed with increased retry 
  numbers. Tests ongoing.
* We're about to try and transition meta-yocto within meta-yocto to 
  meta-poky. The amount of pain this is causing is horrible :(.
* We're considering a bump in the minimum git version requirements 
  due to the requirements of various pieces of project tooling.
* We're rebuilding jethro 2.0.1 due to the glibc security issue, now 
  at -rc7.
 
Key YP 2.1 Dates:
YP 2.1 M2 Target release date is February 12, 2016 (Will slip a few
weeks.)
YP 2.1 M3 Cutoff (Feature Freeze) date is February 29, 2016 noon GMT
YP 2.1 M3 Target release date is March 18, 2016
YP 2.1 M4 / Final Cutoff: March 28, 2016 noon GMT - Stabilization only
milestone.
YP 2.1 Final Release Target: April 29, 2016
 
Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.1_Features
 
Tracking Metrics:
            WDD 2565 (last week 2585)
(https://wiki.yoctoproject.org/charts/combo.html)
 
[If anyone has suggestions for other information you’d like to see on
this weekly status update, let us know!]
 
Thanks,
 
Richard-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


             reply	other threads:[~2016-02-26 17:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 17:36 Richard Purdie [this message]
2016-02-26 17:36 ` [OE-core] Yocto Project Status WW09 Richard Purdie
2016-02-26 18:45 ` Philip Balister
2016-02-26 18:45   ` [OE-core] " Philip Balister
2016-02-26 18:50   ` Richard Purdie
2016-02-26 18:50     ` [OE-core] " Richard Purdie
2016-02-26 19:52     ` [yocto] " Rudolf J Streif
2016-02-26 19:52       ` [OE-core] " Rudolf J Streif
2016-02-26 20:16       ` [yocto] " Philip Balister
2016-02-26 20:16         ` [OE-core] " Philip Balister
2016-02-26 20:58         ` [yocto] " Burton, Ross
2016-02-26 20:58           ` [OE-core] " Burton, Ross
2016-02-27  1:29           ` [yocto] " Christopher Larson
2016-02-27  1:29             ` [OE-core] " Christopher Larson
2016-02-29 11:10 ` FW: " Barros Pena, Belen

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=1456508168.11498.95.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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.