2019 Yocto Project Weekly Status Archive

From Yocto Project
Jump to: navigation, search

Editing Weekly Status (section) Bold textItalic textInternal linkExternal link (remember http:// prefix)Level 2 headlineEmbedded fileFile linkIgnore wiki formattingYour signature with timestampHorizontal line (use sparingly)

Contents

Yocto Project Weekly Status December 17, 2019

Current Dev Position: YP 3.1 M2
Next Deadline: YP 3.1 M2 build date 1/20/2020

Next Team Meetings:

Key Status/Updates:

  • YP 3.0.1 was released.
  • YP 3.1 M1 rc8 is in QA
  • YP 3.1 M1 took a record number of build attempts due to various issues which only appeared during the rc builds.
  • Despite a successful rc8 build (which still had reproducible build test failures) there are a number of concerns, particularly as there appears to be very slow builds for some ‘pathological’ hashequiv scenarios. There has been some progress over the weekend on identifying the causes of that and partially addressing them.
  • There remains a growing set of intermittent autobuilder failures which occur with varying frequencies. We’re struggling to find anyone with time/interest to resolve these and they are becoming problematic for reviewing/testing patches and triaging builds.
  • 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 coming weeks.
  • We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
  • Due to holidays in EU/US, the next status report will be sent in early January (likely 7th). If there is anything critical to report this will happen as needed.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M1 is in QA
  • YP 3.1 M1 release date 12/13/2019
  • YP 3.1 M2 build date 1/20/2020
  • YP 3.1 M2 release date 1/31/2020
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 build date 2/10/20
  • YP 2.7.3 release date 2/21/20
  • YP 3.0.2 build date 2/3/20
  • YP 3.0.2 release date 2/14/20

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status December 10, 2019

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

Next Team Meetings:

Key Status/Updates:

  • YP 3.0.1 was released.
  • Python 2.x has been removed from HOSTTOOLS so OE-Core is python2 use free.
  • Hash Equivalency has been enabled by default for poky using a local server.
  • YP 3.1 M1 was due to be built but issues have been encountered in the release builds, both with previously unseen hash equivalence issue and a ptest performance regression on the autobuilders. Both issues are being worked on but are further delaying a successful M1 build.
  • 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.
  • Patch review and testing has run into new issues with a number of regressions from upgrades causing instability. Most of these were isolated pre-merge but not all.
  • 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 coming weeks.
  • We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/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 build date 12/2/2019
  • YP 3.1 M1 release date 12/13/2019
  • YP 3.1 M2 build date 1/20/2020
  • YP 3.1 M2 release date 1/31/2020
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 3.0.1 is released.
  • YP 2.7.3 build date 2/10/20
  • YP 2.7.3 release date 2/21/20
  • YP 3.0.2 build date 2/3/20
  • YP 3.0.2 release date 2/14/20

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status December 3, 2019

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

Next Team Meetings:

Key Status/Updates:

  • YP 3.0.1 is out of QA with good test results so should be released soon.
  • We have set a deadline of Monday 9th December for removing python2 support from OE-Core, a separate email was sent out about this. The patches to do this are in master-next and they remove python and python2 from HOSTTOOLS.
  • Reproducible builds are now enabled by default in poky, we should also consider this for the default in OE-Core.
  • Hash equivalence continues to undergo testing and further work.
  • We’re likely to build M1 after the python 2 removal is merged next week, also giving time for the hash equivalence work to move forward further.
  • 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 coming weeks.
  • We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/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 build date 12/2/2019
  • YP 3.1 M1 release date 12/13/2019
  • YP 3.1 M2 build date 1/20/2020
  • YP 3.1 M2 release date 1/31/2020
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 3.0.1 is out of QA and should be released soon.
  • YP 2.7.3 build date 2/10/20
  • YP 2.7.3 release date 2/21/20
  • YP 3.0.2 build date 2/3/20
  • YP 3.0.2 release date 2/14/20

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status November 26, 2019

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

Next Team Meetings:

Key Status/Updates:

  • YP 2.7.2 should be released imminently.
  • The reproducibility issues from last week have been addressed and we are hoping to enable this by default soon, thanks to everyone who helped fix issues.
  • The news for hash equivalence is not so promising. Whilst a number of bugs were fixed, we’ve found a major problem which explains some of the failures we’ve seen and are currently working out how we may be able to resolve that issue.
  • 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 focus on hash equivalence and reproducibility has slowed patch merging in other areas. Patch testing has been problematic as there are a lot of regressions being found in submitted patches which also slows down the whole merging process.
  • 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_f4ye64yjnABc/edit?usp=sharing
  • Due to the number of key fixes being found we have delayed YP 3.0.1 being built slightly whilst we merge those fixes, it should build in the next few days.
  • If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+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:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status November 19, 2019

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

Next Team Meetings:

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 have begun collecting ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
  • If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+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:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status November 12, 2019

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
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

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_sUkyc/ . 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 have begun collecting ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
  • If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+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:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status November 5, 2019

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

SWAT Team Rotation:

  • SWAT lead is currently: Armin
  • SWAT team rotation: Armin-> Anuj on Nov. 8, 2019
  • SWAT team rotation: Anuj -> Chen on Nov. 15, 2019
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

Key Status/Updates:

  • The project presence at ELC-E in Lyon was strong, thanks to everyone who contributed, be it through presentations, helping with the booth, visiting the booth or attending or assisting with the summit!
  • YP 2.6.4 was released
  • Patches have continued to merge and master is staying roughly current with the pending patch queue. The autobuilder is still suffering a number of intermittent failures which will start to hamper future development. We’re likely going to have to pause and address those before other development can continue.
  • In particular, issues with pseudo on fedora30 have become apparent due to its use of the new statx() syscall.
  • YP 2.7.2 has been built and is now in QA
  • 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_sUkyc/
  • We have begun collecting ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
  • If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+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.
  • YP 2.6.4 (Thud) was released

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status October 29, 2019

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

SWAT Team Rotation:

  • SWAT lead is currently: Amanda
  • SWAT team rotation: Amanda -> Armin on Nov. 1, 2019
  • SWAT team rotation: Armin-> Anuj on Nov. 8, 2019
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

Key Status/Updates:

  • Yocto Project “Zeus” 3.0 has been released! Thank you to everyone who contributed patches, bugs, feedback and testing. Some very rough git metrics say that 182 different people have contributed patches to this cycle.
  • This week is ELC-E in Lyon, so meetings are limited. If anyone reading this is there please do visit the Yocto Project booth and say hello!
  • Patches have been flowing fast into master. Due to ELC-E this will slow down this week, but Ross will continue to collect patches for testing in ross/mut.
  • There are ongoing intermittent autobuilder failures, particularly in selftest but in other areas too. There is a separate email about this and we could do with help in debugging and resolving those issues.
  • YP 2.6.4 was built and has passed QA, will be released imminently.
  • YP 2.7.2 was held due to an unexplained test failure but will now be built in the next few days.
  • Armin and Anuj have volunteered to maintain Zeus and they plan to work out the maintainership between them, thanks!
  • We have begun collecting ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
  • 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}:

  • YP 3.0 {2.8 (M4)} Final Release 25th Oct

Planned upcoming dot releases:

  • YP 2.7.2 (Warrior) is planned this week.
  • YP 2.6.4 (Thud) is to be released shortly.

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status October 22, 2019

Current Dev Position: YP 3.0 Final Release
Next Deadline: YP 3.0 Final Release 25th Oct

SWAT Team Rotation:

  • SWAT lead is currently: Paul
  • SWAT team rotation: Ross -> Amanda on Oct. 25, 2019
  • SWAT team rotation: Amanda -> Armin on Nov. 1, 2019
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

Key Status/Updates:

  • YP 3.0 as been approved by the TSC and should be released later this week. Only the final tweaks to the release notes remain.
  • Master has continued taking patches for post 3.0.
  • There are a number of intermittent failures on the autobuiler which are causing concern, there is a separate email about this.
  • YP 2.6.4 was built and submitted to QA
  • YP 2.7.2 was not built due to a remaining bug which needs to be resolved first

Next week is ELC-E and therefore may be quiet on the mailing lists with patch merging being delayed.

Planned Releases for YP 3.0 {2.8}:

  • YP 3.0 {2.8 (M4)} Final Release 25th Oct

Planned upcoming dot releases:

  • YP 2.7.2 (Warrior) s planned this week (assuming the remaining bug is resolved).
  • YP 2.6.4 (Thud) is in QA.

Tracking Metrics:

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

Yocto Project Weekly Status October 15, 2019

Current Dev Position: YP 3.0 Final Release
Next Deadline: YP 3.0 Final Release 25th Oct

SWAT Team Rotation:

  • SWAT lead is currently: Paul
  • SWAT team rotation: Paul -> Ross on Oct. 18, 2019
  • SWAT team rotation: Ross -> Amanda on Oct. 25, 2019
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

Key Status/Updates:

  • YP 3.0 was built and submitted to QA as 3.0 rc2 (rc1 had build failures).
  • There is a QA report from QA for 3.0 rc2. There were two issues raised from testing but these are both relatively minor issues that are unlikely to block release.
  • The release is therefore now pending a decision from the TSC on whether we should release.
  • Master has started taking patches for post 3.0 to try and avoid any further backlog buildup.
  • We plan to build 2.7.2, followed by 2.6.4 imminently, Armin has been preparing the branches.
  • We have begun collecting ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
  • 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}:

  • YP 3.0 {2.8 (M4)} Final Release 25th Oct

Planned upcoming dot releases:

  • YP 2.7.2 (Warrior) is planned this week.
  • YP 2.6.4 (Thud) is planned for after YP 2.7.2 release.

Tracking Metrics:

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

Yocto Project Weekly Status October 8, 2019

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: Chen
  • SWAT team rotation: Chen -> Paul on Oct. 11, 2019
  • SWAT team rotation: Paul -> Ross on Oct. 18, 2019
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

Key Status/Updates:

  • The project is about to build M4 rc1 once some final tweaks have been tested and merged (details below).
  • Known issues that have been or are to be addressed before M4 rc1 is built:
    • Strace kernel timeout problems - the issue has now been reproduced and understood upstream and a patch has been found to address the issue. We therefore plan to include this in M4 rc1 (thanks Bruce)
    • We upgraded to a new uninative version to ensure compatibility with distros shipping glibc 2.30 (thanks Michael/Armin).
    • We resolved the systemd hwdb postinst script issues (thanks Ross)
  • The eSDK performance issue has been worked around but removal of old sstate artefacts on the system however we ultimately do need to improve the code (will target 3.1).
  • 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}:

  • 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:

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

Yocto Project Weekly Status October 1, 2019

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: Armin
  • SWAT team rotation: Armin -> Chen on Oct. 4, 2019
  • SWAT team rotation: Chen -> Anuj on Oct. 11, 2019
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

Key Status/Updates:

  • We’re now in feature freeze in M4 for 3.0 and working on bug fixing for final release
  • We have a QA report for M3 and this is due for release this week
  • The known issues to be addressed before M4 rc1 is built:
    • Strace kernel timeout problems
    • Better solution for systemd hwdb timeout
    • Fixes for the lsb->altcfg release directory names
    • Fix for hashserv bitbake-selftest server shutdown issue
    • There is bitbake upgrade problem where an older OE-Core doesn’t work with a newer bitbake due to bb.build.FuncFailed being missing#
  • The aim is to build M4 rc1 this week if at all possible but it depends on the above issues being fixed (there are open high bugs for these)
  • A significant performance problem has been found on the autobuilder where some builds are scaling in time badly as the sstate cache grows, taking 12 hours or more in some cases. Unfortunately nobody seems motivated to help work on this kind of issue.
  • 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 this week.
  • 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:

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

Yocto Project Weekly Status September 24, 2019

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: Amanda
  • SWAT team rotation: Amanda -> Chen on Sept. 27, 2019
  • SWAT team rotation: Chen -> Armin on Oct. 4, 2019
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

Key Status/Updates:

  • We’re now in feature freeze for 3.0 and working on bug fixing for final release
  • We have built M3 and this is due from QA on Thursday
  • The main unresolved issue for 3.0 is with the hash equivalence server causing problems with the eSDK and this issue is being investigated but can’t be reproduced as yet.
  • We also want to find a better solution to the systemd timeout problem before final release.
  • A significant performance problem has been found on the autobuilder where some builds are scaling in time badly as the sstate cache grows, taking 12 hours or more in some cases. Unfortunately nobody seems motivated to help work on this kind of issue.
  • The plan for M4 is to resolve the above issues and any issues raised from M3 QA, then proceed with the main release rc builds. The first M4 build is scheduled for next week.
  • 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:

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

Yocto Project Weekly Status September 17, 2019

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: Ross -> Amanda on Sept. 20, 2019
  • SWAT team rotation: Amanda -> Chen on Sept. 27, 2019
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

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 there are still three issues that need to be resolved:
    • strace ptest regressions with 5.1/5.2 kernels
    • systemd timeouts on mips
    • hashequiv server rewrite
  • The strace regressions will be discussed with the kernel community, the best workaround may be to lower the individual test timeouts so one the affected individual tests fail rather than all tests timing out.
  • The qemumips issue with systemd is puzzling as its happening in hwdb and hwdb should be generated in advance anyway. Investigation is ongoing about why its being regenerated, a workaround is to increase the timeout as mips is just slow (it does complete eventually, its just marginal).
  • The hashequiv server changes are being tested in master-next

It is planned to build M3 this week with the workarounds mentioned above worst case. Its expected there would be further hashequiv fixing during M4.

  • We hope to make up time during M4 by having M3 at high quality and take advantage of our automation.
  • 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:

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

Yocto Project Weekly Status September 10, 2019

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
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

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:

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

Yocto Project Weekly Status September 3, 2019

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: Armin
  • SWAT team rotation: Armin -> Paul on Sept. 6, 2019
  • SWAT team rotation: Paul -> Ross on Sept. 13, 2019
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

Key Status/Updates:

  • We’re now in feature freeze for 3.0 and working on bug fixing for final release
  • Several key 3.0 changes have now merged:
    • 5.2 linux-libc-kernel-headers
    • 5.2 kernel recipes
    • Removal of LSB and poky-lsb and replacement with alt config testing
    • Patches have significantly reduced the dependency on python2
    • Reproducible builds are now being tested for core-image-minimal
  • There are the following changes still under discussion/testing:
    • Systemd vs. sysvinit defaults (maybe for the poky alternative configuration tests)
    • Making 5.2 the default kernel for qemu (has regressions, see below)
    • Hashserv performance issue resolution
    • Final configuration of hash equivalency
    • toolchain testsuite patch series
  • The sstate hash equivalency continues to have challenges:
    • 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
  • Patch merging is roughly up to date again
  • We have several significant problematic bugs that are being worked on:
    • 5.2 stap build issue on qemuarm
    • 5.2 kprobes error message (qemuarm64, qemumips64)
    • qemumips machine hang

8If 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:

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

Yocto Project Weekly Status August 27, 2019

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: Anuj
  • SWAT team rotation: Anuj -> Armin on Aug. 30, 2019
  • SWAT team rotation: Armin -> Paulj on Sept. 6, 2019
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

Key Status/Updates:

  • We’re now in feature freeze for 3.0 and working on bug fixing for final release
  • There are the following planned features which are still under consideration for 3.0:
    • Systemd vs. sysvinit defaults (maybe for the poky alternative configuration tests)
    • Removal of LSB and poky-lsb and replacement with alt config testing
    • Final configuration of hash equivalency
  • The sstate hash equivalency continues to have challenges:
    • 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
  • Patch merging has been delayed due to vacations (RP and Ross) so the final feature patches aren’t resolved yet.
  • If anyone has any status items for the proj

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:

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

Yocto Project Weekly Status August 20, 2019

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
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

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:

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

Please note that all contributions to Yocto Project may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Yocto Project:Copyrights for details). Do not submit copyrighted work without permission!

Summary: /* Yocto Project Weekly Status August 20, 2019 */

This is a minor edit  Watch this page
  Cancel | Editing help (opens in new window)

page discussion edit history move watch Stephen K. Jolley talk preferences watchlist contributions log out navigation Main page Recent changes Random page search

tools What links here Related changes Upload file Special pages Powered by MediaWiki Privacy policy About Yocto Project Disclaimers

Yocto Project Weekly Status August 13, 2019

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
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

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:

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

Yocto Project Weekly Status August 6, 2019

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

SWAT Team Rotation:

Next Team Meetings:

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

Tracking Metrics:

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

Yocto Project Weekly Status July 30, 2019

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

SWAT Team Rotation:

Next Team Meetings:

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:

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

Yocto Project Weekly Status July 23, 2019

Current Dev Position: YP 2.8 M2
Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

SWAT Team Rotation:

Next Team Meetings:

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:

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

Yocto Project Weekly Status July 16, 2019

Current Dev Position: YP 2.8 M2
Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

SWAT Team Rotation:

Next Team Meetings:

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:

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

Yocto Project Weekly Status July 9, 2019

Current Dev Position: YP 2.8 M2
Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

SWAT Team Rotation:

Next Team Meetings:

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:

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

Yocto Project Weekly Status July 2, 2019

Current Dev Position: YP 2.8 M2
Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

SWAT Team Rotation:

Next Team Meetings:

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:

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

Yocto Project Weekly Status June 25, 2019

Current Dev Position: YP 2.8 M2
Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

SWAT Team Rotation:

Next Team Meetings:


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
  • YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and before 2.8 M2

Tracking Metrics:

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

Yocto Project Weekly Status June 18, 2019

Current Dev Position: YP 2.8 M2
Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

SWAT Team Rotation:

Next Team Meetings:

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:

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

Yocto Project Weekly Status June 11, 2019

Current Dev Position: YP 2.8 M2
Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

SWAT Team Rotation:

Next Team Meetings:

Key Status/Updates:

  • 2.8 M1 has been built and rc2 is now undergoing QA (rc1 ran into an issue with a broken autobuilder worker).
  • Stephen continues to be unavailable, please refer any queries to Richard
  • Mailing lists are moving to groups.io instead of our current mailman setup. This shouldn’t impact users directly, more details will be sent to the mailing lists before the transfer. THe Yocto Project lists will move first, followed by OE, likely a week later.
  • 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 seeing an increasing number of intermittent failures which affect the autobuilder builds, causing problems for merging patches and for release builds. One cause, a long standing problem with gpg signing testing has finally been root caused and fixed. Several others keep appearing. There is a backlog of them in the bugzilla and we’re opening bugs for the new ones.
  • M1 isn’t of ideal quality, there are three ptest timeouts (2.7 had none). The ptest failure rate is however much improved. There is nobody actively working on some of the ptest timeout issues so holding the milestone build wouldn’t have made much difference but its a worrying sign for the project quality.
  • M1 also has a couple of MIPS issues with the gcc9 upgrade. There doesn’t appear to be much interest in investigating and fixing these which raises questions about supporting the architecture within the project.
  • There was a Yocto Project related article in LWN: https://lwn.net/Articles/788626/

Planned Releases for YP 2.8:

  • M1 Cutoff June 9th
  • M1 Release June 21st
  • 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.6.3 (Thud) is in planning
  • YP 2.7.1 (Warrior) is in planning

Tracking Metrics:

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

Yocto Project Weekly Status June 4, 2019

Current Dev Position: YP 2.8 M1
Next Deadline: YP 2.8 Milestone 1 Cutoff June 9th, 2019

SWAT Team Rotation:

Next Team Meetings:

Key Status/Updates:

  • 2.8 M1 is nearly upon us with just under a week left for the remaining features/patches.
  • Stephen continues to be unavailable, please refer any queries to Richard
  • Mailing lists are moving to groups.io instead of our current mailman setup. This shouldn’t impact users directly, more details will be sent to the mailing lists before the transfer. THe Yocto Project lists will move first, followed by OE, likely a week later.
  • 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
  • Uninative 2.5 was released which supports gcc 9. This should fix issues for fedora 30 builds and allow the bringup of fedora 30 workers in the autobuilder too.
  • ARM native builds are now working on the autobuilder as well as KVM accelerated ARM ptest and ltp testing.
  • There are ongoing concerns about perl module dependencies. Tim and Richard have applied bandaids to solve some ptest issues but we really need work in this area if there are any perl experts interested.
  • Many further ptests fixes have merged, thanks to all for the contributions.

Planned Releases for YP 2.8:

  • M1 Cutoff June 9th
  • M1 Release June 21st
  • 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.6.3 (Thud) is in planning
  • YP 2.7.1 (Warrior) is in planning

Tracking Metrics:

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

Yocto Project Weekly Status May 28, 2019

Current Dev Position: YP 2.8 M1
Next Deadline: YP 2.8 Milestone 1 Cutoff June 9th, 2019

SWAT Team Rotation:

Next Team Meetings:


Key Status/Updates:

  • Stephen is going to be unavailable for several weeks, please refer any queries to Richard
  • Mailing lists are moving to groups.io instead of our current mailman setup. For various reasons the move was delayed and will take place on 3rd June. This shouldn’t impact users directly, more details will be sent to the mailing lists in due course.
  • 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
  • Adrian Bunk has done some much appreciated work in removing patches which are no longer needed or appropriate.
  • Various upgrades and ptest dependency fixes merged. Work is still needed on ptest dependencies, particularly on perl modules.
  • Gcc 9 is now the default, thanks to Khem for working around the remaining bug in OE-Core

Planned Releases for YP 2.8:

  • M1 Cutoff June 9th
  • M1 Release June 21st
  • 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.6.3 (Thud) is in planning
  • YP 2.7.1 (Warrior) is in planning

Tracking Metrics:

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

Yocto Project Weekly Status May 21, 2019

Current Dev Position: YP 2.8 M1
Next Deadline: YP 2.8 Milestone 1 Cutoff June 9th, 2019

SWAT Team Rotation:

Next Team Meetings:


Key Status/Updates:

  • Stephen is going to be unavailable for several weeks, please refer any queries to Richard
  • The final 2.8 planning meeting was held. The google doc summarising the discussions so far: https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/
  • Mailing lists are moving to groups.io instead of our current mailman setup on 27th May. This shouldn’t impact users directly, more details will be sent to the mailing lists in due course.
  • 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
  • Work is continuing to improve the ptest reliability with a focus now on ensuring the dependencies are correct.

Planned Releases for YP 2.8:

  • M1 Cutoff June 9th
  • M1 Release June 21st
  • 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.6.3 (Thud) is in planning
  • YP 2.7.1 (Warrior) is in planning

Tracking Metrics:

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

Yocto Project Weekly Status May 14, 2019

Current Dev Position: YP 2.8 M1
Next Deadline: YP 2.8 Milestone 1 Cutoff June 9th, 2019

SWAT Team Rotation:

Next Team Meetings:


Key Status/Updates:

  • Stephen is going to be unavailable for several weeks, please refer any queries to Richard
  • The final 2.8 planning meeting was held. The google doc summarising the discussions so far: https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/
  • 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.
  • Most items planned to be worked upon should now be in the bugzilla with appropriately detailed entries there.
  • A summary of the 2.8 planning risk items was included in an email to the yocto-ab list:https://lists.yoctoproject.org/pipermail/yocto-ab/2019-May/002334.html
  • The project is planning to adopt SPDX license headers in its source code where practical, OE-Core now has the markup on its scripts too.
  • Mailing lists are moving to groups.io instead of our current mailman setup on 27th May. This shouldn’t impact users directly, more details will be sent to the mailing lists in due course.
  • 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 about ready to switch over to gcc 9 by default with one more issue needing to be resolved on mips.
  • We’re likely going to change the tuning of qemux86 to something more modern
  • We’re likely to drop openssl 1.0 and irda from OE-Core imminently

Planned Releases for YP 2.8:

  • M1 Cutoff June 9th
  • M1 Release June 21st
  • 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.6.3 (Thud) is in planning
  • YP 2.7.1 (Warrior) is in planning

Tracking Metrics:

Yocto Project Weekly Status May 7, 2019

Current Dev Position: YP 2.8 M1
Next Deadline: YP 2.8 Milestone 1 Target May ??, 2019

SWAT Team Rotation:

Next Team Meetings:


Key Status/Updates:

  • Stephen is going to be unavailable for several weeks, please refer any queries to Richard
  • YP 2.7 was released
  • 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_t6smpZO2HbaJGXbU/
  • 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.
  • At this point we believe we’ve made our final release for the sumo (2.5) series
  • The project is planning to adopt SPDX license headers in its source code where practical, bitbake has had these merged as a first step.
  • 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

Planned Releases for YP 2.8:

  • TBA

Planned upcoming dot releases:

  • YP 2.6.3 (Thud) is in planning
  • YP 2.7.1 (Warrior) is in planning

Tracking Metrics:

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


Yocto Project Weekly Status April 30, 2019

Current Dev Position: YP 2.7 M4 (2.7 rc2 is in QA)
Next Deadline: YP 2.7 Release Target April 26, 2019

SWAT Team Rotation:

Next Team Meetings:


Key Status/Updates:

  • Stephen is going to be unavailable for several weeks, please refer any queries to Richard
  • YP 2.5.3 was released.
  • YP 2.7 is out of QA but pending answers to some questions on the QA report and the final pieces of release process.
  • Huge kudos this week go to Armin for work on test automation of some of the manual tests
  • We’ve merged ltp test automation which is now being run automatically on the autobuilder on a-full builds.
  • Master continues to take patches, somewhat slowed by host specific build issues with vte-native
  • WDD, our bug tracking metric is high and there are few people helping with bugs.
  • 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_t6smpZO2HbaJGXbU/
  • 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.
  • 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


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.6.3 (Thud) is in planning

Tracking Metrics:

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

Yocto Project Weekly Status April 23, 2019

Current Dev Position: YP 2.7 M4 (2.7 rc2 is in QA)
Next Deadline: YP 2.7 Release Target April 26, 2019

SWAT Team Rotation:

Next Team Meetings:

Key Status/Updates:

  • Stephen is going to be unavailable for several weeks, please refer any queries to Richard
  • YP 2.6.2 was released!
  • YP 2.5.3 is likely to be released imminently
  • YP 2.7 rc2 (warrior) is currently going through QA.
  • The final two members of the new YP TSC were elected, Denys and Armin. The TSC will therefore now start to discuss how its going to establish itself and operate.
  • Huge thanks to Joshua Watt for diving in and helping file some ptest bugs and helping sort some missing tweaks with resulttool, it was just appreciated
  • Patches are continuing to flow into master, slightly impeded by holidays/vacation in some parts of the world.
  • WDD, our bug tracking metric is sharply rising as there are few people helping with bugs.
  • 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_t6smpZO2HbaJGXbU/
  • 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) due for release.

Tracking Metrics:

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

Yocto Project Weekly Status April 16, 2019

Current Dev Position: YP 2.7 M4 (2.7 rc2 is in QA)
Next Deadline: YP 2.7 Release Target April 26, 2019

SWAT Team Rotation:

Next Team Meetings:

Key Status/Updates:

  • Stephen is unavailable at the moment, please refer any queries to Richard
  • YP 2.6.2 was rebuilt as rc4 to include the boost upgrade revert and is due to be released today. The YP 2.6.2 rc3/4 report is summarized at https://lists.yoctoproject.org/pipermail/yocto/2019-April/044827.html and the results are at https://autobuilder.yocto.io/pub/releases/yocto-2.6.2.rc4/testresults/.
  • YP 2.5.3 is currently going through the QA process.
  • We’re sad to announce that we will be removing eclipse plugin builds from the autobuilder and will not be including the plugin in any future project releases. This is due to a lack of anyone able to help work on the plugin development, bug fixing or release.
  • The key fixes mentioned in last week’s status have been merged into 2.7.
  • A key bug in pseudo was identified which may be the root cause of the long standing glibc-locale uid “host contamination” issue. Many thanks to Peter and Otavio for the help in debugging that. A separate fix should also ensure pseudo works with newer distro coreutils and glibc versions.
  • YP 2.7 rc2 (warrior) was built successfully and is currently going through the QA process after 2.5.3 is done.
  • The ptest results in 2.7 are much more stable than ever before with results being consistent from build to build. At the start of 2.8 we can make some further improvements so we take advantage of this and build upon it to reduce regressions in the system.
  • In an effort to keep the patch queue under control, patches are merging to master.
  • The list of issues from last week of worrying things we lack resources to improve upon remains:
    • 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_t6smpZO2HbaJGXbU/
  • 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.

Tracking Metrics:

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

Yocto Project Weekly Status April 9, 2019

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:

Next Team Meetings:

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_t6smpZO2HbaJGXbU/
  • 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:

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

Yocto Project Weekly Status April 2, 2019

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:

Next Team Meetings:

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_t6smpZO2HbaJGXbU/ 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:

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

Yocto Project Weekly Status March, 26, 2019

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

SWAT Team Rotation:

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:

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

Yocto Project Weekly Status March, 19, 2019

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

SWAT Team Rotation:

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 M3 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:

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

Yocto Project Weekly Status March, 12, 2019

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

SWAT Team Rotation:

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:

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

Yocto Project Weekly Status March, 5, 2019

Current Dev Position: YP 2.7 M3
Next Deadline: YP 2.7 M3 Cutoff was Mar. 5, 2019

SWAT Team Rotation:

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:

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

Yocto Project Weekly Status February 26, 2019

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

SWAT Team Rotation:

Key Status/Updates:

http://lists.openembedded.org/pipermail/openembedded-architecture/2019-February/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:

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

Yocto Project Weekly Status February 19, 2019

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

SWAT Team Rotation:

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/buildperf-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 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:

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

Yocto Project Weekly Status February 12, 2019

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

SWAT Team Rotation:

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

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

Yocto Project Weekly Status February 5, 2019

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

SWAT Team Rotation:

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:

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

Yocto Project Weekly Status January 29, 2019

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

SWAT Team Rotation:

Key Status/Updates:

  • YP 2.6.1 should release this week. The transition to automated QA is raising some questions about test results but we’re working through those.
  • YP 2.7 M2 was built and is in QA and is 8% done. See: https://wiki.yoctoproject.org/wiki/2.7_QA_Status
  • There have been a further round of gitsm fixes (and new test case additions). If anyone is seeing gitsm fetcher issues please report them. There are requests to backport these changes to the stable series. This has risks but people are reporting bugs there so is something we need to consider.
  • There has been little follow up from the last round of AUH patches. Please can maintainers work on this and get these submitted!
  • There has been little feedback on the proposed virtgl changes, these will likely merge as no discussion will be taken to mean there are no objections. This will have a performance impact.
  • There have been changes to the way the arm tunes are handled which merged after much discussion. The solution that merged should be safe and uncontroversial but if these do cause problems for anyone, please report ASAP.
  • We’re getting much improved results from our automated testing but these are highlighting a number of problems. There is an email about issues found in ptest. The biggest challenge here now is finding people able to step up and help improve things.

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.6.1 (Thud) will release shortly.
  • 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:

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

Yocto Project Weekly Status January 22, 2019

Current Dev Position: YP 2.7 M2
Next Deadline: YP 2.7 M2 Cutoff is Jan. 21, 2019

SWAT Team Rotation:

  • SWAT lead is currently: Chen

SWAT team rotation: Chen -> Armin on Jan. 25, 2019

Key Status/Updates:

  • YP 2.6.1 is out of QA and the QA results are being reviewed. See: https://wiki.yoctoproject.org/wiki/WW02_-_2019-01-09_-_Full_Test_Cycle_2.6.1_RC1
  • We have preliminary patches for the qemuarm migration to an armv7 machine. These haven’t passed testing and will need some improvements, particularly in the area of graphics support so will be deferred to M3 but it is great to see progress being made.
  • The qemu virtgl patchset is also making great progress in review/development but will also be deferred to M3.
  • We are now running the build performance tests as part of our standard autobuilder which is a further step towards streamlining our testing and release process. We are having some problems with the graphs that are generated in the emails. If anyone has experience or interest in helping with this (google charts in emails) we’d love to hear from you!
  • The perl changes which landed last week seem to have mostly been ok, there have been some race issues and we’re grateful to Alex and the perl-cross upstream for their fast turnaround on those.
  • Further fixes for the gitsm fetcher landed but there are still reports of issues. We continue to try and find ways to expand our test case matrix so we can fix the issues *and* ensure we don’t regress.
  • The latest round of updates from the AUH were sent out. Some have responded to this and sent in upgrades, many have not. If you are listed as a maintainer, please help us keep recipes up to date!

Planned Releases for YP 2.7:

  • YP 2.7 M2 Cutoff is Jan. 21, 2019
  • 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.6.1 (Thud) will is out of QA.
  • 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:

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

Yocto Project Weekly Status January 15, 2019

Current Dev Position: YP 2.7 M2
Next Deadline: YP 2.7 M2 Cutoff is Jan. 21, 2019

SWAT Team Rotation:

Key Status/Updates:

  • YP 2.7 M1 was released on Jan. 10, 2019
  • YP 2.6.1 is in QA and 79% complete. See: https://wiki.yoctoproject.org/wiki/2.6_QA_Status
  • We merged the perl changes and version upgrade. This exposed some race issues but we’re hoping those have now been resolved. Thanks AlexK! This may cause fallout for perl module recipes in other layers.
  • There is a proposed patchset to add GL passthrough support for qemu, feedback on the proposals is welcome. There are build time performance implications, particularly due to the use of gtk3+-native.
  • There is a -dev kernel recipe for the Linux 5.0 kernel, thanks Bruce.
  • M2 cutoff is next week!

Planned Releases for YP 2.7:

  • YP 2.7 M2 Cutoff is Jan. 21, 2019
  • 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.6.1 (Thud) will is in QA.
  • 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:

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

Yocto Project Weekly Status January 8, 2019

Current Dev Position: YP 2.7 M2
Next Deadline: YP 2.7 M2 Cutoff is Jan. 21, 2019

SWAT Team Rotation:

Key Status/Updates:

  • YP 2.7 M1 is out of QA and being prepared for release.
  • YP 2.5.2 was released on Jan. 4, 2019.
  • YP 2.6.1 should build once the current patch queue from Armin has final review and is merged.
  • The hash equivalency server code merged, thanks to Joshua Watt for his patience in working through some of the details with that!
  • Many different patches for upgrades, features and fixes continue to be merged and we should be mostly up to date with incoming patches.
  • There do continue to be intermittent failures on the autobuilder, albeit at lower frequency than previously.
  • The cross-perl patchset from AlexK is building successfully on the autobuilder so others are requested to give feedback as its likely to merge soon based on the test results.

Planned Releases for YP 2.7:

  • YP 2.7 M1 Release should happen shortly.
  • YP 2.7 M2 Cutoff is Jan. 21, 2019
  • 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.6.1 (Thud) will be built soon.
  • 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:

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

Yocto Project Weekly Status January 2, 2019

Current Dev Position: YP 2.7 M1 is in QA
Next Deadline: YP 2.7 M1 Release Target is Dec. 21, 2018

SWAT Team Rotation:

Key Status/Updates:

  • YP 2.7 M1 is in QA and 100% complete. The final report should publish shortly. See: https://wiki.yoctoproject.org/wiki/2.7_QA_Status
  • YP 2.5.2 rc1 in the process of being released. The announcement should come shortly.
  • We realised the toolchain bootstrap process could be simplified with the removal of glibc-initial and gcc-cross-initial. There have been separate emails about this and despite the vacation period, Khem and RP believed them to be ready and good enough to merge. Streamlining this bottleneck in the build has been something we’ve wanted to see for a number of years so its good to get this build time performance boost!
  • Some patches have merged over the holiday period, some have been delayed but master-next should be fairly up to date with current patches
  • The occasional issues in oe-selftest are still occurring unfortunately.
  • The perl upgrade continues to be blocked on the fallout from meta-openembedded and the need to make some final tweaks to the patchset.

Planned Releases for YP 2.7:

  • YP 2.7 M1 is in QA and should be out shortly.
  • YP 2.7 M1 Release Target is Dec. 21, 2018
  • YP 2.7 M2 Cutoff is Jan. 21, 2019
  • 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.2 (Sumo) is out of QA and should release shortly.
  • YP 2.6.1 (Thud) will be targeted after YP 2.7 M1 is done.
  • 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:

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

Personal tools