Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status December 18, 2018 ==
== Yocto Project Weekly Status January 2, 2019 ==
Current Dev Position: YP 2.7 M1 is in QA <br/>
Current Dev Position: YP 2.7 M1 is in QA <br/>
Next Deadline: YP 2.7 M1 Release Target is Dec. 21, 2018<br/>
Next Deadline: YP 2.7 M1 Release Target is Dec. 21, 2018<br/>
Line 5: Line 5:
'''SWAT Team Rotation:'''<br/>
'''SWAT Team Rotation:'''<br/>


*SWAT lead is currently: Armin
*SWAT lead is currently: Amanda
*SWAT team rotation: Armin -> Anuj on Dec. 21, 2018
*SWAT team rotation: Amanda -> Paul on Jan. 4, 2019
*SWAT team rotation: Anuj -> Paul on Nov. 28, 2018
*SWAT team rotation: Paul -> Ross on Jan. 11, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*The next status report will be published on 2019/1/2 as we expect things to slow down over the holiday season in many locations.
*YP 2.7 M1 is in QA and 100% complete.  The final report should publish shortly.  See: https://wiki.yoctoproject.org/wiki/2.7_QA_Status
*YP 2.5.2 rc1 is out of QA and should release today or tomorrow.
*YP 2.5.2 rc1 in the process of being released.  The announcement should come shortly.
*YP 2.7 M1 is in QA.
*We realised the toolchain bootstrap process could be simplified with the removal of glibc-initial and gcc-cross-initial. There have been separate emails about this and despite the vacation period, Khem and RP believed them to be ready and good enough to merge. Streamlining this bottleneck in the build has been something we’ve wanted to see for a number of years so its good to get this build time performance boost!
*The distrodata bbclass in OE-Core is being removed since the tinfoil API provides a much better way to handle this kind of issue/data.
*Some patches have merged over the holiday period, some have been delayed but master-next should be fairly up to date with current patches
*We discovered potential hash collision issues with some of bitbake’s caching of objects so we are likely going to change to use sha256 everywhere including for sstate objects.
*The occasional issues in oe-selftest are still occurring unfortunately.
*There are occasional issues continuing in oe-selftest which we’re struggling to get to the bottom of unfortunately.
*The perl upgrade continues to be blocked on the fallout from meta-openembedded and the need to make some final tweaks to the patchset.
*There are some patches like the perl upgrade which are blocked on merging due to limited help in fixing fallout from them in layers like meta-openembedded. Khem in particular does a great job but we can’t rely on him alone.


'''Planned Releases for YP 2.6:'''<br/>
'''Planned Releases for YP 2.6:'''<br/>

Revision as of 15:47, 2 January 2019

Yocto Project Weekly Status January 2, 2019

Current Dev Position: YP 2.7 M1 is in QA
Next Deadline: YP 2.7 M1 Release Target is Dec. 21, 2018

SWAT Team Rotation:

Key Status/Updates:

  • YP 2.7 M1 is in QA and 100% complete. The final report should publish shortly. See: https://wiki.yoctoproject.org/wiki/2.7_QA_Status
  • YP 2.5.2 rc1 in the process of being released. The announcement should come shortly.
  • We realised the toolchain bootstrap process could be simplified with the removal of glibc-initial and gcc-cross-initial. There have been separate emails about this and despite the vacation period, Khem and RP believed them to be ready and good enough to merge. Streamlining this bottleneck in the build has been something we’ve wanted to see for a number of years so its good to get this build time performance boost!
  • Some patches have merged over the holiday period, some have been delayed but master-next should be fairly up to date with current patches
  • The occasional issues in oe-selftest are still occurring unfortunately.
  • The perl upgrade continues to be blocked on the fallout from meta-openembedded and the need to make some final tweaks to the patchset.

Planned Releases for YP 2.6:

  • YP 2.7 M1 Cutoff is in QA.
  • YP 2.7 M1 Release Target is Dec. 21, 2018
  • YP 2.7 M2 Cutoff is Jan. 21, 2019
  • YP 2.7 M2 Release Target is Feb. 1, 2019
  • YP 2.7 M3 Cutoff is Feb. 25, 2019
  • YP 2.7 M3 Release Target is Mar. 8, 2019
  • YP 2.7 M4 Cutoff is Apr. 1, 2019
  • YP 2.7 M4 Release Target is Apr. 26, 2019

Planned upcoming dot releases:

  • YP 2.5.2 (Sumo) is out of QA and should release shortly.
  • YP 2.6.1 (Thud) will be targeted after YP 2.7 M1 is done.
  • YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
  • YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
  • YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

Tracking Metrics:

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=45682"