Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(522 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status March, 26, 2019 ==
== Yocto Project Weekly Status April 30th, 2024 ==
Current Dev Position: YP 2.7 M3 <br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: YP 2.7 M3 Release Target was Mar. 8, 2019<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday May 2nd at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday April 30th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester


*SWAT lead is currently: Paul
'''Key Status/Updates:'''<br/>
*SWAT team rotation: Paul -> Ross on Mar. 30, 2019
*YP 5.0 has been released!
*SWAT team rotation: Ross -> Amanda on Apr. 5, 2019
*Huge thanks to everyone who contributed to 5.0
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*YP 3.1.33 has passed QA and is due to release
*YP 4.0.18 is in QA.
*Updates to graphing on the patch/CVE metrics page merged
*There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990 Please consider signing this to show support for those changes, which would improve our ability to analyze CVEs, and that of many other projects (including other distros) to do so too.
*We continue to watch the NIST NVD (CVE database) situation, the lack of CPE information is problematic for us and we are considering what alternatives we have. The CVE Project announced support for more information fields on CVEs which is a good start.
*Some CVE information is being provided for issues in meta-openembedded, this has been provided with help from the Sovereign Tech Fund.
*The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date.
*There are proposals on the openembedded-architecture list to rework how do_unpack works, switching it from WORKDIR to a new variable and changing some directory layout.
 
 
'''Ways to contribute:'''<br/>
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There are bugs that are currently unassigned for YP 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_Unassigned_Enhancements/Bugs
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
*Help us resolve CVE issues: CVE metrics
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''Key Status/Updates:'''<br/>
*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:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 2.7 M3 Cutoff was Feb. 25, 2019
*YP 5.1 M1 Build date 2024-05-20
*YP 2.7 M3 Release Target was Mar. 8, 2019
*YP 5.1 M1 Release date 2024-05-31
*YP 2.7 M4 Cutoff is Apr. 1, 2019
*YP 5.1 M2 Build date 2024-07-08
*YP 2.7 M4 Release Target is Apr. 26, 2019
*YP 5.1 M2 Release date 2024-07-19
*YP 5.1 M3 Build date 2024-08-26
*YP 5.1 M3 Release date 2024-09-06
*YP 5.1 M4 Build date 2024-09-30
*YP 5.1 M4 Release date 2024-10-25


'''Planned upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 2.5.3 (Sumo) will be targeted for build as soon as it is ready..
*YP 3.1.33 is in QA
*YP 2.6.2 (Thud) will be targeted after YP 2.5.3 is done.
*YP 4.0.18 is in QA
*YP 4.0.18 Release date 2024-05-03
*YP 5.0.1 Build Date 2024-05-13
*YP 5.0.1 Release Date 2024-05-24
*YP 4.0.19 build date 2024-06-03
*YP 4.0.19 Release date 2024-06-14
*YP 5.0.2 Build Date 2024-06-24
*YP 5.0.2 Release Date 2024-07-05
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.20 Release Date 2024-07-26
*YP 5.0.3 Build Date 2024-08-12
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.21 Build Date 2024-09-09
*YP 4.0.21 Release Date 2024-09-20
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.22 Release Date 2024-10-25
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.23 Release Date 2024-11-29


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2418 (last week 2432) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2728 (last week 2714) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1538 (last week 1526)
**Total patches found: 1125 (last week 1140)
**Patches in the Pending State: 656 (43%) [last week 656 (43%)]
**Patches in the Pending State: 221 (20%) [last week 245 (21%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''Key Status Links for YP:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features<br/>


== Archives ==
== Archives ==
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]

Latest revision as of 14:47, 30 April 2024

Yocto Project Weekly Status April 30th, 2024

Current Dev Position: YP 5.1 M1
Next Deadline: YP 5.1 M1 Build 20 May 2024

Next Team Meetings:

Key Status/Updates:

  • YP 5.0 has been released!
  • Huge thanks to everyone who contributed to 5.0
  • YP 3.1.33 has passed QA and is due to release
  • YP 4.0.18 is in QA.
  • Updates to graphing on the patch/CVE metrics page merged
  • There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990 Please consider signing this to show support for those changes, which would improve our ability to analyze CVEs, and that of many other projects (including other distros) to do so too.
  • We continue to watch the NIST NVD (CVE database) situation, the lack of CPE information is problematic for us and we are considering what alternatives we have. The CVE Project announced support for more information fields on CVEs which is a good start.
  • Some CVE information is being provided for issues in meta-openembedded, this has been provided with help from the Sovereign Tech Fund.
  • The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date.
  • There are proposals on the openembedded-architecture list to rework how do_unpack works, switching it from WORKDIR to a new variable and changing some directory layout.


Ways to contribute:


YP 5.1 Milestone Dates:

  • YP 5.1 M1 Build date 2024-05-20
  • YP 5.1 M1 Release date 2024-05-31
  • YP 5.1 M2 Build date 2024-07-08
  • YP 5.1 M2 Release date 2024-07-19
  • YP 5.1 M3 Build date 2024-08-26
  • YP 5.1 M3 Release date 2024-09-06
  • YP 5.1 M4 Build date 2024-09-30
  • YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

  • YP 3.1.33 is in QA
  • YP 4.0.18 is in QA
  • YP 4.0.18 Release date 2024-05-03
  • YP 5.0.1 Build Date 2024-05-13
  • YP 5.0.1 Release Date 2024-05-24
  • YP 4.0.19 build date 2024-06-03
  • YP 4.0.19 Release date 2024-06-14
  • YP 5.0.2 Build Date 2024-06-24
  • YP 5.0.2 Release Date 2024-07-05
  • YP 4.0.20 Build Date 2024-07-15
  • YP 4.0.20 Release Date 2024-07-26
  • YP 5.0.3 Build Date 2024-08-12
  • YP 5.0.3 Release Date 2024-08-23
  • YP 4.0.21 Build Date 2024-09-09
  • YP 4.0.21 Release Date 2024-09-20
  • YP 5.0.4 Build Date 2024-09-23
  • YP 5.0.4 Release Date 2024-10-04
  • YP 4.0.22 Build Date 2024-10-14
  • YP 4.0.22 Release Date 2024-10-25
  • YP 5.0.5 Build Date 2024-11-11
  • YP 5.0.5 Release Date 2024-11-22
  • YP 4.0.23 Build Date 2024-11-18
  • YP 4.0.23 Release Date 2024-11-29

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=86324"