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/>
*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
*YP 3.0.3 is in QA and due out on 21st May
*We’re nearly ready to merge gcc 10 to master with some mingw issues being the currently known remaining blocker.
*Gcc 10 merged to master, with the ‘no-common’ default change disabled for now whilst we address the other gcc 10 issues first, then we’ll loop back to that.
*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 are struggling with autobuilder infrastructure problems, in particular with NFS locking but also with cancelled builds not terminating correctly. These are having a significant negative impact on master and all stable builds and are a significant concern as there is no clear path forward to any resolution.
*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.
*Patches continue to merge into master but at a slower rate than normal. The patch submission rate has dropped slightly which has helped ensure there isn’t a huge backlog.
*YP 3.0.3 will build this week.
*We’re moving the AUH job functionality to the autobuilder and integrating it there which should mean it's easier to reproduce its functionality and allows more people to see what it's doing and work on/with it. This should also reduce hosting costs.


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

Revision as of 14:47, 19 May 2020

Yocto Project Weekly Status May 19, 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:

  • YP 3.0.3 is in QA and due out on 21st May
  • Gcc 10 merged to master, with the ‘no-common’ default change disabled for now whilst we address the other gcc 10 issues first, then we’ll loop back to that.
  • We are struggling with autobuilder infrastructure problems, in particular with NFS locking but also with cancelled builds not terminating correctly. These are having a significant negative impact on master and all stable builds and are a significant concern as there is no clear path forward to any resolution.
  • Patches continue to merge into master but at a slower rate than normal. The patch submission rate has dropped slightly which has helped ensure there isn’t a huge backlog.
  • We’re moving the AUH job functionality to the autobuilder and integrating it there which should mean it's easier to reproduce its functionality and allows more people to see what it's doing and work on/with it. This should also reduce hosting costs.

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 is in QA
  • 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