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/>
*We will build the first release candidate build for YP 4.0 (3.5) later today.
*The next release, kirkstone will be 4.0 (previously known as 3.5) and will be bitbake 2.0 based.
*YP 3.4.3 was released
*The first release candidate build for YP 4.0 (3.5) is in QA but has at least one issue which will mean we need a second release candidate build. We will build that after the final QA report is back.
*YP 3.3.6, the final hardknott release will build after 4.0 rc1.
*YP 3.3.6, the final hardknott release will build after 4.0 rc2.
*We’re planning to take a couple of further changes (pseudo fix, apt signing minus the test and the unwind sdl workaround) and then call the first release candidate build good.
*There are several issues which have arisen in the last week which mean we will need a second release candidate build:
*There were a number of good fixes for memory resident bitbake this week and also some interesting and useful fixes for the bitbake parsing process which should avoid lockups in the error case. The hope is these should avoid some of the intermittent issues we’ve been seeing on the autobuilder.
**edgerouter didn’t boot with rc1 due to a kernel patch issue
*An issue with make 4.2.1 on some distros remains, often causing hangs in kernel and perl builds in particular. Help in developing a workaround for this (a make buildtools tarball?) would be appreciated.
**uninative didn’t work with libstdc++ from gcc 12 so we have an upgraded version
**there were several CVE fixes that came in (libarchive, gzip, xz)
**a key intermittent autobuilder fix was identified
Not all of these were release blockers but together they mean an rc2 is appropriate.
*If anyone is aware of other issues in rc1 that need to be addressed in rc2, please let us know ASAP.
*YP 4.1 planning document is available for review at: https://docs.google.com/document/d/1-g7DatSdmIETwD3xFSCxV7MbWVVkpQvQ788mIr1MPTI/edit?usp=sharing
*YP 4.1 planning document is available for review at: https://docs.google.com/document/d/1-g7DatSdmIETwD3xFSCxV7MbWVVkpQvQ788mIr1MPTI/edit?usp=sharing
*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.

Revision as of 14:45, 12 April 2022

Yocto Project Weekly Status Apr. 12th, 2022

Current Dev Position: YP 4.1 M1
Next Deadline: 30th May 2022 YP 4.1 M1 build

Next Team Meetings:

Key Status/Updates:

  • The next release, kirkstone will be 4.0 (previously known as 3.5) and will be bitbake 2.0 based.
  • The first release candidate build for YP 4.0 (3.5) is in QA but has at least one issue which will mean we need a second release candidate build. We will build that after the final QA report is back.
  • YP 3.3.6, the final hardknott release will build after 4.0 rc2.
  • There are several issues which have arisen in the last week which mean we will need a second release candidate build:
    • edgerouter didn’t boot with rc1 due to a kernel patch issue
    • uninative didn’t work with libstdc++ from gcc 12 so we have an upgraded version
    • there were several CVE fixes that came in (libarchive, gzip, xz)
    • a key intermittent autobuilder fix was identified

Not all of these were release blockers but together they mean an rc2 is appropriate.

  • If anyone is aware of other issues in rc1 that need to be addressed in rc2, please let us know ASAP.
  • YP 4.1 planning document is available for review at: https://docs.google.com/document/d/1-g7DatSdmIETwD3xFSCxV7MbWVVkpQvQ788mIr1MPTI/edit?usp=sharing
  • 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 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 We did work out the cause of the infamous tinfoil wait_event intermittent issue.

Ways to contribute:

YP 4.0 Milestone Dates:

  • YP 4.0 is in QA
  • YP 4.0 M4 Release date 2022/04/29

YP 4.1 Milestone Dates:

  • YP 4.1 M1 build date 2022/05/30
  • YP 4.1 M1 Release date 2022/06/10
  • YP 4.1 M2 build date 2022/07/11
  • YP 4.1 M2 Release date 2022/07/22
  • YP 4.1 M3 build date 2022/08/22
  • YP 4.1 M3 Release date 2022/09/02
  • YP 4.1 M4 build date 2022/10/03
  • YP 4.1 M4 Release date 2022/10/28

Upcoming dot releases:

  • 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
  • YP 3.4.4 build date 2022/05/02
  • YP 3.4.4 Release date 2022/05/13
  • YP 4.0.1 build date 2022/05/16
  • YP 4.0.1 Release date 2022/05/27
  • YP 3.1.17 build date 2022/06/06
  • YP 3.1.17 Release date 2022/06/17
  • YP 4.0.2 build date 2022/06/27
  • YP 4.0.2 Release date 2022/07/08
  • YP 3.1.18 build date 2022/07/18
  • YP 3.1.18 Release date 2022/07/29
  • YP 4.0.3 build date 2022/08/08
  • YP 4.0.3 Release date 2022/08/19
  • YP 3.1.19 build date 2022/08/29
  • YP 3.1.19 Release date 2022/09/09
  • YP 4.0.4 build date 2022/09/19
  • YP 4.0.4 Release date 2022/09/30
  • YP 3.1.20 build date 2022/10/10
  • YP 3.1.20 Release date 2022/10/21
  • YP 4.0.5 build date 2022/10/31
  • YP 4.0.5 Release date 2022/11/11

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