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 are now close to building YP 3.3 rc1 for the final release. That build may happen later today if three are no more urgent pending changes. The biggest blockers on release may be the changelog/release notes and migration guide as those have not been started yet.
*YP 3.3 rc2 has a clean bill of health from QA so pending TSC approval and release notes/migration guide, it's looking likely to release. rc1 was abandoned due to a couple of intermittent autobuilder issues accounted on the first build.
*YP 3.2.3 was released.
*YP 3.1.7 is being built today
*We did merge a change to oeqa/runqemu to allow the qemu images to be run from a tmpfs. This should mean writes aren’t held up in the IO queue which we believe may have been a cause of the intermittent failures. Unfortunately we can’t use cgroups as the versions on most of the autobuilder workers isn’t recent enough for IO priorities, even ignoring the permission issues so this tmpfs solution seemed like the best option and was not very invasive to implement. It does mean we now see the “qemu didn’t start in 120s” error instead much more regularly if the copy into tmpfs is locked.
*There are a number of pending patches queued in master-next waiting for 3.4 to open for development.
*There are a number of patches queued in master-next but most are version upgrades which will wait for 3.4 to open for development.
*We do have some development series undergoing review now such as the PRServ rework and changes to the git fetcher to make it more efficient.
*Intermittent autobuilder issues continue to occur and are now at a record high level. 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 are working to identify the load pattern on the infrastructure that seems to trigger these.
*Intermittent autobuilder issues continue to occur and are now at a record high level. 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 are working to identify the load pattern on the infrastructure that seems to trigger these.


Line 23: Line 23:
'''YP 3.3 Milestone Dates:'''<br/>
'''YP 3.3 Milestone Dates:'''<br/>
*YP 3.3 M4 is out of QA.
*YP 3.3 M4 is out of QA.
'''YP 3.4 Milestone Dates:'''<br/>
*YP 3.4 M1 build date 2021/06/07
*YP 3.4 M1 Release date 2021/06/18
*YP 3.4 M2 build date 2021/07/12
*YP 3.4 M2 Release date 2021/07/23
*YP 3.4 M3 build date 2021/08/23
*YP 3.4 M3 Release date 2021/09/03
*YP 3.4 M4 build date 2021/10/04
*YP 3.4 M4 Release date 2021/10/29


'''Planned upcoming dot releases:'''<br/>
'''Planned upcoming dot releases:'''<br/>
*YP 3.2.3 has been released.
*YP 3.1.7 is being built.
*YP 3.1.7 build date 2021/03/29
*YP 3.1.7 release date 2021/04/09
*YP 3.1.7 release date 2021/04/09
*YP 3.2.4 build date 2021/05/3
*YP 3.2.4 build date 2021/05/3
Line 32: Line 41:
*YP 3.1.8 build date 2021/05/17
*YP 3.1.8 build date 2021/05/17
*YP 3.1.8 release date 2021/05/28
*YP 3.1.8 release date 2021/05/28
*YP 3.3.1 build date 2021/05/24
*YP 3.3.1 release date 2021/06/04
*YP 3.1.9 build date 2021/06/21
*YP 3.1.9 release date 2021/07/02
*YP 3.1.10 build date 2021/07/26
*YP 3.1.10 release date 2021/08/06
*YP 3.3.2 build date 2021/08/09
*YP 3.3.2 release date 2021/08/20
*YP 3.1.11 build date 2021/09/13
*YP 3.1.11 release date 2021/9/24


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>

Revision as of 14:38, 13 April 2021

Yocto Project Weekly Status Apr. 13, 2021

Current Dev Position: YP 3.3 M4 (Feature Freeze)
Next Deadline: 5th April 2021 YP 3.3 M4 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.3 rc2 has a clean bill of health from QA so pending TSC approval and release notes/migration guide, it's looking likely to release. rc1 was abandoned due to a couple of intermittent autobuilder issues accounted on the first build.
  • YP 3.1.7 is being built today
  • There are a number of pending patches queued in master-next waiting for 3.4 to open for development.
  • We do have some development series undergoing review now such as the PRServ rework and changes to the git fetcher to make it more efficient.
  • Intermittent autobuilder issues continue to occur and are now at a record high level. 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 are working to identify the load pattern on the infrastructure that seems to trigger these.

Ways to contribute:

YP 3.3 Milestone Dates:

  • YP 3.3 M4 is out of QA.

YP 3.4 Milestone Dates:

  • YP 3.4 M1 build date 2021/06/07
  • YP 3.4 M1 Release date 2021/06/18
  • YP 3.4 M2 build date 2021/07/12
  • YP 3.4 M2 Release date 2021/07/23
  • YP 3.4 M3 build date 2021/08/23
  • YP 3.4 M3 Release date 2021/09/03
  • YP 3.4 M4 build date 2021/10/04
  • YP 3.4 M4 Release date 2021/10/29

Planned upcoming dot releases:

  • YP 3.1.7 is being built.
  • YP 3.1.7 release date 2021/04/09
  • YP 3.2.4 build date 2021/05/3
  • YP 3.2.4 release date 2021/05/14
  • YP 3.1.8 build date 2021/05/17
  • YP 3.1.8 release date 2021/05/28
  • YP 3.3.1 build date 2021/05/24
  • YP 3.3.1 release date 2021/06/04
  • YP 3.1.9 build date 2021/06/21
  • YP 3.1.9 release date 2021/07/02
  • YP 3.1.10 build date 2021/07/26
  • YP 3.1.10 release date 2021/08/06
  • YP 3.3.2 build date 2021/08/09
  • YP 3.3.2 release date 2021/08/20
  • YP 3.1.11 build date 2021/09/13
  • YP 3.1.11 release date 2021/9/24

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