Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 10: Line 10:


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1.1 is out from QA and had no defects raised so is likely to be released after review
*YP 3.1.1 was released
*YP 3.2 M1 will be built as soon as we have a clean build run of the currently queued patches. We’ve not seen anything else pending critical to M1.
*YP 3.2 M1 is through QA and awaiting a release decision. The only defects found were two valgrind ptest results so it's likely to release.
*We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
*We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
*There was a key fix to the gitsm fetcher which resolved autobuilder regressions, thanks Paul Barker for helping resolve that at short notice.
*We continue to be concerned about autobuilder stability, we’re continuing to see high numbers of intermittent failures (along with instability in upstream repositories which is now also breaking builds). A list of issues was posted to the OE-Core mailing list, there are other older bugs which have also recurred. We have figured out some fixes but help is urgently needed to bring these to a manageable level.
*There were some important improvements to multiconfig this week so that multiconfig task hashes are correctly accounted for and rebuilt as well as BBMASK being handled correctly in individual multiconfigs, thanks Joshua Watt for those improvements.
*The biggest concern for both LTS and master right now are the intermittent test failures that keep occurring on the infrastructure, we’re struggling to get clean builds of either branch due to these issues. Instability in the upstream distros we run on (which we regularly pull for security updates) are sadly contributing to the issues, seemingly more significantly than usual.
*If anyone has thoughts on attracting and recognising project contributors and contributions, we would be interested in ideas and assistance in that area.
*If anyone has thoughts on attracting and recognising project contributors and contributions, we would be interested in ideas and assistance in that area.
*There remain a large number of bugs that we’d ideally like to fix in 3.2 M2 but they are “unassigned”, there is nobody to work on them. If anyone has time, looking at these bugs would be a great way to help us. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
*There remain a large number of bugs that we’d ideally like to fix in 3.2 M2 but they are “unassigned”, there is nobody to work on them. If anyone has time, looking at these bugs would be a great way to help us. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
*We’re pleased to announce we have a new manual in the Yocto Project documentation ‘bookshelf’ which covers the project’s testing processes and infrastructure including the autobuilder and resulttool. A work-in-progress version of this can be viewed here: https://www.yoctoproject.org/docs/docs_temp/test-manual/test-manual.html. So far, it contains basic information in key areas, we’re happy to take feedback on areas that are missing or need more information and/or take contributions to further extend this work.
*Next week is ELC which is taking place virtually this year and Yocto Project has a presence there. There is also a virtual Yocto Project Developer Day: https://events.linuxfoundation.org/yocto-dev-day-north-america/
*On a positive note, we are looking the closest we’ve ever been to upstream software versions thanks to AUH and work from Alex in particular, the recent AUH reports have been shorter than ever with low numbers of upgrade failures.


'''YP 3.2 Milestone Dates:'''<br/>
'''YP 3.2 Milestone Dates:'''<br/>

Revision as of 14:46, 23 June 2020

Yocto Project Weekly Status June 23, 2020

Current Dev Position: YP 3.2 M2
Next Deadline: YP 3.2 M2 build date 2020/7/27

Next Team Meetings:

Key Status/Updates:

  • YP 3.1.1 was released
  • YP 3.2 M1 is through QA and awaiting a release decision. The only defects found were two valgrind ptest results so it's likely to release.
  • We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
  • We continue to be concerned about autobuilder stability, we’re continuing to see high numbers of intermittent failures (along with instability in upstream repositories which is now also breaking builds). A list of issues was posted to the OE-Core mailing list, there are other older bugs which have also recurred. We have figured out some fixes but help is urgently needed to bring these to a manageable level.
  • If anyone has thoughts on attracting and recognising project contributors and contributions, we would be interested in ideas and assistance in that area.
  • There remain a large number of bugs that we’d ideally like to fix in 3.2 M2 but they are “unassigned”, there is nobody to work on them. If anyone has time, looking at these bugs would be a great way to help us. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • We’re pleased to announce we have a new manual in the Yocto Project documentation ‘bookshelf’ which covers the project’s testing processes and infrastructure including the autobuilder and resulttool. A work-in-progress version of this can be viewed here: https://www.yoctoproject.org/docs/docs_temp/test-manual/test-manual.html. So far, it contains basic information in key areas, we’re happy to take feedback on areas that are missing or need more information and/or take contributions to further extend this work.
  • Next week is ELC which is taking place virtually this year and Yocto Project has a presence there. There is also a virtual Yocto Project Developer Day: https://events.linuxfoundation.org/yocto-dev-day-north-america/
  • On a positive note, we are looking the closest we’ve ever been to upstream software versions thanks to AUH and work from Alex in particular, the recent AUH reports have been shorter than ever with low numbers of upgrade failures.

YP 3.2 Milestone Dates:

  • YP 3.2 M1 should be released shortly.
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.1 was released
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

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

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=76006"