* Yocto Project Status WW01
@ 2017-01-03 15:51 Jolley, Stephen K
2017-01-03 16:16 ` Richard Purdie
0 siblings, 1 reply; 3+ messages in thread
From: Jolley, Stephen K @ 2017-01-03 15:51 UTC (permalink / raw)
To: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
[-- Attachment #1: Type: text/plain, Size: 2072 bytes --]
Current Dev Position: YP 2.3 M2 -> M3
Next Deadline: YP 2.3 M2 by Jan 23, 2017
SWAT team rotation: Maxin -> Joshua
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
* M1 is having some QA difficulties due to some kind of bad interaction between the PR service and tinfoil2. We're waiting until people are back from vacation and up to speed before we decide what to do about this.
* Both Ross and Richard decided to spend time away from computers over the holidays so things have not really changed much over the past couple of weeks, there is a small backlog of patches pending which will be worked through this week.
* M2 will be upon us sooner than we realize and there are some key changes such as recipe specific sysroots and the oeqa framework rework pending with some potential for disruption. Wider testing of these patch sets as they're published would be appreciated.
Proposed upcoming dot releases:
YP 2.2.1 Release by Jan. 20, 2017
YP 2.1.3 Release by May. 19, 2017
Key YP 2.3 Dates:
YP 2.3 M1 Release is Dec. 23, 2016
YP 2.3 M2 Cutoff is Jan. 23, 2017
YP 2.3 M2 Release is Feb. 3, 2017
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 3, 2017
YP 2.3 M4 Release is April 28, 2017
Tracking Metrics:
WDD 2594 (last week 2559)
(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: 17237 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Yocto Project Status WW01
2017-01-03 15:51 Yocto Project Status WW01 Jolley, Stephen K
@ 2017-01-03 16:16 ` Richard Purdie
0 siblings, 0 replies; 3+ messages in thread
From: Richard Purdie @ 2017-01-03 16:16 UTC (permalink / raw)
To: Jolley, Stephen K, yocto@yoctoproject.org,
openembedded-core@lists.openembedded.org
On Tue, 2017-01-03 at 15:51 +0000, Jolley, Stephen K wrote:
> Current Dev Position: YP 2.3 M2 -> M3
> Next Deadline: YP 2.3 M2 by Jan 23, 2017
>
> SWAT team rotation: Maxin -> Joshua
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>
> Key Status/Updates:
> · M1 is having some QA difficulties due to some kind of bad
> interaction between the PR service and tinfoil2. We’re waiting until
> people are back from vacation and up to speed before we decide what
> to do about this.
One question which came up was whether just to cherry-pick fixes for M1
into a branch, or whether we use master. For me personally master is
tempting but its probably safer just to use an M1 branch as master has
moved on a fair bit. I wanted to give people an opportunity to express
opinions either way.
Cheers,
Richard
^ permalink raw reply [flat|nested] 3+ messages in thread
* Yocto Project Status WW01
@ 2017-01-03 15:38 Jolley, Stephen K
0 siblings, 0 replies; 3+ messages in thread
From: Jolley, Stephen K @ 2017-01-03 15:38 UTC (permalink / raw)
To: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]
Current Dev Position: YP 2.3 M2 -> M3
Next Deadline: YP 2.3 M2 by Jan 23, 2017
SWAT team rotation: Maxin -> Joshua
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
* M1 is having some QA difficulties due to some kind of bad interaction between the PR service and tinfoil2. We're waiting until people are back from vacation and up to speed before we decide what to do about this.
* Both Ross and Richard decided to spend time away from computers over the holidays so things have not really changed much over the past couple of weeks, there is a small backlog of patches pending which will be worked through this week.
* M2 will be upon us sooner than we realize and there are some key changes such as recipe specific sysroots pending with some potential for disruption. Wider testing of these patch sets as they're published would be appreciated.
Proposed upcoming dot releases:
YP 2.2.1 Release by Jan. 20, 2017
YP 2.1.3 Release by May. 19, 2017
Key YP 2.3 Dates:
YP 2.3 M1 Release is Dec. 23, 2016
YP 2.3 M2 Cutoff is Jan. 23, 2017
YP 2.3 M2 Release is Feb. 3, 2017
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 3, 2017
YP 2.3 M4 Release is April 28, 2017
Tracking Metrics:
WDD 2594 (last week 2559)
(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: 15098 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-01-03 16:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-01-03 15:51 Yocto Project Status WW01 Jolley, Stephen K
2017-01-03 16:16 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2017-01-03 15:38 Jolley, Stephen K
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox