Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
No edit summary
Line 72: Line 72:


Tracking Metrics: WDD 2672 (last week 2700)
Tracking Metrics: WDD 2672 (last week 2700)
(https://wiki.yoctoproject.org/charts/combo.html)
Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
== Yocto Project Weekly Status Jan. 8, 2018 ==
Current Dev Position: YP 2.5 M2 development
Next Deadline: YP 2.5 M2 cut off of 1/15/18
SWAT team rotation: Cal -> Joshua on Jan. 5, 2018.
SWAT team rotation: Joshua -> Armin on Jan. 12, 2018.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
• 2.3.3 and 2.4.1 are likely due to imminently release, we tracked down the performance regressions to some kind of infrastructure issue which is still being investigated.
• The automated testing issues have mostly been resolved now and this has meant we’ve run a series of builds for master and the stable release branches. As such, the backlog of patches against morty, pyro, rocko and master are substantially reduced after this weekend.
• Armin’s help with the stable patch queues is much appreciated.
• Due to testing problems with 2.5 M1 rc1, particular from the qemu APIC hangs, we have put a new build, rc3 into QA. The QA of YP 2.5 M1 rc3 is about 2% complete.  See: https://wiki.yoctoproject.org/wiki/2.5_QA_Status
• We’re aware there are some serious security issues around at the moment. We’ve been stalled partly as maintainers are returning from vacation, partly as fixes are only now becoming available. As fixes are available we will waterfall these into the branches. One of the reasons we’ve focused on clearing the other patches queued is so we can quickly test and merge these and then proceed with another set of point releases.
Planned upcoming dot releases:
YP 2.4.1 (Rocko) rc1 is out of QA, and should be released this week.
YP 2.3.3 (Pyro) rc1 is out of QA, and should be released this week.
YP 2.2.3 (Morty) rc1 is in QA, see https://wiki.yoctoproject.org/wiki/2.2_QA_Status.
Key YP 2.5 Dates are:
YP 2.5 M1 rc1 is in QA, see above link.
YP 2.5 M2 cut off of 1/15/18
YP 2.5 M2 release of 1/26/18
YP 2.5 M3 cut off of 2/19/18
YP 2.5 M3 release of 3/2/18
YP 2.5 M4 cut off of 4/2/18
YP 2.5 M4 release of 4/27/18
Tracking Metrics:
            WDD 2700 (last week 2764)
(https://wiki.yoctoproject.org/charts/combo.html)
(https://wiki.yoctoproject.org/charts/combo.html)



Revision as of 15:33, 29 January 2018

Yocto Project Weekly Status Jan. 22, 2018

Current Dev Position: YP 2.5 M2 development Next Deadline: YP 2.5 M2 cut off was 1/15/18

SWAT team rotation: Armin -> Ross on Jan. 19, 2018. SWAT team rotation: Ross -> Juro on Jan. 26, 2018. https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates: YP 2.5 M1 rc3 is out of QA and should be released imminently. There were some minor issues but we’ll address these as part of M2. See: https://wiki.yoctoproject.org/wiki/WW03_-_2018-1-18-_Full_Test_Cycle_-_2.5_M1_rc3 and see: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status#Milestone_1_-_Target_Dec._15.2C_2017 With a round of security released fixes likely to land shortly, we’ll likely wait for these before we roll M2. The Automatic Upgrade Helper (AUH) ran, now based on devtool functionality and testing against a wider set of architectures and build options. This looks likely to easy recipe maintenance and increase productivity for people and I’d like to thank Alex for his work on this. There is much it could do better but it is continuing to evolve and become easier to use which is great to see. The AUH emails have triggered a good batch of recipe upgrades. QEMU was also upgraded (which can often cause problems). I sent out a separate summary of changes which are happening to the Autobuilder, people on the SWAT team need to be especially aware of this http://lists.openembedded.org/pipermail/openembedded-architecture/2018-January/000694.html The long queued python recipe changes including its manifest have landed. We tested this as far as we could in core and I know there is some fall out in other layers, help and patience to work through the issues is appreciated. Patches pending against the python recipes will need to be rebased and resent. There have been some significant changes to cmake, ninja and meson and meson is now the default for some recipes. There were some significant gettext cleanups.

Planned upcoming dot releases: YP 2.4.2 (Rocko) will be built when a stable version of the spectre/meltdown patches are ready. YP 2.3.4 (Pyro) will be built when a stable version of the spectre/meltdown patches are ready. YP 2.2.3 (Morty) rc1 is in QA, see https://wiki.yoctoproject.org/wiki/2.2_QA_Status. This will not contain the spectre/meltdown patches as they’re not ready yet.

Key YP 2.5 Dates are: YP 2.5 M2 cut off is past, it should be built as soon as a decision on the spectre/meltdown patches is made. YP 2.5 M2 release of 1/26/18 YP 2.5 M3 cut off of 2/19/18 YP 2.5 M3 release of 3/2/18 YP 2.5 M4 cut off of 4/2/18 YP 2.5 M4 release of 4/27/18

Tracking Metrics: WDD 2657 (last week 2672) (https://wiki.yoctoproject.org/charts/combo.html)

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

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

Yocto Project Status Jan. 16, 2018

Current Dev Position: YP 2.5 M2 development Next Deadline: YP 2.5 M2 cut off was 1/15/18

SWAT team rotation: Joshua -> Armin on Jan. 12, 2018. SWAT team rotation: Armin -> Ross on Jan. 19, 2018. https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates: • 2.3.3 and 2.4.1 were released. These releases do not contain spectre/meltdown patches/fixes as those are still being worked on and haven’t merged yet. • We are mostly up to date with patch queues although there are some bigger series which are still being tested/reviewed and are still pending • Due to testing problems with 2.5 M1 rc3, it is still undergoing QA testing and is 90% complete. We are continuing to have some QA transition/infrastructure issues. See: https://wiki.yoctoproject.org/wiki/2.5_QA_Status. • A separate update on the spectre/meltdown status and the project has been sent out to the oe-core mailing list.

Planned upcoming dot releases: YP 2.4.2 (Rocko) will be built when a stable version of the spectre/meltdown patches has been proven ready. YP 2.3.4 (Pyro) will be built when a stable version of the spectre/meltdown patches has been proven ready. YP 2.2.3 (Morty) rc1 is in QA, see https://wiki.yoctoproject.org/wiki/2.2_QA_Status. We are considering holding this release candidate and building another when a stable version of the spectre/meltdown patches has been proven ready.

Key YP 2.5 Dates are: YP 2.5 M1 rc3 is in QA, see above link. YP 2.5 M2 cut off is past, it should be built as soon as the spectre/meltdown patches are ready and have been proven ready. YP 2.5 M2 release of 1/26/18 YP 2.5 M3 cut off of 2/19/18 YP 2.5 M3 release of 3/2/18 YP 2.5 M4 cut off of 4/2/18 YP 2.5 M4 release of 4/27/18

Tracking Metrics: WDD 2672 (last week 2700) (https://wiki.yoctoproject.org/charts/combo.html)

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

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

Yocto Project Weekly Status Jan. 8, 2018

Current Dev Position: YP 2.5 M2 development Next Deadline: YP 2.5 M2 cut off of 1/15/18

SWAT team rotation: Cal -> Joshua on Jan. 5, 2018. SWAT team rotation: Joshua -> Armin on Jan. 12, 2018. https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates: • 2.3.3 and 2.4.1 are likely due to imminently release, we tracked down the performance regressions to some kind of infrastructure issue which is still being investigated. • The automated testing issues have mostly been resolved now and this has meant we’ve run a series of builds for master and the stable release branches. As such, the backlog of patches against morty, pyro, rocko and master are substantially reduced after this weekend. • Armin’s help with the stable patch queues is much appreciated. • Due to testing problems with 2.5 M1 rc1, particular from the qemu APIC hangs, we have put a new build, rc3 into QA. The QA of YP 2.5 M1 rc3 is about 2% complete. See: https://wiki.yoctoproject.org/wiki/2.5_QA_Status • We’re aware there are some serious security issues around at the moment. We’ve been stalled partly as maintainers are returning from vacation, partly as fixes are only now becoming available. As fixes are available we will waterfall these into the branches. One of the reasons we’ve focused on clearing the other patches queued is so we can quickly test and merge these and then proceed with another set of point releases.

Planned upcoming dot releases: YP 2.4.1 (Rocko) rc1 is out of QA, and should be released this week. YP 2.3.3 (Pyro) rc1 is out of QA, and should be released this week. YP 2.2.3 (Morty) rc1 is in QA, see https://wiki.yoctoproject.org/wiki/2.2_QA_Status.

Key YP 2.5 Dates are: YP 2.5 M1 rc1 is in QA, see above link. YP 2.5 M2 cut off of 1/15/18 YP 2.5 M2 release of 1/26/18 YP 2.5 M3 cut off of 2/19/18 YP 2.5 M3 release of 3/2/18 YP 2.5 M4 cut off of 4/2/18 YP 2.5 M4 release of 4/27/18

Tracking Metrics:

           WDD 2700 (last week 2764)

(https://wiki.yoctoproject.org/charts/combo.html)

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

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]