All of lore.kernel.org
 help / color / mirror / Atom feed
* Yocto Project Status WW06'20
@ 2020-02-11 15:51 ` sjolley.yp.pm
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Jolley @ 2020-02-11 15:51 UTC (permalink / raw)
  To: yocto, openembedded-core

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

Current Dev Position: YP 3.1 M3

Next Deadline: YP 3.1 M3 build date 2/24/2020

 

Next Team Meetings:

*	Bug Triage meeting Thursday Feb. 13th  at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
*	Monthly Project Meeting Tuesday Mar. 3rd  at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Weekly Engineering Sync Tuesday Feb. 11th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Twitch - Next event is Tuesday Feb. 11th at 8am PDT (
<https://www.twitch.tv/yocto_project> https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*	YP 3.1 M2 was released
*	We're now in a much better position with reproducibility issues
after around 20 patches merged addressing various problems. Some issues
still remain but the bulk of the issues appear to be under control now.
*	Due to the number and type of fixes found, the 3.0.2 rc1 build will
be abandoned and rc2 built with the reproducibility fixes (as well as
additional hashserv/multiconfig fixes). This delays 3.0.2 by a week but for
a reasonable set of improvements.
*	YP 3.0.2 should therefore enter QA within the next day or so.
*	Review of newly queued warrior (2.7.3) patches will happen later
this week once 3.0.2 is in QA.
*	With the new fixes and a small fix to the autobuilder code, we
managed the first green "full" build in nearly three months.
*	The incoming patch queue is roughly under control again
*	We're collecting a list of companies, products and projects which
use the Yocto Project on the wiki:
<https://wiki.yoctoproject.org/wiki/Project_Users>
https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are
missing (or email Richard/Stephen who can add).
*	One worrying metric is that the WDD is now on level with the high of
2017 so our worst defect weighting in two years. This is sadly unsurprising
and directly correlated to a lack of participation in the triage process and
a lack of people working on general bug fixing.
*	The triage team is worried about attendance at triage meetings and
the project is finding it hard to find people to help fix bugs. If anyone is
willing to work on bugs, assistance would be greatly appreciated.

 

YP 3.1 Milestone Dates:

*	YP 3.1 M3 build date 2/24/2020
*	YP 3.1 M3 release date 3/6/2020
*	YP 3.1 M4 build date  3/30/2020
*	YP 3.1 M4 release date  4/24/2020

 

Planned upcoming dot releases:

*	YP 2.7.3 build date  2/10/2020
*	YP 2.7.3 release date 2/21/2020
*	YP 3.0.2 build date  2/3/2020
*	YP 3.0.2 release date 2/14/2020

 

Tracking Metrics:

*	WDD 2728 (last week 2767) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
*	Poky Patch Metrics  

*	Total patches found: 1361 (last week 1368)
*	Patches in the Pending State: 547 (40%) [last week 544 (40%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 <https://wiki.yoctoproject.org/wiki/TSC>
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:
<https://wiki.yoctoproject.org/wiki/Weekly_Status>
https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[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

*    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com> 

 


[-- Attachment #2: Type: text/html, Size: 35138 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Yocto Project Status WW06'20
@ 2020-02-11 15:51 ` sjolley.yp.pm
  0 siblings, 0 replies; 2+ messages in thread
From: sjolley.yp.pm @ 2020-02-11 15:51 UTC (permalink / raw)
  To: yocto, openembedded-core

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

Current Dev Position: YP 3.1 M3

Next Deadline: YP 3.1 M3 build date 2/24/2020

 

Next Team Meetings:

*	Bug Triage meeting Thursday Feb. 13th  at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
*	Monthly Project Meeting Tuesday Mar. 3rd  at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Weekly Engineering Sync Tuesday Feb. 11th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Twitch - Next event is Tuesday Feb. 11th at 8am PDT (
<https://www.twitch.tv/yocto_project> https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*	YP 3.1 M2 was released
*	We're now in a much better position with reproducibility issues
after around 20 patches merged addressing various problems. Some issues
still remain but the bulk of the issues appear to be under control now.
*	Due to the number and type of fixes found, the 3.0.2 rc1 build will
be abandoned and rc2 built with the reproducibility fixes (as well as
additional hashserv/multiconfig fixes). This delays 3.0.2 by a week but for
a reasonable set of improvements.
*	YP 3.0.2 should therefore enter QA within the next day or so.
*	Review of newly queued warrior (2.7.3) patches will happen later
this week once 3.0.2 is in QA.
*	With the new fixes and a small fix to the autobuilder code, we
managed the first green "full" build in nearly three months.
*	The incoming patch queue is roughly under control again
*	We're collecting a list of companies, products and projects which
use the Yocto Project on the wiki:
<https://wiki.yoctoproject.org/wiki/Project_Users>
https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are
missing (or email Richard/Stephen who can add).
*	One worrying metric is that the WDD is now on level with the high of
2017 so our worst defect weighting in two years. This is sadly unsurprising
and directly correlated to a lack of participation in the triage process and
a lack of people working on general bug fixing.
*	The triage team is worried about attendance at triage meetings and
the project is finding it hard to find people to help fix bugs. If anyone is
willing to work on bugs, assistance would be greatly appreciated.

 

YP 3.1 Milestone Dates:

*	YP 3.1 M3 build date 2/24/2020
*	YP 3.1 M3 release date 3/6/2020
*	YP 3.1 M4 build date  3/30/2020
*	YP 3.1 M4 release date  4/24/2020

 

Planned upcoming dot releases:

*	YP 2.7.3 build date  2/10/2020
*	YP 2.7.3 release date 2/21/2020
*	YP 3.0.2 build date  2/3/2020
*	YP 3.0.2 release date 2/14/2020

 

Tracking Metrics:

*	WDD 2728 (last week 2767) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
*	Poky Patch Metrics  

*	Total patches found: 1361 (last week 1368)
*	Patches in the Pending State: 547 (40%) [last week 544 (40%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 <https://wiki.yoctoproject.org/wiki/TSC>
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:
<https://wiki.yoctoproject.org/wiki/Weekly_Status>
https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[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

*    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com> 

 


[-- Attachment #2: Type: text/html, Size: 35138 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-02-11 15:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-11 15:51 Yocto Project Status WW06'20 Stephen Jolley
2020-02-11 15:51 ` sjolley.yp.pm

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.