2020 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 March 31, 2020

Current Dev Position: YP 3.1 M4 - Stabilization- Final RC builds
Next Deadline: YP 3.1 M4 build date 3/30/2020

Next Team Meetings:

Key Status/Updates:

  • 3.1 M3 was released
  • The 3.1 rc1 build has not happened yet, the final remaining patches are being worked upon and will be built when the remaining high issues are resolved.
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • The focus is now on stabilizing and bug fixing for the final release
  • We continue to have concerns about the number of autobuilder intermittent failures, particularly with this being an LTS release however the remaining issues are proving hard to reproduce and track down.

Proposed YP 3.1 Milestone Dates

  • 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.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

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 March 24, 2020

Current Dev Position: YP 3.1 M4 - Stabilization
Next Deadline: YP 3.1 M4 build date 3/30/2020

Next Team Meetings:

Key Status/Updates:

  • M3 is through QA and due to be released.
  • The first M4 rc candidate is due to be built on Monday.
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • We’ve uncovered significant issues with the datastore connector approach in tinfoil. There is a proposed fix which effectively rewrites it which is not something undertaken lightly at this point in release but reluctantly, is probably necessary.
  • The focus is now on stabilizing and bug fixing for the final release

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M3 being reviewed for release
  • 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.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

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 March 17, 2020

Current Dev Position: YP 3.1 M4 - Stabilization
Next Deadline: YP 3.1 M4 build date 3/30/2020

Next Team Meetings:

Key Status/Updates:

  • M3 has now been built and is in QA. We are therefore feature frozen.
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • There were logging changes merged to better handle hashequiv and usability concerns, thanks Joshua
  • We have seen a welcome rise in green builds recently although several key intermittent failures have not been addressed. It is crucial for an LTS release we do resolve these.
  • Recipe upgrades are now unlikely to be merged into 3.1 as we focus on stabilizing and bug fixing for the final release

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M3 is in QA
  • 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.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

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 March 10, 2020

Current Dev Position: YP 3.1 M3 - At Feature Freeze, build pending
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • We are now past M3 feature freeze. The blocking issues continue to reduce, thanks to everyone who has contributed fixes. The remaining issues are:
    • continued minor bugs with buildtools tarball integration
    • coreutils ptest blocked on reproducibility issues with gcc-plugins
    • SystemExit() intermittent selftest failure
    • pseudo sysroot high priority bug
  • There are significant changes proposed to bitbake’s logging structure to address concerns raised by hashequiv changes. These are currently in testing and are likely to become part of M3 given the timing, wider review is welcome.
  • Recipe upgrades are now unlikely to be merged into 3.1 as we focus on stabilizing and bug fixing for the release
  • Autobuilder build results continue to be a concern as we’re not getting green builds very often due to multiple varied issues.

Proposed YP 3.1 Milestone Dates

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

Planned upcoming dot releases:

  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

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 March 3, 2020

Current Dev Position: YP 3.1 M3 - At Feature Freeze, build pending
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • YP 2.7.3 and 3.0.2 have been released.
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • We are now past M3 feature freeze. A number of key issues have been addressed, thanks to everyone who contributed:
    • psplash systemd race issues fixed (Thanks Scott)
    • make mips issue root caused and glibc fix pulled in (Thanks Victor/Khem)
    • ltp upgrade resolved (Thanks Petr)
    • util-linux update resolved (Thanks Pierre-Jean)
    • Uninative tumbleweed issue resolved (Thanks Michael)
    • libgpg-error upgrade (Thanks Alex)
  • There were many other fixes and upgrades, thanks all!
  • The remaining issues we need to look at addressing before we build M3 are:
    • bind upgrade (needs libuv maintainer fix and resend from Armin)
    • coreutils ptest blocked on libmodule-build-perl reproducibility issue
    • Locked signature selftest failure
    • SystemExit() intermittent selftest failure
    • pseudo sysroot high priority bug
    • gcc buildtools tarball solution for centos7 support
  • Recipe upgrades are now much less likely to be accepted unless there is a pressing need, ideally these should be held until 3.1 is released and development for 3.2 is started. We do not have a tracking branch for 3.2 as we’d like to focus people on 3.1 right now.
  • Bug metrics are not good with a rise in WDD when typically it should be falling for this point in a release cycle.

Proposed YP 3.1 Milestone Dates

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

Planned upcoming dot releases:

  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

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 February 25, 2020

Current Dev Position: YP 3.1 M3 - At Feature Freeze
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • YP 2.7.3 rc1 is in QA with the report due next week.
  • YP 3.0.2 rc2 was rebuilt to remove a broken bash CVE patch, rc3 had automated QA only and is now due for release.
  • We are now at the date for M3 which is feature freeze. We are not yet in a position where we can build M3 as there are a number of open high blocking bugs but patches will need to start tapering down to bug fix only. More invasive or unplanned features will no longer be accepted.
  • We have a serious issue with hashequiv but a patch in progress for that. There is also a usability issue raised with hashequiv and this can only realistically be fixed in M4, it means changing the UI message handling within bitbake.
  • We continue to see automated test failures with master, most are long standing issues which we’re struggling to resolve. A minority now have had their causes narrowed down or are now reproducible at will which should help but there is concern about the others.
  • Some recent changes like psplash systemd support have introduced a race causing intermittent build failures. We had thought those resolved but they reappeared after merging.
  • Alex Kanavin has quietly but very effectively been fixing ptest failures and we now have only a very small number of non-toolchain tests failing, thanks Alex!
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

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

Planned upcoming dot releases:

  • YP 2.7.3 built and in QA
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 release soon
  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

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 February 18, 2020

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

Next Team Meetings:

Key Status/Updates:

  • The project recently updated its git hosting infrastructure and there were some issues encountered with the cgit http/https repository sharing. Those issues should now be resolved, apologies if they caused issues for anyone. The git:// protocol sharing was unaffected.
  • YP 3.0.2 rc2 is in QA with the report due soon.
  • We continue to see a small number of reproducibility issues with master which need resolving for green builds (in particular gstreamer and perl).
  • A significant memory usage issue was identified during bitbake parsing where memory usage would grow in each parser thread linearly per number of recipes parsed. This would therefore particularly affect large numbers of layers, multilibs and multiconfig. The fix has merged into bitbake along with the corresponding zeus and warrior branches. For one test case it reduced peak memory usage during parsing for 5 multiconfigs from 20GB to 2GB.
  • Warrior patches for 2.7.3 are out for review.
  • With the git infrastructure issue updated, we now have centos8 workers added to the autobuilder.
  • We are making various queued changes to the autobuilder configuration to fix bugs, improve efficiency and test coverage but this may result in some test result instability as we test and resolve issues.
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

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

Planned upcoming dot releases:

  • YP 2.7.3 built and in QA
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

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 February 11, 2020

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

Next Team Meetings:

Key Status/Updates:

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

Proposed YP 3.1 Milestone Dates

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

Planned upcoming dot releases:

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

Tracking Metrics:

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 February 4, 2020

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

Next Team Meetings:

Key Status/Updates:

  • YP 3.1 M2 is due to be released with reservations.
  • There are significant concerns with M2 due to the build build reproducibility failures which continue to cause major problems with master too. These will have to block the M3 build/release.
  • The NPM fetcher rework patches have now merged, we’d like to thank Jean-Marie Lemetayer for his patience whilst they were made into good shape with regression tests, thanks, its a good end result.
  • The host dependencies on makeinfo and pod2man have now been dropped to simplify build dependencies and improve reproducibility.
  • The mpc8315e-rdb machine/BSP has been dropped from meta-yocto-bsp.
  • Build reproducibility issues have been tracked down to a number of causes but many more remain, some with open bugs, some with bugs yet to be filed. Any assistance with reproducibility issues is appreciated as is the major factor blocking patch merging at present.
  • Reproducibility failure debugging has been improved with better integration into the autobuilder to assist with this. Saved problematic output is now saved at: https://autobuilder.yocto.io/pub/repro-fail/
  • Ongoing kernel issues still prevent kernel upgrades merging at present but work on debugging the issues is moving forward (thanks Victor/Cisco in particular)
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • We have created a “documentation” list and a “licensing” list on the yocto project mailing list infrastructure. We believe these topics would benefit from dedicated discussions, the people involved usually aren’t interested in bulk email as would be found on other lists. The new lists can be found at: https://lists.yoctoproject.org/g/licensing/join and https://lists.yoctoproject.org/g/docs/join
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M2 should release shortly
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

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

Tracking Metrics:

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 January 28, 2020

Current Dev Position: YP 3.1 M3
Next Deadline: YP 3.1 M2 in QA - release 1/31/20

Next Team Meetings:

Tip of the Week:

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

Key Status/Updates:

  • YP 3.1 M2 is in QA but has issues with build reproducibility
  • We’re unlikely to rebuild M2 as master has the same issues and they look like they will take a while to resolve.
  • There are now serious problems with the build reproducibility test failures on the autobuilder. We’re not sure why there is a sudden set of problems but they are real issues and causing most builds to fail. The tests will have to be disabled unless they can be resolved quickly. There are fixes merged for the CONFIG_SHELL issue and kbd and patches queued as a potential fix for makeinfo. There are more remaining issues, some have open bugs, others don’t have bugs yet. Help with any of these would be appreciated (or help filing the bugs).
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • We have created a “documentation” list and a “licensing” list on the yocto project mailing list infrastructure. We believe these topics would benefit from dedicated discussions, the people involved usually aren’t interested in bulk email as would be found on other lists. The new lists can be found at: https://lists.yoctoproject.org/g/licensing/join and https://lists.yoctoproject.org/g/docs/join
  • There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
  • We continue to struggle to get clean ‘full’ builds due to the reproducibility issues in particular.
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M2 release date 1/31/2020
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

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

Tracking Metrics:

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 January 21, 2020

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

Next Team Meetings:

Tip of the Week:

  • ‘You can quickly test a change to a recipe on a target by rebuilding it alone, then rsyncing pieces of WORKDIR/image/ or WORKDIR/packages-split/PACKAGENAME/ rather than rebuilding the image (bit of a hack but effective).
  • (anyone with tips they’d like to see here, please send to Stephen or Richard)

Key Status/Updates:

  • YP 3.1 M2 will build shortly, the only remaining blocking issue is the buildtools-extended-tarball fixes which should happen today.
  • Python 2 has been finally removed from OE-Core. This was long scheduled and whilst its causing problems for other layers, we really need to resolve those issues now rather than later in the release cycle so it is the right time to finally do this.
  • Patch merging continues to be making good progress and staying roughly up to date.
  • The patch metrics showed significant improvement this week, partly from continuing work done by Alex Kanavin in keeping things up to date but also from the python2 removal.
  • Bruce is struggling to get the 5.4 kernel to work on all platforms and any help, particularly with MIPS would be much appreciated. This is blocking the kernel updates at this point.
  • We’re starting to see problems as distros enable seccomp in file which then conflicts with our use of pseudo. We need to come up with a better fix but for now, a wrapper script which adds “-S” to the command line for file, injected into PATH is a workaround.
  • There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
  • There is a separate email about buildtools tarballs continuing toolchains to support building on wider combinations of host distros, please see that for more info if interested in this.
  • We continue to struggle to get clean ‘full’ builds.
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • 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/2020
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

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 January 14, 2020

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

Next Team Meetings:

Tip of the Week:

  • ‘oe-pkgdata-browser’ is a new handy small helper UI added by Ross to visualise the pkgdata held within a build.
  • (anyone with tips they’d like to see here, please send to Stephen or Richard)

Key Status/Updates:

  • YP 3.1 M2 is due to be built next week.
  • Patch merging is roughly on track however there are a number of failures identified with key patches (glibc has a prelink issue on mips, python 3.8 upgrade blocked on uid issue, gstreamer meson transition blocked on nodistro failure). Most of these issues are making progress over time.
  • The more worrying aspect is that there are a number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
  • Looking at the build history, “full” images have built cleanly only once in the past month (3 times in the last two months), which is a pretty shocking statistic which summarises the challenges we face there. Most of these are being procrastinated on by the bug owners since we can’t reproduce them at will. We really need help working on these kinds of issues.
  • We have changed the sstate mirrors to be per release, simply to lower the numbers of files in any given sstate directory.
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • 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/2020
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

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 January 7, 2020

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.1 M1 was released.
  • Over the last two weeks there were a number of significant fixes for hash equivalence which should resolve some of the long standing bugs reported here. Some of these fixes may require further architectural tweaks to the codebase but those are cleanups which can happen in due course now the root causes are identified.
  • There are performance issues that remain in hashequivlence but these will be looked at only once the correctness issues and intermittent test failures are addressed.
  • There are some puzzling selftest failures that remain, in particular a locked signatures one which seems to be caused through bad interaction with the hash equivalence code but is intermittent and does not make sense.
  • The patch queue for master should be roughly up to date which some key changes such as the gettext upgrade having merged recently. Some pending changes like the glibc upgrade look problematic.
  • A key functionality change has merged this week where the layout of the sstate directory has changed. This was done to try and improve performance and handle some performance issues where the previous code simply wasn’t scaling. There is no user visible impact but it does mean new sstate will be generated into a new layout and the older sstate will be ignored. The sstate filename length issues should also be addressed by this patchset.
  • Whilst the SWAT process is disbanded, the effect of this is that Richard now has to file the bugs personally. This distracts from other things that could be worked on.
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.
  • 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

Proposed YP 3.1 Milestone Dates

  • 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/2020
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

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

Personal tools