Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status May 5, 2020 ==
== Yocto Project Weekly Status May 12, 2020 ==
Current Dev Position: YP 3.2 M1 <br/>
Current Dev Position: YP 3.2 M1 <br/>
Next Deadline: YP 3.2 M1 build date 2020/6/16<br/>
Next Deadline: YP 3.2 M1 build date 2020/6/16<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday May 7th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday May 14th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday May 5th at 8am  PDT (https://zoom.us/j/990892712)
*Monthly Project Meeting Tuesday June 2nd at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday May 12th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday May 12th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - See http://www.twitch.tv/letoatreidesthe2nd
*Twitch - See http://www.twitch.tv/letoatreidesthe2nd


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We are now merging patches into master, debugging some of the issues has proven problematic but we’re making good progress on various deferred upgrades.
*Patches continue to merge into master, there have been a number of infrastructure issues and build failures which have delayed some patches until we could get clean builds
*In particular there was a further problem with buildtools-extended-tarball which ended up ‘corrupting’ sstate by over-optimising binaries so they wouldn't run on older CPUs. Fixes for this have merged and we’ll need to release a new buildtools tarball.
*We’re nearly ready to merge gcc 10 to master with some mingw issues being the currently known remaining blocker.
*The 3.1 stable branch has started taking its first rounds of patches, help with review of these would be much appreciated.
*A number of other slightly more invasive changes are merging such as the changing of QA warnings to become errors and changes to the way libva is built. Some further, more invasive changes are in the queue (e.g. image sstate structure) so review of the patch queue by people with interests in these things is appreciated.
*A 3.0 stable build is due as soon as the current patches in review are sorted out.
*We believe autoconf may release a new version soon (the first in a few years) so have worked with autoconf upstream to ensure it should work for us, reporting test results back.
*The multilib issue mentioned in previous status reports and on the architecture list is proving tricky, do we make the invasive changes in master-next for master now they appear to work? Backport to dunfell? Or try and come up with a more invasive core bitbake change?
*YP 3.0.3 will build this week.
*We are aware of some issues with bug trend metrics due to server transitions and are working to resolve those.


'''YP 3.2 Milestone Dates:'''<br/>
'''YP 3.2 Milestone Dates:'''<br/>
Line 42: Line 41:
*WDD 2577 (last week 2577) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2577 (last week 2577) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1353 (last week 1367)
**Total patches found: 1345 (last week 1353)
**Patches in the Pending State: 536 (40%) [last week 540 (40%)]
**Patches in the Pending State: 536 (40%) [last week 536 (40%)]


'''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 14:43, 12 May 2020

Yocto Project Weekly Status May 12, 2020

Current Dev Position: YP 3.2 M1
Next Deadline: YP 3.2 M1 build date 2020/6/16

Next Team Meetings:

Key Status/Updates:

  • Patches continue to merge into master, there have been a number of infrastructure issues and build failures which have delayed some patches until we could get clean builds
  • We’re nearly ready to merge gcc 10 to master with some mingw issues being the currently known remaining blocker.
  • A number of other slightly more invasive changes are merging such as the changing of QA warnings to become errors and changes to the way libva is built. Some further, more invasive changes are in the queue (e.g. image sstate structure) so review of the patch queue by people with interests in these things is appreciated.
  • We believe autoconf may release a new version soon (the first in a few years) so have worked with autoconf upstream to ensure it should work for us, reporting test results back.
  • YP 3.0.3 will build this week.

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • 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.0.3 build date 2020/5/4
  • YP 3.0.3 release date 2020/5/15
  • YP 2.7.4 build date 2020/5/18
  • YP 2.7.4 release date 2020/5/29
  • YP 3.1.1 build date 2020/6/29
  • YP 3.1.1 release date 2020/7/10
  • 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=74293"