Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status February 4, 2020 ==
== Yocto Project Weekly Status February 11, 2020 ==
Current Dev Position: YP 3.1 M3 <br/>
Current Dev Position: YP 3.1 M3 <br/>
Next Deadline: YP 3.1 M3 build date 2/24/2020<br/>
Next Deadline: YP 3.1 M3 build date 2/24/2020<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Feb. 6th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday Feb. 13th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday  Fab. 4th at 8am  PDT (https://zoom.us/j/990892712)
*Monthly Project Meeting Tuesday  Mar. 3rd at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Feb. 11th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Feb. 11th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - Next event is Tuesday Feb. 11th at 8am PDT (https://www.twitch.tv/yocto_project)
*Twitch - Next event is Tuesday Feb. 11th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1 M2 is due to be released with reservations.
*YP 3.1 M2 was released
*There are significant concerns with M2 due to the build reproducibility failures which continue to cause major problems with master too. These will have to block the M3 build/release.
*We’re now in a much better position with reproducibility issues after around 20 patches merged addressing various problems. Some issues still remain but the bulk of the issues appear to be under control now.
*The NPM fetcher rework patches have now merged, we’d like to thank Jean-Marie Lemetayer for his patience whilst they were made into good shape with regression tests, thanks, its a good end result.
*Due to the number and type of fixes found, the 3.0.2 rc1 build will be abandoned and rc2 built with the reproducibility fixes (as well as additional hashserv/multiconfig fixes). This delays 3.0.2 by a week but for a reasonable set of improvements.
*The host dependencies on makeinfo and pod2man have now been dropped to simplify build dependencies and improve reproducibility.
*YP 3.0.2 should therefore enter QA within the next day or so.
*The mpc8315e-rdb machine/BSP has been dropped from meta-yocto-bsp.
*Review of newly queued warrior (2.7.3) patches will happen later this week once 3.0.2 is in QA.
*Build reproducibility issues have been tracked down to a number of causes but many more remain, some with open bugs, some with bugs yet to be filed. Any assistance with reproducibility issues is appreciated as is the major factor blocking patch merging at present.
With the new fixes and a small fix to the autobuilder code, we managed the first green “full” build in nearly three months.
*Reproducibility failure debugging has been improved with better integration into the autobuilder to assist with this. Saved problematic output is now saved at: https://autobuilder.yocto.io/pub/repro-fail/
*The incoming patch queue is roughly under control again
*Ongoing kernel issues still prevent kernel upgrades merging at present but work on debugging the issues is moving forward (thanks Victor/Cisco in particular)
*We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
*We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
*We have created a “documentation” list and a “licensing” list on the yocto project mailing list infrastructure. We believe these topics would benefit from dedicated discussions, the people involved usually aren’t interested in bulk email as would be found on other lists. The new lists can be found at: https://lists.yoctoproject.org/g/licensing/join and https://lists.yoctoproject.org/g/docs/join
*One worrying metric is that the WDD is now on level with the high of 2017 so our worst defect weighting in two years. This is sadly unsurprising and directly correlated to a lack of participation in the triage process and a lack of people working on general bug fixing.
*The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.
*The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Proposed YP 3.1 Milestone Dates'''<br/>
*YP 3.1 M2 should release shortly
*YP 3.1 M3 build date 2/24/2020
*YP 3.1 M3 build date 2/24/2020
*YP 3.1 M3 release date 3/6/2020
*YP 3.1 M3 release date 3/6/2020
Line 36: Line 34:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2767 (last week 2765) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2728 (last week 2767) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1368 (last week 1368)
**Total patches found: 1361 (last week 1368)
**Patches in the Pending State: 544 (40%) [last week 545 (40%)]
**Patches in the Pending State: 547 (40%) [last week 544 (40%)]


'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>

Revision as of 15:50, 11 February 2020

Yocto Project Weekly Status February 11, 2020

Current Dev Position: YP 3.1 M3
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • YP 3.1 M2 was released
  • We’re now in a much better position with reproducibility issues after around 20 patches merged addressing various problems. Some issues still remain but the bulk of the issues appear to be under control now.
  • Due to the number and type of fixes found, the 3.0.2 rc1 build will be abandoned and rc2 built with the reproducibility fixes (as well as additional hashserv/multiconfig fixes). This delays 3.0.2 by a week but for a reasonable set of improvements.
  • YP 3.0.2 should therefore enter QA within the next day or so.
  • Review of newly queued warrior (2.7.3) patches will happen later this week once 3.0.2 is in QA.

With the new fixes and a small fix to the autobuilder code, we managed the first green “full” build in nearly three months.

  • The incoming patch queue is roughly under control again
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • One worrying metric is that the WDD is now on level with the high of 2017 so our worst defect weighting in two years. This is sadly unsurprising and directly correlated to a lack of participation in the triage process and a lack of people working on general bug fixing.
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 build date 2/10/2020
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

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