Skip to contentSkip to conversation

Yocto Project Status WW04'20

DISCUSSION [email protected] 10 participants 11 messages Jan 28, 2020 – Mar 16, 2021

lore
Share & tools
lore
#0 lore raw

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: [email protected]
<mailto:[email protected]>

#1 lore raw
Quoted 10 lines · Stephen Jolley

...
* 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

#2 lore raw

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

Alex

Quoted 23 lines · Adrian Bunk
Quoted 12 lines · Stephen Jolley

...
* 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

#5 lore raw
In reply to Adrian Bunk
Quoted 2 lines · Adrian Bunk

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

#6 lore raw
Quoted 5 lines · Ross Burton
Quoted 2 lines · Adrian Bunk

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.

Quoted 1 line

Ross

cu
Adrian

#7 lore raw
In reply to Adrian Bunk
Quoted 12 lines · Adrian Bunk
Quoted 10 lines · Stephen Jolley

...
* 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
...

Quoted 5 lines

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

Quoted 7 lines

Thanks
Adrian

#3 lore raw
In reply to Alexander Kanavin
Quoted 2 lines · Alexander Kanavin

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..

#4 lore raw
In reply to Alexander Kanavin

Howdy!

Quoted 1 line · Alexander Kanavin

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

My vote is totally on this too!

Greetz.

Quoted 28 lines

Alex

Quoted 23 lines · Adrian Bunk
Quoted 12 lines · Stephen Jolley

...
* 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

Signature · 20 lines
———————————————
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
#8 lore raw
In reply to Philip Balister
Quoted 12 lines · Philip Balister
Quoted 11 lines · Adrian Bunk
Quoted 10 lines · Stephen Jolley

...
* 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
...

Quoted 8 lines
Quoted 5 lines

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

Quoted 11 lines

Philip

Quoted 8 lines

Thanks
Adrian

#9 lore raw
Quoted 18 lines · akuster
Quoted 15 lines · Philip Balister
Quoted 14 lines · Adrian Bunk
Quoted 10 lines · Stephen Jolley

...
* 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?

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

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

Quoted 13 lines
Quoted 10 lines

Philip

Quoted 8 lines

Thanks
Adrian