[yocto] Yocto Project Status WW47'19

[sjolley.yp.pm]

Current Dev Position: YP 3.1 M1 

Next Deadline: YP 3.1 M1 build Dec. 2, 2019

 

Next Team Meetings:

*   Bug Triage meeting Thursday Nov. 21st at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday Dec. 3rd at 8am PDT (
 https://zoom.us/j/990892712)
*   Weekly Engineering Sync Tuesday Nov. 19th at 8am PDT (
 https://zoom.us/j/990892712)
*   Twitch - Next event is Tuesday Dec. 10th at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   YP 2.7.2 is under review by the TSC and likely to be released.
*   Tests were made on making reproducibility the default for poky.
There were several issues found for which bugs were filed:

*   A double free issue in opkg (Alejandro looking into, thanks)
*   devtool failures (Paul sent a fix, thanks)
*   recipetool failures (Richard sent a fix)

*   Tests were made on making the hashserver default for poky. There
were also several issues found and RP is trying to understand and work
through those. At least one critical issue has been identified and due to be
tested.
*   The SWAT team no longer has enough people on it to make it
sustainable and has therefore been disbanded. This means build owners need
to triage their own build failures. Richard will be responsible for failures
in the scheduled master builds.
*   Intermittent build failures continue to hamper builds, particularly
combined with the above issues and as few people are available to attempt to
debug and resolve them.
*   The TSC is working on LTS plans, productive discussions have been
had and a new policy on handling this and stable releases should be
available in the next couple of weeks.
*   We are continuing to collect ideas for YP 3.1 in this document:

https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjn
ABc/edit?usp=sharing
*   If anyone has any status items for the project they'd like to add to
the weekly reports, please email Richard and Stephen.

 

Proposed YP 3.1 Milestone Dates:

*   YP 3.1 M1 Proposed build date 12/2/2019
*   YP 3.1 M1 Proposed release date 12/13/2019
*   YP 3.1 M2 Proposed build date 1/20/2020
*   YP 3.1 M2 Proposed release date 1/31/2020
*   YP 3.1 M3 Proposed build date 2/24/2020
*   YP 3.1 M3 Proposed release date 3/6/2020
*   YP 3.1 M4 Proposed build date  3/30/2020
*   YP 3.1 M4 Proposed release date  4/24/2020

 

Planned upcoming dot releases:

*   YP 2.7.2 Should release this week.
*   YP 3.0.1 Proposed build date  11/25/2019
*   YP 3.0.1 Proposed release date 12/06/2019
*   YP 2.7.3 Proposed build date  2/10/20
*   YP 2.7.3 Proposed release date 2/21/20
*   YP 3.0.2 Proposed build date  2/3/20
*   YP 3.0.2 Proposed release date 2/14/20

 

Tracking Metrics:

*   WDD 2533 (last week 2508) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1461 (last week 1445)
*   Patches in the Pending State: 579 (40%) [last week 579 (40%)]

 

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

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

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW46'19

[sjolley.yp.pm]

Current Dev Position: YP 3.1 M1 

Next Deadline: YP 3.1 M1 build Dec. 2, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Anuj 
*   SWAT team rotation: Anuj -> Chen on Nov. 15, 2019
*   SWAT team rotation: Chen > Paul on Nov. 22, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

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

 

Key Status/Updates:

*   YP 2.7.2 is still undergoing QA
*   There were some key fixes for pseudo related issues which mean it
continues to work with modern distros like Fedora 31.
*   Patches have continued to merge and master is staying roughly
current with the pending patch queue but there continue to be recurring
build failures that are not being addressed.
*   The YP TSC worked on and shared a proposal on how an LTS release
could work which is available at:

https://docs.google.com/document/d/1AwAFDf52f_FoXksbHEVUMlu4hpcI0JMGVG-Kj_sU
kyc/ . There has been much discussion about this, patience would be
appreciated as the TSC and governing board work through this to come up with
plans on how we proceed.
*   We are continuing to collect ideas for YP 3.1 in this document:

https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjn
ABc/edit?usp=sharing
*   If anyone has any status items for the project they'd like to add to
the weekly reports, please email Richard and Stephen.

 

Proposed YP 3.1 Milestone Dates:

*   YP 3.1 M1 Proposed build date 12/2/2019
*   YP 3.1 M1 Proposed release date 12/13/2019
*   YP 3.1 M2 Proposed build date 1/20/2020
*   YP 3.1 M2 Proposed release date 1/31/2020
*   YP 3.1 M3 Proposed build date 2/24/2020
*   YP 3.1 M3 Proposed release date 3/6/2020
*   YP 3.1 M4 Proposed build date  3/30/2020
*   YP 3.1 M4 Proposed release date  4/24/2020

 

Planned upcoming dot releases:

*   YP 3.0.1 has patches being queued in poky-contrib
*   YP 2.7.2 (Warrior) is in QA.

 

Tracking Metrics:

*   WDD 2508 (last week 2518) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1445 (last week 1446)
*   Patches in the Pending State: 579 (40%) [last week 579 (40%)]

 

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

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

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW37'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M4 Feature Freeze

Next Deadline: YP 3.0 Final Release 25th Oct

 

SWAT Team Rotation:

*   SWAT lead is currently: Paul
*   SWAT team rotation: Paul -> Ross on Sept. 13, 2019
*   SWAT team rotation: Ross -> Amanda on Sept. 20, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday Sept 12th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday Oct. 1st at 8am PDT (
 https://zoom.us/j/990892712)
*   Weekly Engineering Sync Tuesday Sept. 10th at 8am PDT (
 https://zoom.us/j/990892712)
*   Twitch - Next event is Tuesday Sept. 10th at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   We're now in feature freeze for 3.0 and working on bug fixing for
final release
*   We have not built M3 yet as some work still remains for us to be
feature complete and ready for QA. This puts us behind schedule but the plan
is to complete the key features we've planned rather than adhere strictly to
dates. We hope to make up time during M4 by having M3 at high quality and
take advantage of our automation.
*   RP is away for the rest of the week which means M3 progress will be
limited this week, Ross will queue patches.
*   Key 3.0 changes have now merged:

*   5.2 linux-libc-kernel-headers
*   5.2 kernel recipes by default for all reference BSPs
*   Removal of LSB and poky-lsb and replacement with alt config testing
*   systemd by default for poky-altcfg
*   Patches have significantly reduced the dependency on python2
*   Reproducible builds are now being tested for core-image-minimal
*   Automated toolchain testsuite tests (binutils, gcc, glibc)

*   Key blocking issues for M3 that have been fixed:

*   Systemtap issues with 5.2 were debugged and patches sent/merged
upstream
*   5.2 dmesg on qemuarm64 fixed
*   qemumips hang when using highmem root caused and worked around (for
now)
*   mdadm ptest timeout worked around
*   quilt and libevent ptest regressions from M2 resolved

*   Remaining issues blocking M3:

*   systemd boot failure on qemumips
*   strace ptest timeout
*   Hash equivalence performance problems (RP has a simple idea to
~double speed)
*   Hash equivalence bugs
*   Toolchain testsuite relocation bugs (Nathan working on it)

*   Hash Equivalency status:

*   Ideas about removing some dependency information from the hashes to
allow faster bulk queries aren't viable so the current codebase approach is
correct
*   we need to rework the client/server communication to scale to the
autobuilder
*   there are some bugs in the code the autobuilder continues to expose
*   we have cases where its not 100% clear what the correct behaviour
should be
*   test cases are proving to be problematic to write in a maintainable
way

*   Documentation - Due to illness Scott is unavailable for the next
month or two so doc patches will be handled by Richard or Ross in the short
term. We'll likely limit them to correctness issues and defer any
substantial new text. If anyone has availability and skills to work on the
manuals please talk to us. We're aware there is a patch backlog.
*   If anyone has any status items for the project they'd like to add to
the weekly reports, please email Richard+Stephen.

 

Planned Releases for YP 3.0 {2.8}:

*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept - this will be YP 3.0.
*   YP 3.0 {2.8 (M4)} Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.2 (Warrior) is planned for after YP 3.0 release.
*   YP 2.6.4 (Thud) is planned for after YP 2.7.2  release.

 

Tracking Metrics:

*   WDD 2424 (last week 2413) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1417 (last week 1470)
*   Patches in the Pending State: 582 (41%) [last week 611 (42%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

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

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

 

The Status reports are now stored on the wiki at:

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 291
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW34'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M3

Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Chen
*   SWAT team rotation: Chen -> Anuj on Aug. 23, 2019
*   SWAT team rotation: Anuj -> Armin on Aug. 30, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday August 22nd at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday Sept. 3rd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday Sept. 10th at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   YP 2.6.3 has been released.
*   This release which was 2.8 will now become 3.0.
*   The sstate hash equivalency continues to have challenges:

*   performance of the hash server is not able to scale to the
autibuilder's load
*   there are some bugs in the code the autobuilder continues to expose
*   we have cases where its not 100% clear what the correct behaviour
should be
*   test cases are proving to be problematic to write in a maintainable
way

*   On a more positive note, some of the key performance issues were
identified and fixed so performance doesn't regress for usage without hash
equivalence. Several corruption issues and other key fixes to runqueue also
merged.
*   Jason Wessel finally tracked down our mystery glibc-locale bug,
which was not a pseudo issue. Thanks and kudos to Jason!
*   General patch merging is currently delayed along with patch feedback
due to the hash equivalence issues and lack of bandwidth to progress
everything at once.
*   We still need to make a decision on systemd or sysvinit defaults as
the init system.
*   We are a week away from the 3.0 feature freeze.

 

Planned Releases for YP 3.0 {2.8}:

*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept - this will be YP 3.0.
*   YP 3.0 {2.8 (M4)} Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.2 (Warrior) is planned for after YP 3.0 release.
*   YP 2.6.4 (Thud) is planned for after YP 2.7.2  release.

 

Tracking Metrics:

*   WDD 2495 (last week 2482) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1491 (last week 1489)
*   Patches in the Pending State: 616 (41%) [last week 617 (41%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

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

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

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 297
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com)
an e-mail with the bug number you would like and I will assign it to you
(please make sure you have a Bugzilla account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW33'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M3

Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Amanda
*   SWAT team rotation: Amanda -> Chen on Aug. 16, 2019
*   SWAT team rotation: Chen -> Armin on Aug. 23, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday August 15th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday Sept. 3rd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday Sept. 3rd at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   YP 2.6.3 is out of QA and being readied for release.
*   This release which was 2.8 will now become 3.0.
*   The sstate has equivalency work has run into some challenges:

*   performance of the hash server is not able to scale to the
autibuilder's load
*   performance of runqueue has regressed even when not using the hash
equivalency code
*   bugfixes in master-next regress performance even further
*   there are bugs being triggered by the has equivalency code that need
investigation and resolution (along with test cases creating).

These issues are being worked on but we need to ensure correctness of the
new code first before the performance can be fixed

*   There were updates so some key components for bug fixes this week,
in particular pseudo.
*   General patch merging is happening and the queue is mostly clear and
flowing but it isn't happening as frequently as usual due to the hash
equivalency work.

 

Planned Releases for YP 3.0 {2.8}:

*   M2 is released.
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept - this will be YP 3.0.
*   YP 3.0 {2.8 (M4)} Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.2 (Warrior) is planned for after YP 3.0 release.
*   YP 2.6.3 (Thud) is out of QA and being readied for release.
*   YP 2.6.4 (Thud) is planned for after YP 2.7.2  release.

 

Tracking Metrics:

*   WDD 2482 (last week 2481) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1489 (last week 1496)
*   Patches in the Pending State: 617 (41%) [last week 615 (41%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

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

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

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 297
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW32'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M3

Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Ross
*   SWAT team rotation: Ross -> Amanda on Aug. 9, 2019
*   SWAT team rotation: Amanda -> Chen on Aug. 16, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday August 8th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday August 6th at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday August 6th at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   YP 2.8 M2 is due for release this week
*   YP 2.6.3 is in QA
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   This release which was 2.8 will now become 3.0
*   The project is working on some mentor and mentee opportunities.
Please see the separate email from Nicolas on the yocto list about this.
*   Patches to bitbake to enable the task scheduler to react to
"equivalent" build output have merged. There is more information about this
major change in a separate email:

 

http://lists.openembedded.org/pipermail/openembedded-core/2019-August/285300
.html

It is hoped this change should improve productivity and reduce rebuilds.

*   In making some of these changes, there were some API changes in
bitbake, notably the removal of the bb.build.FuncFailed exception, the
signature generator task representation changed and there were some siggen
function API changes.
*   libx11-diet was removed as its not really appropriate on a modern
locale aware system.

 

Planned Releases for YP 3.0 {2.8}:

*   M2 is out of QA and being reviewed.
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept - this will be YP 3.0.
*   YP 3.0 {2.8 (M4)} Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.2 (Warrior) is planned for after 2.8 M2 release.
*   YP 2.6.3 (Thud) is iin QA.

 

Tracking Metrics:

*   WDD 2481 (last week 2466) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1496 (last week 1498)
*   Patches in the Pending State: 615 (41%) [last week 619 (41%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

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

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

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PST)

[sjolley.yp.pm]

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at
8am PST tomorrow. (8/6)  

 

Yocto Project Technical Team Meeting: We encourage people attending the
meeting to logon and announce themselves on the Yocto Project IRC chancel
during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

WhenMonthly from 8am to 8:30am on the first Tuesday Pacific Time

Where   Zoom Meeting: https://zoom.us/j/990892712 

 

I will be tracking the minutes at:
https://docs.google.com/document/d/1Y5IIuE-z0Ykdl-DwuzUJh52flOZuhN_TSAfw2tdU
9pg/edit?ts=5c06b22d  Please request access if you want to assist in editing
them.  The world should have view access. 

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 297
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW31'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M3

Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Paul 
*   SWAT team rotation: Paul -> Ross on Aug. 2, 2019
*   SWAT team rotation: Ross -> Amanda on Aug. 9, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday August 1st at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday August 6th at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday August 6th at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   YP 2.8 M2 rc1 is in QA which is due to complete on Wednesday
*   YP 2.6.3 will build to go into QA on Wednesday
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   The Yocto Project TSC has determined how it plans to operate and put
the details into the appropriate wiki page:

https://wiki.yoctoproject.org/wiki/TSC. It is intended as a decision making
body of last resort, if there are issues people wish it to address, please
raise them with one of its members.
*   After discussion in various places its been agreed that the next
project release will be "3.0", to replace "2.8". The 2.8 placeholder may
continue to be used, particularly in the bugzilla. There are many good
reasons to bump the version, the most recent being the runqueue changes
allowing build optimizations based upon output equivalence (see below) but
also including the new project governance, the autobuilder, improved test
coverage any many other things.
*   There are patches available which enable runqueue optimisations
based on output comparisons of tasks. This removes the need to run later
tasks if the output is unchanged and is based upon the previous hash
equivalence server work. This feature should be a significant win for the
users and is now working to a level where we'll likely make this a key
feature of the next release. These patches are being tested in master-next
at present.
*   There are also changes in -next which are being considered which
change several bitbake APIs around runqueue. The feeling is now may be the
best time to clean up several interfaces. If there are other API fixes
people want to see, now is a good time to mention them.
*   The project is working on some mentor and mentee opportunities.
Please see the separate email from Nicolas on the yocto list about this.

 

Planned Releases for YP 2.8:

*   M2 is in QA
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.2 (Warrior) is planned for after 2.8 M2  release.
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M3.

 

Tracking Metrics:

*   WDD 2466 (last week 2483) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1498 (last week 1499)
*   Patches in the Pending State: 619 (41%) [last week 623 (42%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 300
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW30'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Anuj 
*   SWAT team rotation: Anuj -> Paul on July 26, 2019
*   SWAT team rotation: Paul -> Ross on Aug. 2, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday July 25th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday August 6th at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday August 6th at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   2.7.1 was released
*   2.6.3 has patches pending review and then will be built
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   There are ongoing discussions on a few key topics which are
summarized here for convenience. Please contribute if you have an interest
in these areas:

*   Running the testsuites for glibc/binutils/gcc
*   Moving lsb to its own layer
*   Removing poky-lsb in favour of some configuration fragments
*   Reproducibility
*   Minimizing python2 dependencies
*   Configuration of init systems

*   Changing poky's init system default to systemd is running into a
large number of testing failures on the autobuilder which puts that change
at risk.
*   The autobuilder performance problem when stopping builds has been
tracked down and fixed. The controller was also upgraded for some
performance improvements (thanks Michael).
*   There are patches available which enable runqueue optimisations
based on output comparisons of tasks. This removes the need to run later
tasks if the output is unchanged and is based upon the previous hash
equivalence server work. This feature should be a significant win for the
users and is now working to a level where we'll likely make this a key
feature of the next release.

 

Planned Releases for YP 2.8:

*   M2 Cutoff 14th July
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.1 (Warrior) is released.
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2.

 

Tracking Metrics:

*   WDD 2483 (last week 2498) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1499 (last week 1502)
*   Patches in the Pending State: 623 (42%) [last week 630 (42%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 304
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com)
an e-mail with the bug number you would like and I will assign it to you
(please make sure you have a Bugzilla account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW29'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Amanda
*   SWAT team rotation: Amanda ->  Anuj on July 19, 2019
*   SWAT team rotation: Anuj -> Paul on July 26, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday July 18th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday August 6th at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday August 13th at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   2.7.1 is cleared for release and will be announced shortly
*   2.6.3 has two remaining issues before it can be built
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   General patch backlog and merging is running back to normal
*   Our numbers of patches in the metadata has been slowly decreasing
and I wanted to mention how much we appreciate anyone doing cleanup of
old/stale data. Over time it is making a significant difference!
*   There are ongoing discussions on a few key topics which are
summarised here for convenience. Please contribute if you have an interest
in these areas:

*   Running the testsuites for glibc/binutils/gcc
*   Moving lsb to its own layer
*   Removing poky-lsb in favour of some configuration fragments
*   Reproducibility
*   Minimising python2 dependencies
*   Configuration of init systems

*   Bitbake changes which change the way runqueue works quite radically
have merged. If people see errors with setscene or normal task execution
people do report them.
*   Runqueue change to optimise sstate usage/sharing in multiconfig
builds merged. Please report if its not working where you'd expect it to.

 

Planned Releases for YP 2.8:

*   M2 Cutoff 14th July
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.1 (Warrior) is ready for release.
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2

 

Tracking Metrics:

*   WDD 2498 (last week 2496) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1502 (last week 1506)
*   Patches in the Pending State: 630 (42%) [last week 634 (42%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 303
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW28'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Armin
*   SWAT team rotation: Armin -> Amanda on July 12, 2019
*   SWAT team rotation: Amanda ->  Anuj on July 19, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday July 11th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday August 6th at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday 9th July at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   2.7.1 has a ptest issue which is being investigated before the
release decision.
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   No progress on autobuilder NFS glitches or UI performance. The pigz
issue looks like an opensuse specific pthreads problem at this point (

https://github.com/madler/pigz/issues/68)
*   Richard has been working on runqueue changes to run setscene and
normal tasks in parallel. The patches are in master-next for regression
testing at present. Ultimately these would allow sstate hash equivalency to
be acted upon mid build. The changes aren't as invasive as first feared
which should reduce the changes and scope of regressions.
*   The usual patch queue handling is slower due to the runqueue
distraction.
*   There is a discussion on the mailing list about reproducibility in
the project, please respond there if you have opinions.
*   There was an interesting patch on the mailing list to enable some
big test suites from the toolchain components (binutils/gcc/glibc). This is
great to see and feedback is encouraged, it would make a great addition
alongside ptest and the other tests we have automated.

 

Planned Releases for YP 2.8:

*   M2 Cutoff 14th July
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.1 (Warrior) is out of QA.
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2

 

Tracking Metrics:

*   WDD 2496 (last week 2484) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1506 (last week 1505)
*   Patches in the Pending State: 634 (42%) [last week 638 (42%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 304
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW27'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Chen
*   SWAT team rotation: Chen -> Armin on July 5, 2019
*   SWAT team rotation: Armin -> Amanda on July 12, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday July 11th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday July 2nd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday 9th July at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   2.7.1 rc1 is in QA
*   Emails about the mailing list transition are being prepared and we
now have a plan to move forward. The list addresses will need to change,
archive URLs should remain available.
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   There is a discussion on the mailing list about reproducibility in
the project, please respond there if you have opinions.
*   The autobuilder is continuing to see NFS glitches, we know how to
unblock them but aren't sure of the cause at present.
*   There is a performance issue with the autobuilder UI we've been
debugging where build cancellation in particular locks the controller up for
several minutes. Switching the database backend from sqlite to mysql after
advice from upstream unfortunately didn't help. The switch has helped some
other UI responsiveness though.
*   There is a recurring pigz threads problem occuring in builds. There
is a patch in -next to try and get more debug, the problem has never
occurred with the patch applied. Its unclear if pigz 2.4 has a fix as the
failures only occurred with 2.3.3 (from the host). There are no obvious
differences in the area of the code where the errors occurs between the
versions.
*   There has been a significant change in behaviour in do_package and
handling of pkgdata which should result in better deterministic build and
improve build performance. 
*   We have hopefully now tracked down and resolved the various syslog
restart races and automated testing failures

 

Planned Releases for YP 2.8:

*   M2 Cutoff 14th July
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.1 (Warrior) has been submitted to QA.
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2

 

Tracking Metrics:

*   WDD 2484 (last week 2482) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1505 (last week 1509)
*   Patches in the Pending State: 638 (42%) [last week 638 (42%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 282
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Meetings next week.

[sjolley.yp.pm]

All,

 

Due to the 4th of July holiday next week.  Some meetings will be changed.

 

Triage will be canceled on the 4th..  Next Bug Triage meeting Thursday will
be July 11th at 7:30am PDT (https://zoom.us/j/454367603)

Monthly Project Meeting will still be Tuesday July 2nd at 8am PDT (
 https://zoom.us/j/990892712) 

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW26'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Ross
*   SWAT team rotation: Ross -> Amanda on June 28, 2019
*   SWAT team rotation: Amanda -> Chen on July, 5, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday June 27th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday July 2nd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday 9th July at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   2.8 M1 has been released.
*   Mailing lists issues are continuing to be worked on as a top
priority.
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   Several key reproducibility fixes have merged, thanks Joshua!
*   The autobuilder has suffered stability issues with its NFS setup,
seemingly related to the increased load from the new servers. We're
monitoring changes, hoping they fix the issue.
*   We had significant problems with the versioning of libcrypt in
recent distros which resulted in the need for a new uninative release. This
fixes autobuilder builds.

 

Planned Releases for YP 2.8:

*   M2 Cutoff 14th July
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.1 (Warrior) is planned for build imminently now that 2.8 M1
is done but is pending the new uninative changes.
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2

 

Tracking Metrics:

*   WDD 2482 (last week 2479) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1509 (last week 1511)
*   Patches in the Pending State: 638 (42%) [last week 641 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 283
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW25'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Paul
*   SWAT team rotation: Paul -> Ross on June 21, 2019
*   SWAT team rotation: Ross -> Amanda on June 28, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday June 20th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday July 2nd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday 9th July at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   2.8 M1 has been through QA and is waiting on responses from YP TSC
members on release readiness. It had more issues that would be ideal but
most were relatively minor and are being worked upon, several with known
causes now with fixes in master. As such its likely to be released.
*   Stephen is recovering from the accident and will now respond to
emails. We're pleased to have him back and wish him a continued speedy
recovery!
*   Mailing lists are proving to be a tricky subject. Some people are
having trouble with emails not making it to the lists which we recognise is
a serious issue. Equally, our groups.io plan isn't proving workable without
major user visible change due to the current domain structure we have. It is
being worked on as a priority to find a way forward.
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   We're grateful to Sandy, WindRiver and Michael for helping get
patchtest back into operation. Its tests are looking like they could do with
a little improvement but it is catching some issues and great to see
progress with it again.
*   During M2 Richard plans to look into our options for changing
runqueue to better support more advanced sstate usage. This may have an
impact on how quickly patches merge as the work there is involved and needs
focus.
*   We'd like to remind people that where test suites exist, we'd
appreciate it if people would run them before they send patches, e.g.
"oe-selftest -r devtool" or "oe-selftest -r wic".

 

Planned Releases for YP 2.8:

*   M1 is built and out of QA
*   M2 Cutoff 14th July
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.1 (Warrior) is planned for build imminently now that 2.8 M1
is done
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2

 

Tracking Metrics:

*   WDD 2479 (last week 2478) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1511 (last week 1507)
*   Patches in the Pending State: 641 (43%) [last week 641 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 280
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW14'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M4 (New feature Freeze has begun.)

Next Deadline: YP 2.7 M3 Release Target was Mar. 8, 2019 and it should
release today!

 

SWAT Team Rotation:

*   SWAT lead is currently: Amanda 
*   SWAT team rotation: Amanda -> Chen on Apr. 12, 2019
*   SWAT team rotation: Chen -> Armin Apr. 19, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   YP 2.8 Planning meeting Tuesday April 16nd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Bug Triage meeting Thursday April 11th at 7:30am PDT (
 https://zoom.us/j/454367603)

 

Key Status/Updates:

*   YP 2.7 M3 rc1 will be released today. The YP 2.7 M3 rc1 report is
summarized at

https://lists.yoctoproject.org/pipermail/yocto/2019-April/044667.html and
the results are at

https://autobuilder.yocto.io/pub/releases/yocto-2.7_M3.rc1/testresults/.
*   YP 2.5.3 and YP 2.6.2 stable releases were built and have been
submitted to QA
*   YP 2.6.2 is currently going through the QA process with YP 2.5.3
queued behind it. 
*   Process issues in the way ptest was being processed by QA have been
discovered which mean the previous ptest results are not comparable with the
new QA process. For consistency going forward we will be using the new QA
process as the definitive results and will be comparing for regressions
based upon these.
*   The "warrior" branches for 2.7 have been created and the metadata
updated, patches are being slowed in line with release stablisation with
increasingly critical fixes only.
*   The remaining things which are planned for YP 2.7 M4 before we have
the final 2.7 rc1 build are:

*   Upgrading -tiny to the 5.0 linux-yocto kernel (currently 4.18)
*   Removal of the 4.18 kernel
*   Fixing the python3 ptest timeout and result status issues
*   Fixing some of the util-linux ptest failures
*   Potentially integrating a key and long time puzzling pseudo issue
*   Integrating qemumips shutdown issues identified in the kernel
*   Continue to investigate python3 testsuite hang on 5.0+ kernels
(trying to get help upstream)

*   Worrying things which we don't have good plans for currently (mainly
lack of people to help with):

*   Intermittent autobuilder failures (fork running out of resources -
which resources?, oe-selftest intermittent issues, gpg signing resource
problems, occasional PR server failure and more)
*   Build-appliance testing issues (show up on each QA report across
multiple releases)
*   40% valgrind ptest failures
*   Known bitbake memory resident bugs
*   Other ptest failures

*   The 2.8 planning discussions are starting and there is a google doc
summarising the discussions so far:

https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJG
XbU/

If people are planning to work on specific things in 2.8 please let us know
so we can incorporate this into our plans. If you're interested in working
on anything in the document, please also let us know or talk with us in one
of the planning meetings.

 

Planned Releases for YP 2.7:

*   YP 2.7 M4 Cutoff was Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) is in QA.
*   YP 2.6.2 (Thud) is in QA.

 

Tracking Metrics:

*   WDD 2471 (last week 2442) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1553 (last week 1542
*   Patches in the Pending State: 655 (42%) [last week 656 (42%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 281 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.9', "2.99" and "Future", the more pressing/urgent issues being in
"2.7" and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] YPTM minutes

[sjolley.yp.pm]

Attendees: Stephen, Joshua, Alex, Jon, Randy, Richard, Michael, David,
Bruce, Shawn, Jaewon, Manjukum, Tracey, Chris, Tim, Chandana, Aitronics,
Paul, Tomas, Ross, 

 

YP 2.7 M3 rc1 is out of QA.  The YP 2.7 M3 rc1 report is summarized at

https://lists.yoctoproject.org/pipermail/yocto/2019-April/044667.html and
the results are at

https://autobuilder.yocto.io/pub/releases/yocto-2.7_M3.rc1/testresults/.

YP 2.5.3 and YP 2.6.2 stable releases were built and submitted to QA last
week.

We discuss the YP 2.8 Ideas document at:

https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJG
XbU/ - If you wish to edit the file, send a request. 

 

AR: Tim - Add to planning document details about installable images via WIC.


AR: Stephen - Cancel 4/16 engineering meeting and add 4/16 Planning meeting.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW14'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M4 (New feature Freeze has begun.)

Next Deadline: YP 2.7 M3 Release Target was Mar. 8, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Ross
*   SWAT team rotation: Ross -> Amanda on Apr. 5, 2019
*   SWAT team rotation: Amanda -> Chen on Apr. 12, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   YP 2.8 Planning meeting Tuesday April 2nd at 8am PDT (
 https://zoom.us/j/990892712) or see the invite
on the mailing list at: (

https://lists.yoctoproject.org/pipermail/yocto/2019-April/044654.html) 
*   Bug Triage meeting Thursday April 4th at 7:30am PDT (
 https://zoom.us/j/454367603)

 

Key Status/Updates:

*   The QA report for M3 rc1 is available. This is the first time we've
used the new QA process so we're still understanding how the new format for
the data works out. There are some issues but right now we believe we'll aim
to fix these before the final release build and proceed to that with the
first build of M4 aiming for next week.
*   The YP 2.7 M3 rc1 report is summarized at

https://lists.yoctoproject.org/pipermail/yocto/2019-April/044667.html and
the results are at

https://autobuilder.yocto.io/pub/releases/yocto-2.7_M3.rc1/testresults/.
*   2.5.3 and 2.6.2 stable releases were built and submitted to QA last
week.
*   The "warrior" branches for 2.7 have been created and the metadata
updated. This will have a ripple effect across the layers as they update to
match this. This process is important as it allows layers to indicate which
versions of the project they are compatible with.
*   The 2.8 planning discussions are starting and there is a google doc
summarising the discussions so far:

https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJG
XbU/

If people are planning to work on specific things in 2.8 please let us know
so we can incorporate this into our plans. If you're interested in working
on anything in the document, please also let us know or talk with us in one
of the planning meetings.

 

Planned Releases for YP 2.7:

*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) is in QA.
*   YP 2.6.2 (Thud) is in QA.

 

Tracking Metrics:

*   WDD 2442 (last week 2418) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1542 (last week 1538)
*   Patches in the Pending State: 654 (42%) [last week 656 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PST)

[sjolley.yp.pm]

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at
8am PST tomorrow. (April 2nd)  We will start planning for YP 2.8 

 

Yocto Project Technical Team Meeting: We encourage people attending the
meeting to logon and announce themselves on the Yocto Project IRC chancel
during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

WhenMonthly from 8am to 9am on the first Tuesday Pacific Time

Where   Zoom Meeting: https://zoom.us/j/990892712 

 

I will be tracking the minutes at:
https://docs.google.com/document/d/1Y5IIuE-z0Ykdl-DwuzUJh52flOZuhN_TSAfw2tdU
9pg/edit?ts=5c06b22d  Please request access if you want to assist in editing
them.  The world should have view access. 

 

The planning document for YP 2.8 is at:
https://drive.google.com/open?id=1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXb
U   If you want to add ideas or edit it, just request it and I will grant
you edit access.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 287 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.9', "2.99" and "Future", the more pressing/urgent issues being in
"2.7" and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW13'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M4 (New feature Freeze has begun.)

Next Deadline: YP 2.7 M3 Release Target was Mar. 8, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Paul 
*   SWAT team rotation: Paul -> Ross on Mar. 30, 2019
*   SWAT team rotation: Ross -> Amanda on Apr. 5, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*   M3 has been built and is currently in QA
*   There are a small number of upgrades which merged after M3 as it was
felt better to be up to date in these cases along with various other fixes.
The project is now very much in feature freeze and bug fixing working toward
the final release though.
*   The OpenEmbedded election for its TSC members is now in the
nomination phase.
*   For the stable releases, the autobuilder-helper changes have now
merged and the resulttool patches are also backported on the relevant -next
branches. This means we're ready to build both 2.5.3 and 2.6.2.

 

Planned Releases for YP 2.7:

*   YP 2.7 M3 Cutoff was Feb. 25, 2019
*   YP 2.7 M3 Release Target was Mar. 8, 2019
*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) will be targeted for build as soon as it is ready..
*   YP 2.6.2 (Thud) will be targeted after YP 2.5.3 is done.

 

Tracking Metrics:

*   WDD 2418 (last week 2432) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1538 (last week 1526)
*   Patches in the Pending State: 656 (43%) [last week 656 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 296 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.9', "2.99" and "Future", the more pressing/urgent issues being in
"2.7" and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW12'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M3 (New feature Freeze has begun.)

Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Armin 
*   SWAT team rotation: Armin -> Paul on Mar. 23, 2019
*   SWAT team rotation: Paul -> Ross on Mar. 30, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*   M3 has not built yet however most major pieces are in place,
including now, agreement on the new QA process. The delay is partly due to
RP travel with others able to cover being unavailable for other reasons,
combined with infrastructure issues.
*   The remaining questions for M3 are:

*   Public documentation of the new QA process
*   Upgrade for uninative for glibc 2.29
*   Mesa upgrade? (unlikely given failures in testing)

*   The Yocto Project has updated to its new governance model which
includes establishing a Technical Steering Committee (TSC) for Yocto
Project. This is designed to complement  and work alongside the OpenEmbedded
TSC. Three members of the YP TSC are selected by the Yocto Project governing
board and those people are Ross Burton, Khem Raj and Richard Purdie. The
remaining two seats will be elected by OpenEmbedded. It is intended the TSC
will take over the release process, SWAT team, bug triage and feature
planning/development for 2.8.
*   YP 2.5.3 continues to be blocked on autobuilder-helper changes for
the stable branches and the resulttool changes in master to move to the new
QA process.
*   There is discussion on the openembedded-architecture list about
changes to the stable branch patch criteria to bring us more into line with
current industry best practices and thinking.

 

Planned Releases for YP 2.7:

*   YP 2.7 M3 Cutoff was Feb. 25, 2019
*   YP 2.7 M3 Release Target was Mar. 8, 2019
*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*   YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*   YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

 

Tracking Metrics:

*   WDD 2432 (last week 2439) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1526 (last week 1523)
*   Patches in the Pending State: 656 (43%) [last week 657 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 296 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW11'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M3 (New feature Freeze has begun.)

Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Anuj 
*   SWAT team rotation: Anuj -> Armin on Mar. 15, 2019
*   SWAT team rotation: Armin -> Paul on Mar. 23, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*   YP 2.7 M2 rc2 was released on May 5, 2019.
*   We believe we now have all the key components for 2.7M3 in
master-next but have not completed a successful test run with this. In
addition to the list last week, this means M3 will include:

*   5.0 kernel
*   qemuarm transition to armv7
*   Busybox full replacement utils

*   Some invalid source revisions tested in master-next have broken the
autobuilder causing build hangs and failures. With travel and other
distractions, nobody is available to dive in and debug this immediately so
it will block M3.
*   We also want to complete the transition to the new QA process and
test this for M3. Aproov is going to send out details of this imminently, we
believe the main code work is complete and its process/documentation that
remains. We will block on this as we want to use the new QA process for M3
and the final 2.7 release.
*   YP 2.5.3 continues to be blocked on autobuilder-helper changes for
the stable branches and the resulttool changes in master to move to the new
QA process.

 

Planned Releases for YP 2.7:

*   YP 2.7 M3 Cutoff is Feb. 25, 2019
*   YP 2.7 M3 Release Target is Mar. 8, 2019
*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*   YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*   YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

 

Tracking Metrics:

*   WDD 2439 (last week 2436) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1523 (last week 1502)
*   Patches in the Pending State: 657 (43%) [last week 658 (44%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 295 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] YPTM minutes

[sjolley.yp.pm]

Yocto Technical Team Minutes for Mar. 5, 2019.

 

Attendees: Armin, Joshua, Randy, Richard, Joshua, Tim, Stephen, Tracey,
Michael, Alex,

 

YP Status: YP 2.7 M2 rc2 is being released today Mar. 5, 2019.

YP 2.7 M3 has a 4 items still to be resolved before the build.

YP 2.5.3 needs one major item to be resolved before it is built.

Richard discussed the status of M3 and the remaining work to be done, see
the status report.

Richard discussed the status of QA automation, need to backport the changes
to 2.5 and 2.6

Richard discussed the current SWAT status, need more attention and members.

Stephen discussed that next month's Technical meeting we will begin the
planning for YP 2.8.  The link for YP 2.7 Plan is at:

https://docs.google.com/document/d/15jB6nUJU2wrtnu6w07L9RZpNlj6AoxSTPEX5aELt
s1g/edit

Richard discussed the updates from YP Advisory Board, both Comcast upgrading
to Platinum and the new agreed to Governance plan for YP.  This allows the
creation of the YP TSC. (Technical Steering Committee.)

Richard discussed that we can't run vgl without GPU HW in the cluster. Need
to decide if we need GPU cards in any/all servers.

Richard discussed the status of bug 8729.

Armin discussed the changes planned for QA transition.  Need to update
documentation to reflect the changes. 

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW10'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M3 (New feature Freeze has begun.)

Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Ross
*   SWAT team rotation: Chen -> Anuj on Mar. 8, 2019
*   SWAT team rotation: Anuj -> Armin on Mar. 15, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*   YP 2.7 M2 rc2 is being released today Mar. 5, 2019.
*   YP 2.7 M3 has not yet been built but progress has been made in
resolving several issues:

*   bug 13178 "X server and matchbox desktop don't start up properly on
beaglebone" was fixed
*   multiconfig bugs have been fixed and a test case added
*   qemu virgl code and selftests have been added (not enabled as
default)
*   qemu native build was split into user and system components
*   lttng-tools ptest timeout fixed
*   systemd version upgrade
*   ltp recipe version upgrade
*   perl ptest regressions fixed

*   The list of remaining potential items for M3 is:

*   5.0 linux kernel (and libc headers) (Bruce)
*   qemuarm to v7 changes (Jon)
*   Aarch64 build host support finalization (Jon)
*   Busybox 'full' utility replacement (Tom)

*   YP 2.5.3 is nearly ready for building however the autobuilder-helper
changes need to be resolved for the stable branches, as do the resulttool
changes in master to move to the new QA process.

 

Planned Releases for YP 2.7:

*   YP 2.7 M2 Released Mar. 5, 2019
*   YP 2.7 M3 Cutoff is Feb. 25, 2019
*   YP 2.7 M3 Release Target is Mar. 8, 2019
*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*   YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*   YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

 

Tracking Metrics:

*   WDD 2436 (last week 2415) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1502 (last week 1516)
*   Patches in the Pending State: 658 (44%) [last week 660 (44%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PST)

[sjolley.yp.pm]

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at
8am PST tomorrow. (3/5)  

 

Yocto Project Technical Team Meeting: We encourage people attending the
meeting to logon and announce themselves on the Yocto Project IRC chancel
during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

WhenMonthly from 8am to 8:30am on the first Tuesday Pacific Time

Where   Zoom Meeting: https://zoom.us/j/990892712 

 

I will be tracking the minutes at:
https://docs.google.com/document/d/1Y5IIuE-z0Ykdl-DwuzUJh52flOZuhN_TSAfw2tdU
9pg/edit?ts=5c06b22d  Please request access if you want to assist in editing
them.  The world should have view access. 

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 296 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW09'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M3 (New feature Freeze has begun.)

Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Ross
*   SWAT team rotation: Ross -> Chen on Mar. 1, 2019
*   SWAT team rotation: Chen -> Armin on Mar. 8, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*   We have now passed the feature freeze point for 2.7
*   YP 2.7 M2 rc2 is out of QA and being readied for release.  See:

https://wiki.yoctoproject.org/wiki/WW07_-_2019-02-14_-_Full_Test_Cycle_2.7_M
2_RC2 and

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status#Milestone_2_-_T
arget_Feb._1.2C_2019
*   We now have resulttool, buildhistory and build-performance all
working with the autobuilder and will be using this as the primary QA
mechanism going forward. More details can be found here:

 

http://lists.openembedded.org/pipermail/openembedded-architecture/2019-Febru
ary/001591.html

*   There were some serious usability issues found with multiconfig,
those have been fixed in master and thud.
*   Various recipe upgrades made it in, thanks to all who contributed.
Several recipes also converted to meson including glib-2.0 and gdk-pixbuf.
*   We now need to build M3 as we're past feature freeze point for 2.7.
Right now we're aware of the following things which ideally need to be
resolved first:

*   Bug 13178 "X server and matchbox desktop don't start up properly on
beaglebone" needs to be fixed
*   Find the framebuffer problem with qemuarmv7 and switch to that
*   Several ptest issues would be addressed (missing openssl tests, 3
timeouts)
*   Arm build host issues identified and resolved

*   It's unlikely we'll switch to virtgl by default for 2.7 due to lack
of testing from the community although the base patches for this have
merged.

 

Planned Releases for YP 2.7:

*   YP 2.7 M2 rc2 is out of QA.
*   YP 2.7 M2 Release Target was Feb. 1, 2019
*   YP 2.7 M3 Cutoff is Feb. 25, 2019
*   YP 2.7 M3 Release Target is Mar. 8, 2019
*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*   YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*   YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

 

Tracking Metrics:

*   WDD 2415 (last week 2392) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1516 (last week 1527)
*   Patches in the Pending State: 660 (44%) [last week 663 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

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...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 294 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 295 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW08'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M3

Next Deadline: YP 2.7 M3 Cutoff is Feb. 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Amanda
*   SWAT team rotation: Amanda -> Ross on Feb. 22, 2019
*   SWAT team rotation: Ross -> Chen on Mar. 1, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*   YP 2.7 M2 rc2 is in QA and 94% complete.  See:

https://wiki.yoctoproject.org/wiki/2.7_QA_Status
*   YP M2 rc1 had major problems in perl as fallout from the perl
upgrade and switch to perl-cross. We've therefore built an rc2 based on a
more recent master.
*   The project is considering moving its mailing list hosting to
groups.io, if anyone has any experience of that, positive or negative please
let Michael, Nico and Richard know. Note that google has made further
significant changes to its mail processing at the detriment to mailing
lists:

https://lists.freedesktop.org/archives/freedesktop/2019-February/000396.html
*   RDEPENDS handling in native recipes had a significant change, fixing
some long standing bugs but also needing some circular dependencies to be
fixed. The change may impact other layers.
*   Circular dependency debugging from bitbake was fixed and should no
longer hang, another long standing issue which when fixed, allowed the
native RDEPENDS to be debugged and fixed.
*   The default compiler path mappings were enhanced and should now also
cover macro files.
*   There is major work/review going on for "resulttool" with a view to
using this for QAing M3.
*   A new round of AUH (Automatic upgrade Helper) patches has been sent,
thanks to everyone who's processed and responded to those! It was able to
upgrade around half the recipes needing upgrading.

 

Planned Releases for YP 2.7:

*   YP 2.7 M2 is in QA for rc2.
*   YP 2.7 M2 Release Target is Feb. 1, 2019
*   YP 2.7 M3 Cutoff is Feb. 25, 2019
*   YP 2.7 M3 Release Target is Mar. 8, 2019
*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*   YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*   YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

 

Tracking Metrics:

*   WDD 2392 (last week 2353) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1527 (last week 1527
*   Patches in the Pending State: 663 (43%) [last week 663 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW07'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M3

Next Deadline: YP 2.7 M3 Cutoff is Feb. 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Paul 
*   SWAT team rotation: Paul -> Ross on Feb. 15, 2019
*   SWAT team rotation: Ross -> Amanda on Feb. 22, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*   YP M2 rc1 had major problems in perl as fallout from the perl
upgrade and switch to perl-cross. We've therefore built an rc2 based on a
more recent master.
*   The python upgrade to 3.7 merged, thanks to AlexK for his hard work
on this. It means all of the major components in OE-Core are finally up to
date (many minor versions are still adrift).
*   Major util-linux changes have just merged which should hopefully
allow easier long term maintenance of this recipe (all binaries now have
their own package, this recipe kept being split up)
*   Build performance tests on the autobuilder have been improved and
builds now have automated result comparisons, e.g.:

https://autobuilder.yocto.io/pub/non-release/20190212-7/testresults/buildper
f-ubuntu1604/perf-ubuntu1604_master_20190212045844_be52da1.html (from

https://autobuilder.yoctoproject.org/typhoon/#/builders/92/builds/101)
(Thanks to Markus for a lot of the underlying code/work)
*   Build performance can now compare master to master-next test builds
*   We continue to need help with ptest, both on the tests themselves
and on the results reporting. The intent is to have something similar to the
build performance pieces above.
*   The recipe reporting system integration with the layer index is
available at:  
https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the
historical data has now been imported.
*   The project is considering moving its mailing list hosting to
groups.io, if anyone has any experience of that, positive or negative please
let Michael, Nico and Richard know. Note that google has made further
significant changes to its mail processing at the detriment to mailing
lists:

https://lists.freedesktop.org/archives/freedesktop/2019-February/000396.html
*   If anyone has feedback about the maintainers/recipe upgrade
processes or how to attract new recipe maintainers, please talk to Richard
Purdie / Ross Burton

 

Planned Releases for YP 2.7:

*   YP 2.7 M2 is being rebuilt and will go back to QA for rc2.
*   YP 2.7 M2 Release Target is Feb. 1, 2019
*   YP 2.7 M3 Cutoff is Feb. 25, 2019
*   YP 2.7 M3 Release Target is Mar. 8, 2019
*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*   YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*   YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

 

Tracking Metrics:

*   WDD 2353 (last week 2356) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1527 (last week 1572
*   Patches in the Pending State: 663 (43%) [last week 678 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 294 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 

*Cell:(208) 244-4460

* Email: stephen.k.jol...@intel.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] New e-mail address

[sjolley.yp.pm]

All,

 

I have moved from stephen.k.jol...@intel.com
  to sjolley.yp...@gmail.com
  for my e-mail address I am using for the
Yocto Project PM work.   Please use the new e-mail address if you wish to
communicate with me going forward.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] YPTM minutes

[sjolley.yp.pm]

Yocto Technical Team Minutes for Feb. 5, 2019.

 

Attendees: Armin, David, Joshua, Randy, Tim, Richard G., Stephen, Jan-Simon,
Manjukum, Tracey, Trevor, Nick, Richard P, Mark, Kate, Michael, 

 

YP 2.6.1 was released on Feb. 4, 2019.

YP 2.7 M2 was built and is in QA and is 79% done.  See:

https://wiki.yoctoproject.org/wiki/2.7_QA_Status

 

Armin agreed to add Ubuntu 18.4 to YP 2.6 series and we will use in for YP
2.7 

We discussed that the YP 2.6 manual doesn't have an upgrading to YP 2.6.
Tracey will look into this.

 

We discussed the status of YP 2.7 upgrades and we are doing OK there.  We
are struggling on new features YP 2.7.  Richard is primarily working to
stabilize the autobuilder to produce an automated QA report to allow QA to
transition from Intel. 

 

Richard discussed maintainers of OE-Core.  AUH is sending requests but not
getting feedback. 

 

Richard discussed that we have issues with some products and need support
from the community to fix.

 

Tim discussed ptest issues Richard has identified.

 

Richard asked if there were ideas about how to better communicate with the
community. No specific suggestions.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW06'19

[sjolley.yp.pm]

Current Dev Position: YP 2.7 M3

Next Deadline: YP 2.7 M3 Cutoff is Feb. 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Anuj 
*   SWAT team rotation: Anuj -> Paul on Feb. 8, 2019
*   SWAT team rotation: Paul -> Ross on Feb. 15, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*   YP 2.6.1 was released on Feb. 4, 2019.
*   YP 2.7 M2 was built and is in QA and is 79% done.  See:

https://wiki.yoctoproject.org/wiki/2.7_QA_Status
*   Some major recipe upgrades merged (glibc, binutils, llvm)
*   Some "prework" patches for various series merged (util-linux,
virtgl) but the main series are still pending development or review
*   Various ptest-runner and ptest runtime testing integration fixes
merged but many problems with the tests remain no volunteers to help resolve
issues.
*   We're seeing test failures which highlight major problems with the
archiver class, in particular the src.rpm component of it. I've proposed we
remove it, if you do care about it please step up and help fix it else it
will be removed. The src.rpm support is limited anyhow and likely to mislead
user expectations so removing it may be a good thing.
*   The recipe reporting system integration with the layer index is now
complete and available at:

https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/. Historical data
has not yet been imported to it.
*   The project autobuilder is running at slightly reduced capacity (but
not functionality) due to hardware failures.
*   The project is considering moving its mailing list hosting to
groups.io, if anyone has any experience of that, positive or negative please
let Michael, Nico and Richard know
*   We're becoming seriously concerned about the lack of response to the
last round of AUH patches

 

Planned Releases for YP 2.7:

*   YP 2.7 M2 is built and in QA.
*   YP 2.7 M2 Release Target is Feb. 1, 2019
*   YP 2.7 M3 Cutoff is Feb. 25, 2019
*   YP 2.7 M3 Release Target is Mar. 8, 2019
*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*   YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*   YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

 

Tracking Metrics:

*   WDD 2356 (last week 2393) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1572 (last week 1583
*   Patches in the Pending State: 678 (43%) [last week 677 (43%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

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 Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 294 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 

*Cell:(208) 244-4460

* Email: stephen.k.jol...@intel.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PDT)

[sjolley.yp.pm]

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at
8am PDT tomorrow. (2/5)  

 

I will start tracking the minutes at:

https://docs.google.com/document/d/1Y5IIuE-z0Ykdl-DwuzUJh52flOZuhN_TSAfw2tdU
9pg/edit?ts=5c06b22d  Please request access if you want to assist in editing
them.  The world should have view access. 

 

Yocto Project Technical Team Meeting: We encourage people attending the
meeting to logon and announce themselves on the Yocto Project IRC chancel
during the meeting (optional):

Yocto IRC:  
http://webchat.freenode.net/?channels=#yocto

 

Wiki:  
https://www.yoctoproject.org/public-virtual-meetings/

 

WhenMonthly from 8am to 8:30am on the first Tuesday Pacific Time

Where   Zoom Meeting:  
https://zoom.us/j/990892712 

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto