Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status Mar. 1st, 2022 ==
== Yocto Project Weekly Status Mar. 8th, 2022 ==
Current Dev Position: YP 3.5 M4<br/>
Current Dev Position: YP 3.5 M4<br/>
Next Deadline: 4th Apr. 2022 YP 3.5 M4 build<br/>
Next Deadline: 4th Apr. 2022 YP 3.5 M4 build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Mar. 3rd at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday Mar. 10th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Mar. 1st at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Monthly Project Meeting Tuesday Apr. 5th at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Mar. 8th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Mar. 8th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester
*Twitch -  See https://www.twitch.tv/theyoctojester


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We are now at feature freeze for 3.5, our next LTS release
*YP 3.3.5 has been released.
*YP 3.3.5 is out of QA and pending release approval
*YP 3.5 M3 is now in QA
*Inclusive language changes have merged however there are still:
*All of the known disruptive changes for 3.5 should now be merged and we’re looking at stabilizing up to release in around 4 weeks.
**Incompatible license related variable changes
*We do plan to experiment a little with M4 in this cycle by taking low risk upgrades before release as this does tend to help improve the baseline versions in the final release and help reduce our security exposure. Experience shows issues tend to be introduced by feature changes and potentially other code improvements rather than recipe upgrades and that the autobuilder testing generally does a good job of evaluating upgrades.
**Function variable name changes needed
*Help in completing the migration documentation would be much appreciated.
**No migration documentation or documentation of the changes
**No documentation of the bitbake rename code
**No updates to the manual for the variable renames
We do need people to pull things together and finish things off, help in doing that is needed and much appreciated.
*There is a pending patch to warn about old style license identifiers pending in master-next and due to be posted for review. On balance this is probably a good thing to get into the LTS but we’re open to input on that.
*The incompatible license changes will mean anyone using those variables will need to update what they’re doing carefully. Patches in master-next now pass testing and are due to be posted on the mailing list.
*The python build process change to use wheels has merged. That change has caused some disruption but was close enough to being ready it seemed worth making the final push for inclusion.
*The infrastructure move was successful and all services should be restored. There are some networking issues occurring on autobuilder builds which are preventing release builds at this time and are being looked into.
*As such, the M3 release build will likely happen late this week or early next week.
*If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
*If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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
Line 34: Line 25:


'''YP 3.5 Milestone Dates:'''<br/>
'''YP 3.5 Milestone Dates:'''<br/>
*YP 3.5 M3 build date 2022/02/21
*YP 3.5 M3 is in QA
*YP 3.5 M3 Release date 2022/03/04
*YP 3.5 M3 Release date 2022/03/04
*YP 3.5 M4 build date 2022/04/04
*YP 3.5 M4 build date 2022/04/04
Line 40: Line 31:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.3.5 is out of QA
*YP 3.3.5 is released
*YP 3.3.5 Release date 2022/02/25
*YP 3.1.15 build date 2022/03/14
*YP 3.1.15 build date 2022/03/14
*YP 3.1.15 Release date 2022/03/25
*YP 3.1.15 Release date 2022/03/25
Line 52: Line 42:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2679 (last week 2652) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2652 (last week 2679) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*Poky Patch Metrics
**Total patches found: 1202 (last week 1202)
**Total patches found: 1204 (last week 1202)
**Patches in the Pending State: 336 (28%) [last week 334 (28%)]
**Patches in the Pending State: 337 (28%) [last week 336 (28%)]


'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>

Revision as of 16:00, 8 March 2022

Yocto Project Weekly Status Mar. 8th, 2022

Current Dev Position: YP 3.5 M4
Next Deadline: 4th Apr. 2022 YP 3.5 M4 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.3.5 has been released.
  • YP 3.5 M3 is now in QA
  • All of the known disruptive changes for 3.5 should now be merged and we’re looking at stabilizing up to release in around 4 weeks.
  • We do plan to experiment a little with M4 in this cycle by taking low risk upgrades before release as this does tend to help improve the baseline versions in the final release and help reduce our security exposure. Experience shows issues tend to be introduced by feature changes and potentially other code improvements rather than recipe upgrades and that the autobuilder testing generally does a good job of evaluating upgrades.
  • Help in completing the migration documentation would be much appreciated.
  • If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
  • Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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

Ways to contribute:

YP 3.5 Milestone Dates:

  • YP 3.5 M3 is in QA
  • YP 3.5 M3 Release date 2022/03/04
  • YP 3.5 M4 build date 2022/04/04
  • YP 3.5 M4 Release date 2022/04/29

Upcoming dot releases:

  • YP 3.3.5 is released
  • YP 3.1.15 build date 2022/03/14
  • YP 3.1.15 Release date 2022/03/25
  • YP 3.4.3 build date 2022/03/21
  • YP 3.4.3 Release date 2022/04/01
  • YP 3.3.6 build date 2022/03/28
  • YP 3.3.6 Release date 2022/04/08
  • YP 3.1.16 build date 2022/04/25
  • YP 3.1.16 Release date 2022/05/06

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