Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status January 29, 2019 ==
== Yocto Project Weekly Status February 5, 2019 ==
Current Dev Position: YP 2.7 M3 <br/>
Current Dev Position: YP 2.7 M3 <br/>
Next Deadline: YP 2.7 M3 Cutoff is Feb. 25, 2019<br/>
Next Deadline: YP 2.7 M3 Cutoff is Feb. 25, 2019<br/>
Line 5: Line 5:
'''SWAT Team Rotation:'''<br/>
'''SWAT Team Rotation:'''<br/>


*SWAT lead is currently: Armin
*SWAT lead is currently: Anuj  
*SWAT team rotation: Armin -> Anuj on Feb. 1, 2019
*SWAT team rotation: Anuj -> Paul on Feb. 8, 2019
*SWAT team rotation: Anuj -> Paul on Feb. 8, 2019
*SWAT team rotation: Paul -> Ross on Feb. 15, 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/>
*YP 2.6.1 should release this week. The transition to automated QA is raising some questions about test results but we’re working through those.
*YP 2.6.1 was released on Feb. 4, 2019.
*YP 2.7 M2 was built and is in QA and is 8% done.  See: https://wiki.yoctoproject.org/wiki/2.7_QA_Status
*YP 2.7 M2 was built and is in QA and is 79% done.  See: https://wiki.yoctoproject.org/wiki/2.7_QA_Status
*There have been a further round of gitsm fixes (and new test case additions). If anyone is seeing gitsm fetcher issues please report them. There are requests to backport these changes to the stable series. This has risks but people are reporting bugs there so is something we need to consider.
*Some major recipe upgrades merged (glibc, binutils, llvm)
*There has been little follow up from the last round of AUH patches. Please can maintainers work on this and get these submitted!
*Some “prework” patches for various series merged (util-linux, virtgl) but the main series are still pending development or review
*There has been little feedback on the proposed virtgl changes, these will likely merge as no discussion will be taken to mean there are no objections. This will have a performance impact.
*Various ptest-runner and ptest runtime testing integration fixes merged but many problems with the tests remain no volunteers to help resolve issues.
*There have been changes to the way the arm tunes are handled which merged after much discussion. The solution that merged should be safe and uncontroversial but if these do cause problems for anyone, please report ASAP.
*We’re seeing test failures which highlight major problems with the archiver class, in particular the src.rpm component of it. I’ve proposed we remove it, if you do care about it please step up and help fix it else it will be removed. *The src.rpm support is limited anyhow and likely to mislead user expectations so removing it may be a good thing.
*We’re getting much improved results from our automated testing but these are highlighting a number of problems. There is an email about issues found in ptest. The biggest challenge here now is finding people able to step up and help improve things.
*The recipe reporting system integration with the layer index is now complete and available at: https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/. Historical data has not yet been imported to it.
*The project autobuilder is running at slightly reduced capacity (but not functionality) due to hardware failures.
*The project is considering moving its mailing list hosting to groups.io, if anyone has any experience of that, positive or negative please let Michael, Nico and Richard know
*We’re becoming seriously concerned about the lack of response to the last round of AUH patches


'''Planned Releases for YP 2.7:'''<br/>
'''Planned Releases for YP 2.7:'''<br/>
Line 28: Line 31:


'''Planned upcoming dot releases:'''<br/>
'''Planned upcoming dot releases:'''<br/>
*YP 2.6.1 (Thud) will release shortly.
*YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 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.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
Line 34: Line 36:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2393 (last week 2421) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2356 (last week 2393) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1583 (last week 1572)
**Total patches found: 1572 (last week 1583)
**Patches in the Pending State: 677 (43%) [last week 677 (43%)]
**Patches in the Pending State: 678 (43%) [last week 677 (43%)]


'''Key Status Links for YP:'''<br/>
'''Key Status Links for YP:'''<br/>

Revision as of 15:46, 5 February 2019

Yocto Project Weekly Status February 5, 2019

Current Dev Position: YP 2.7 M3
Next Deadline: YP 2.7 M3 Cutoff is Feb. 25, 2019

SWAT Team Rotation:

Key Status/Updates:

  • YP 2.6.1 was released on Feb. 4, 2019.
  • YP 2.7 M2 was built and is in QA and is 79% done. See: https://wiki.yoctoproject.org/wiki/2.7_QA_Status
  • Some major recipe upgrades merged (glibc, binutils, llvm)
  • Some “prework” patches for various series merged (util-linux, virtgl) but the main series are still pending development or review
  • Various ptest-runner and ptest runtime testing integration fixes merged but many problems with the tests remain no volunteers to help resolve issues.
  • We’re seeing test failures which highlight major problems with the archiver class, in particular the src.rpm component of it. I’ve proposed we remove it, if you do care about it please step up and help fix it else it will be removed. *The src.rpm support is limited anyhow and likely to mislead user expectations so removing it may be a good thing.
  • The recipe reporting system integration with the layer index is now complete and available at: https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/. Historical data has not yet been imported to it.
  • The project autobuilder is running at slightly reduced capacity (but not functionality) due to hardware failures.
  • The project is considering moving its mailing list hosting to groups.io, if anyone has any experience of that, positive or negative please let Michael, Nico and Richard know
  • We’re becoming seriously concerned about the lack of response to the last round of AUH patches

Planned Releases for YP 2.7:

  • YP 2.7 M2 is built and in QA.
  • 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.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=47222"