Yocto Project Status WW04'20

Yocto Project Status WW04'20

[Stephen Jolley]

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

Current Dev Position: YP 3.1 M3

Next Deadline: YP 3.1 M2 in QA - release 1/31/20

 

Next Team Meetings:

*	Bug Triage meeting Thursday Jan. 30th  at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
*	Monthly Project Meeting Tuesday Feb. 4th  at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Weekly Engineering Sync Tuesday Jan. 28th 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)

 

Tip of the Week:

*	The scripts in ${WORKDIR}/temp/run.XXX for shell tasks can be
quickly hacked and used for standalone debugging by replacing the function
call at the end with "bash -i" which will then drop you into a shell
environment matching the task being debugged (minus the fakeroot context). 
*	Bonus marks for anyone sending a patch to add the fakeroot context
as comments at the start of the scripts.
*	(send any tips you'd like to see here to Stephen or Richard)

 

Key Status/Updates:

*	YP 3.1 M2 is in QA but has issues with build reproducibility
*	We're unlikely to rebuild M2 as master has the same issues and they
look like they will take a while to resolve.
*	There are now serious problems with the build reproducibility test
failures on the autobuilder. We're not sure why there is a sudden set of
problems but they are real issues and causing most builds to fail. The tests
will have to be disabled unless they can be resolved quickly. There are
fixes merged for the CONFIG_SHELL issue and kbd and patches queued as a
potential fix for makeinfo. There are more remaining issues, some have open
bugs, others don't have bugs yet. Help with any of these would be
appreciated (or help filing the bugs).
*	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).
*	We have created a "documentation" list and a "licensing" list on the
yocto project mailing list infrastructure. We believe these topics would
benefit from dedicated discussions, the people involved usually aren't
interested in bulk email as would be found on other lists. The new lists can
be found at:  <https://lists.yoctoproject.org/g/licensing/join>
https://lists.yoctoproject.org/g/licensing/join and
<https://lists.yoctoproject.org/g/docs/join>
https://lists.yoctoproject.org/g/docs/join 
*	There is continued concern about the number of
recurring/intermittent failures in the automated testing, mostly from
selftest and testimage.
*	We continue to struggle to get clean 'full' builds due to the
reproducibility issues in particular.
*	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 M2 release date 1/31/2020
*	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 2765 (last week 2758) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
*	Poky Patch Metrics  

*	Total patches found: 1368 (last week 1357)
*	Patches in the Pending State: 545 (40%) [last week 536 (39%)]

 

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: 40820 bytes --]

Yocto Project Status WW04'20

[sjolley.yp.pm]

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

Current Dev Position: YP 3.1 M3

Next Deadline: YP 3.1 M2 in QA - release 1/31/20

 

Next Team Meetings:

*	Bug Triage meeting Thursday Jan. 30th  at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
*	Monthly Project Meeting Tuesday Feb. 4th  at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Weekly Engineering Sync Tuesday Jan. 28th 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)

 

Tip of the Week:

*	The scripts in ${WORKDIR}/temp/run.XXX for shell tasks can be
quickly hacked and used for standalone debugging by replacing the function
call at the end with "bash -i" which will then drop you into a shell
environment matching the task being debugged (minus the fakeroot context). 
*	Bonus marks for anyone sending a patch to add the fakeroot context
as comments at the start of the scripts.
*	(send any tips you'd like to see here to Stephen or Richard)

 

Key Status/Updates:

*	YP 3.1 M2 is in QA but has issues with build reproducibility
*	We're unlikely to rebuild M2 as master has the same issues and they
look like they will take a while to resolve.
*	There are now serious problems with the build reproducibility test
failures on the autobuilder. We're not sure why there is a sudden set of
problems but they are real issues and causing most builds to fail. The tests
will have to be disabled unless they can be resolved quickly. There are
fixes merged for the CONFIG_SHELL issue and kbd and patches queued as a
potential fix for makeinfo. There are more remaining issues, some have open
bugs, others don't have bugs yet. Help with any of these would be
appreciated (or help filing the bugs).
*	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).
*	We have created a "documentation" list and a "licensing" list on the
yocto project mailing list infrastructure. We believe these topics would
benefit from dedicated discussions, the people involved usually aren't
interested in bulk email as would be found on other lists. The new lists can
be found at:  <https://lists.yoctoproject.org/g/licensing/join>
https://lists.yoctoproject.org/g/licensing/join and
<https://lists.yoctoproject.org/g/docs/join>
https://lists.yoctoproject.org/g/docs/join 
*	There is continued concern about the number of
recurring/intermittent failures in the automated testing, mostly from
selftest and testimage.
*	We continue to struggle to get clean 'full' builds due to the
reproducibility issues in particular.
*	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 M2 release date 1/31/2020
*	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 2765 (last week 2758) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
*	Poky Patch Metrics  

*	Total patches found: 1368 (last week 1357)
*	Patches in the Pending State: 545 (40%) [last week 536 (39%)]

 

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: 40820 bytes --]

Re: [yocto] Yocto Project Status WW04'20

[Adrian Bunk]

On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
>...
> *	We have created a "documentation" list and a "licensing" list on the
> yocto project mailing list infrastructure. We believe these topics would
> benefit from dedicated discussions, the people involved usually aren't
> interested in bulk email as would be found on other lists. The new lists can
> be found at:  <https://lists.yoctoproject.org/g/licensing/join>
> https://lists.yoctoproject.org/g/licensing/join and
> <https://lists.yoctoproject.org/g/docs/join>
> https://lists.yoctoproject.org/g/docs/join 
>...

Would it be possible to also create a yocto-devel or yocto-core
mailing list for discussing development of Yocto?

Currently the yocto list is a mixture of core development list and forum 
for newbie user questions, with no easy way to have them separate.

Thanks
Adrian

Re: [yocto] Yocto Project Status WW04'20

[Alexander Kanavin]

Why separate them? I’d rather have newbies and experts in the same room.

Alex

> On 2 Feb 2020, at 14.28, Adrian Bunk <bunk@stusta.de> wrote:
> 
>> On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
>> ...
>> *    We have created a "documentation" list and a "licensing" list on the
>> yocto project mailing list infrastructure. We believe these topics would
>> benefit from dedicated discussions, the people involved usually aren't
>> interested in bulk email as would be found on other lists. The new lists can
>> be found at:  <https://lists.yoctoproject.org/g/licensing/join>
>> https://lists.yoctoproject.org/g/licensing/join and
>> <https://lists.yoctoproject.org/g/docs/join>
>> https://lists.yoctoproject.org/g/docs/join 
>> ...
> 
> Would it be possible to also create a yocto-devel or yocto-core
> mailing list for discussing development of Yocto?
> 
> Currently the yocto list is a mixture of core development list and forum 
> for newbie user questions, with no easy way to have them separate.
> 
> Thanks
> Adrian
> 

Re: [yocto] Yocto Project Status WW04'20

[Ross Burton]

On Sun, 2 Feb 2020 at 13:35, Adrian Bunk <bunk@stusta.de> wrote:
> Would it be possible to also create a yocto-devel or yocto-core
> mailing list for discussing development of Yocto?

What would it cover that isn't already covered in other lists?

Ross

Re: [yocto] Yocto Project Status WW04'20

[Adrian Bunk]

On Sun, Feb 02, 2020 at 03:16:24PM +0000, Ross Burton wrote:
> On Sun, 2 Feb 2020 at 13:35, Adrian Bunk <bunk@stusta.de> wrote:
> > Would it be possible to also create a yocto-devel or yocto-core
> > mailing list for discussing development of Yocto?
> 
> What would it cover that isn't already covered in other lists?

It would be easier to follow only development discussions if these 
would move to a dedicated list.

> Ross

cu
Adrian

Re: [yocto] Yocto Project Status WW04'20

[Philip Balister]

On 2/2/20 2:28 PM, Adrian Bunk wrote:
> On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
>> ...
>> *	We have created a "documentation" list and a "licensing" list on the
>> yocto project mailing list infrastructure. We believe these topics would
>> benefit from dedicated discussions, the people involved usually aren't
>> interested in bulk email as would be found on other lists. The new lists can
>> be found at:  <https://lists.yoctoproject.org/g/licensing/join>
>> https://lists.yoctoproject.org/g/licensing/join and
>> <https://lists.yoctoproject.org/g/docs/join>
>> https://lists.yoctoproject.org/g/docs/join 
>> ...
> 
> Would it be possible to also create a yocto-devel or yocto-core
> mailing list for discussing development of Yocto?
> 
> Currently the yocto list is a mixture of core development list and forum 
> for newbie user questions, with no easy way to have them separate.

We have openembedded-architecture for this.

http://lists.openembedded.org/mailman/listinfo/openembedded-architecture

Philip

> 
> Thanks
> Adrian
> 
> 
> 
> 

Re: [yocto] Yocto Project Status WW04'20

[Chuck Wolber]

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

On Sun, Feb 2, 2020 at 6:09 AM Alexander Kanavin <alex.kanavin@gmail.com>
wrote:

> Why separate them? I’d rather have newbies and experts in the same room..
>

Enthusiastic second to this.

If you separate things too much, newbies get no sense of the depth of the
project, and experienced people get less of a sense of the "newcomer pain
points".

Granted, this breaks down when traffic elevates to to LKML levels, but we
are not even close to that (yet).

..Ch:W..

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

Re: [yocto] Yocto Project Status WW04'20

[Josef Holzmayr]

Howdy!

On Sun, Feb 02, 2020 at 03:09:07PM +0100, Alexander Kanavin wrote:
> Why separate them? I’d rather have newbies and experts in the same room.

My vote is totally on this too!

Greetz.

> 
> Alex
> 
> > On 2 Feb 2020, at 14.28, Adrian Bunk <bunk@stusta.de> wrote:
> > 
> >> On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
> >> ...
> >> *    We have created a "documentation" list and a "licensing" list on the
> >> yocto project mailing list infrastructure. We believe these topics would
> >> benefit from dedicated discussions, the people involved usually aren't
> >> interested in bulk email as would be found on other lists. The new lists can
> >> be found at:  <https://lists.yoctoproject.org/g/licensing/join>
> >> https://lists.yoctoproject.org/g/licensing/join and
> >> <https://lists.yoctoproject.org/g/docs/join>
> >> https://lists.yoctoproject.org/g/docs/join 
> >> ...
> > 
> > Would it be possible to also create a yocto-devel or yocto-core
> > mailing list for discussing development of Yocto?
> > 
> > Currently the yocto list is a mixture of core development list and forum 
> > for newbie user questions, with no easy way to have them separate.
> > 
> > Thanks
> > Adrian
> > 

> 


-- 
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548 

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

Re: [yocto] Yocto Project Status WW04'20

[akuster]

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



On 2/2/20 10:18 AM, Philip Balister wrote:
> On 2/2/20 2:28 PM, Adrian Bunk wrote:
>> On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
>>> ...
>>> *	We have created a "documentation" list and a "licensing" list on the
>>> yocto project mailing list infrastructure. We believe these topics would
>>> benefit from dedicated discussions, the people involved usually aren't
>>> interested in bulk email as would be found on other lists. The new lists can
>>> be found at:  <https://lists.yoctoproject.org/g/licensing/join>
>>> https://lists.yoctoproject.org/g/licensing/join and
>>> <https://lists.yoctoproject.org/g/docs/join>
>>> https://lists.yoctoproject.org/g/docs/join 
>>> ...
>> Would it be possible to also create a yocto-devel or yocto-core
>> mailing list for discussing development of Yocto?
>>
>> Currently the yocto list is a mixture of core development list and forum 
>> for newbie user questions, with no easy way to have them separate.
> We have openembedded-architecture for this.
>
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture

Also openembedded-core
>
> Philip
>
>> Thanks
>> Adrian
>>
>>
>>
>>
>>
>> 


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

Re: [yocto] Yocto Project Status WW04'20

[Denys Dmytriyenko]

On Mon, Feb 03, 2020 at 08:16:47AM -0800, akuster wrote:
> 
> 
> On 2/2/20 10:18 AM, Philip Balister wrote:
> > On 2/2/20 2:28 PM, Adrian Bunk wrote:
> >> On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
> >>> ...
> >>> *	We have created a "documentation" list and a "licensing" list on the
> >>> yocto project mailing list infrastructure. We believe these topics would
> >>> benefit from dedicated discussions, the people involved usually aren't
> >>> interested in bulk email as would be found on other lists. The new lists can
> >>> be found at:  <https://lists.yoctoproject.org/g/licensing/join>
> >>> https://lists.yoctoproject.org/g/licensing/join and
> >>> <https://lists.yoctoproject.org/g/docs/join>
> >>> https://lists.yoctoproject.org/g/docs/join 
> >>> ...
> >> Would it be possible to also create a yocto-devel or yocto-core
> >> mailing list for discussing development of Yocto?
> >>
> >> Currently the yocto list is a mixture of core development list and forum 
> >> for newbie user questions, with no easy way to have them separate.
> > We have openembedded-architecture for this.
> >
> > http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
> 
> Also openembedded-core

Also openembedded-devel

> > Philip
> >
> >> Thanks
> >> Adrian
> >>
> >>
> >>
> >>
> >>
> >> 
> 

> 

Re: Yocto Project Status WW04'20

[DUDZIAK Krzysztof]

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

Sorry for be that late. Just for fellows who in future look answers to above question (like me today).
I really like Philips feedback, thanks for that:
https://lists.openembedded.org/g/openembedded-architecture/message/1194

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