[yocto] Yocto Project Status WW18’18

2018-04-30 Thread Jordan, Robin L
Current Dev Position: YP 2.5 is in QA.

Next Deadline: YP 2.5 M4 release is 4/27/18


SWAT Team Rotation:

SWAT lead is currently: Stephano

SWAT team rotation: Stephano -> Stephano on May 4, 2018

SWAT team rotation: Stephano -> Maxin on May 11, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   2.5 rc1 is in QA
  *   As things stand we are aware of some minor issues in rc1 such as the 
bitbake version not having been updated and a fix for the eclipse plugin being 
missing. A workaround is available for the latter. We will let QA run its 
course before deciding on whether an rc2 makes sense.
  *   The monthly technical call is tomorrow (1st May) and will focus on 2.6 
planning discussion (https://www.yoctoproject.org/monthly-technical-call/). The 
email linked to below details the planning process we will be following along 
with some of the possible ideas for 2.6: 
http://lists.openembedded.org/pipermail/openembedded-core/2018-April/150040.html


Planned upcoming dot releases:

YP 2.3.4 (Pyro) will be built after 2.5

YP 2.2.4 (Morty) will be built after 2.5

YP 2.4.3 (Rocko) is planned for post YP 2.5


Key YP 2.5 Dates are:

YP 2.5 M4 release of 4/27/18


Tracking Metrics:

  *   WDD 2508 (last week 2486) 
(https://wiki.yoctoproject.org/charts/combo.html)
  *   Patches
 *   Same as last week as nothing has merged.
 *   Total patches found: 1635
 *   Percentage of patches in the Pending State: 46%


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


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Yocto Project Status WW17’18

2018-04-23 Thread Jordan, Robin L
Current Dev Position: YP 2.5 M4 final close out.

Next Deadline: YP 2.5 M4 release is 4/27/18


SWAT Team Rotation:

SWAT lead is currently: Tracy.

SWAT team rotation: Stephano -> Maxin on April 27, 2018

SWAT team rotation: Maxin -> Rebecca on March 4, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   Several key uninative issues were identified and fixed which should mean 
uninative is much more reliable than previously as there were some rare but 
problematic corner cases which are now fixed.
  *   Other potentially 2.5 blocking changes such as timezone issues were fixed.
  *   We have documented sstate mirror setup for poky as opt-in, not by default 
and will monitor the usage of this to see how sustainable it is.
  *   Assuming the current test build succeeds, 2.5 rc1 will be built today.
  *   An email about 2.6 planning was sent out and people are invited to the 
next monthly technical call 
(https://www.yoctoproject.org/monthly-technical-call/). The email details the 
planning process we will be following along with some of the possible ideas for 
2.6. The email is: 
http://lists.openembedded.org/pipermail/openembedded-core/2018-April/150040.html
  *   We are now tracking patch status in the tracking metrics below. The 
percentage of patches with Upstream-Status should stay at 100% now with our 
monitoring. Over time we want to reduce the percentage in the “Pending” state 
and the overall number of patches.


Planned upcoming dot releases:

YP 2.3.4 (Pyro) will be built after 2.5

YP 2.2.4 (Morty) will be built after 2.5

YP 2.4.3 (Rocko) is planned for post YP 2.5


Key YP 2.5 Dates are:

YP 2.5 M4 cut off of 4/2/18

YP 2.5 M4 release of 4/27/18


Tracking Metrics:

  *   WDD 2486 (last week 2573) 
(https://wiki.yoctoproject.org/charts/combo.html)
  *   Patches
 *   Total patches found: 1635
 *   Percentage of patches in the Pending State: 46%


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


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Yocto Project Status April 16, 2018

2018-04-16 Thread Jordan, Robin L
Current Dev Position: YP 2.5 M4 final close out.

Next Deadline: YP 2.5 M4 release is 4/27/18


SWAT Team Rotation:

SWAT lead is currently: Tracy.

SWAT team rotation: Tracy -> Stephano on April 20, 2018

SWAT team rotation: Stephano -> Maxin on April 27, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   2.5 M3 was released. There were some issues but we have decided to target 
these for the final release rather than respinning M3.
  *   Our automated testing shows problems but only on machines in Asia. This 
was root caused to the timezone settings of the builds. We have therefore moved 
some of the reproducibility code to be the default (TZ setting) in order to 
have consistent builds.
  *   Fedora28 has necessitated a late uninative upgrade which is due to merge 
for 2.5 but may have an issue still to resolve (rpm-native popt issue).
  *   The final 2.5 build is blocked on the fedora28 issue above and the two 
remaining build issues we are seeing on debian9 machine the QA team has. Our 
main autobuilder debian9 builds are ok.
  *   Master-next still has a number of recipe upgrades queued which are being 
rebased continually. We still want to discourage people from sending recipe 
upgrades until we start 2.6; however, there were simply too many patches to 
ignore. This has meant various people and build resources have ended up 
distracted from 2.5 work.
  *   For 2.6 we are looking at a slightly different planning process. In the 
next monthly team call we will discuss the plans for 2.6. The agenda will be 
seeded with some high level ideas/goals about what we may be able to do in 2.6. 
It will then be up to the Yocto Project members and community to decide if they 
can contribute the time and resources to make them happen (or add to the list). 
If you are able to work on something in 2.6 please let us know or come to the 
meeting and discuss it with us so that we can ensure we have an accurate plan! 
A separate announcement email will be sent out about this in the next few days.


Planned upcoming dot releases:

YP 2.3.4 (Pyro) will be built after 2.5

YP 2.2.4 (Morty) will be built after 2.5

YP 2.4.3 (Rocko) is planned for post YP 2.5.


Key YP 2.5 Dates are:

YP 2.5 M4 cut off of 4/2/18

YP 2.5 M4 release of 4/27/18


Tracking Metrics:

WDD 2573 (last week 2570)

(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


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Yocto Project Status WW15’18

2018-04-09 Thread Jordan, Robin L
Current Dev Position: YP 2.5 M4 final close out.

Next Deadline: YP 2.5 M4 release is 4/27/18


SWAT Team Rotation:

SWAT lead is currently: Paul.

SWAT team rotation: Paul -> Tracy on April 13, 2018

SWAT team rotation: Tracy -> Stephano on April 20, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   The M3 rc1 QA report has been completed: 
https://wiki.yoctoproject.org/wiki/WW15_-_2018-04-09-_Full_Test_Cycle_-_2.5_M3_rc1
   There are a number of selftest failures and a known SRCREV related issue 
with the build-appliance. We will look into these, but at this point we don’t 
foresee these blocking M3 and will aim to start testing release candidates for 
the final 2.5 release this week.
  *   A problem was spotted with fedora28 which has worryingly decided to merge 
extra patches ahead of glibc and “break” ABI over the split of libcrypt out of 
glibc into libxcrypt. Since we will have to handle this, we have decided to 
change nativesdk-glibc for the 2.5 release but keep on target as is until the 
situation with upstream glibc becomes clearer.
  *   We realised late in the cycle that we needed to change the 
LAYERSERIES_COMPAT variable in the core layers. We have also added warnings to 
make this variable more obvious and required it for Yocto Project Compatible v2 
status. It seemed best to make these changes for 2.5 rather than wait until 2.6.
  *   We are considering a final late change to 2.5 to allow poky to use the 
Yocto Project sstate mirrors by default. Feedback welcome on whether we should 
do this. It is late in the cycle but would make a good speedup for users 
potentially.
  *   Armin fixed the SDK locale issues with morty, thanks! We are aware of a 
related locale  build regression on morty sadly.
  *   We were able to upgrade pseudo and have hopefully resolved our 
fedora27/coreutils issues. Thanks to all who helped!
  *   Master-next has a number of recipe upgrades queued. We still want to 
discourage people from sending recipe upgrades until we start 2.6; however, 
there were simply too many patches to ignore. This has meant various people and 
build resources have ended up distracted from 2.5 work.


Planned upcoming dot releases:

YP 2.3.4 (Pyro) will be built after 2.5 M3

YP 2.2.4 (Morty) will be built after 2.5 M3 once the glibc 2.27 issue is fixed

YP 2.4.3 (Rocko) is planned for post YP 2.5.


Key YP 2.5 Dates are:

YP 2.5 M3 is in QA.  See status above.

YP 2.5 M3 was scheduled for release 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 2570 (last week 2594)

(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


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Yocto Project Status WW14’18

2018-04-02 Thread Jordan, Robin L
Current Dev Position: YP 2.5 M3 final close out.

Next Deadline: YP 2.5 M4 stabilization is 4/2/18

SWAT Team Rotation:

SWAT lead is currently Juro.

SWAT team rotation: Juro -> Paul on April 6, 2018

SWAT team rotation: Paul -> Tracy on April 13, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   Two issues have so far been identified in the M3 rc1 build. One is due to 
differences in build-appliance srcrev between the new and old buildbot 
autobuilder codebases. The second is an issue with the particular stable kernel 
version causing problems on 32bit IA which we believe is fixed in current 
master due to kernel version changes there.
  *   We continue to be blocked with morty on the glibc 2.27 and the sdk locale 
issues.  Armin has been looking into it.
  *   The pseudo issue with newer versions of coreutils as used in fedora27 
continues to cause problems, but thanks to some work by several people we do 
look close to a solution.  The help from everyone is much appreciated.
  *   We are now well into the stabilization period and are seeing a number of 
good patches both to fix current issues and future proof the release, 
foreseeing potential problems with versions and heading those issues off.  
Thanks to everyone helping with these.
  *   The codename for 2.6 (after sumo) will be ‘thud’.
  *   As a reminder, general recipe upgrades will not be merged during this 
period unless there is a pressing reason.  Those will be held for 2.6.


Planned upcoming dot releases:

YP 2.3.4 (Pyro) will be built after 2.5 M3

YP 2.2.4 (Morty) will be built after 2.5 M3 once the glibc 2.27 issue is fixed

YP 2.4.3 (Rocko) is planned for post YP 2.5.


Key YP 2.5 Dates are:

YP 2.5 M3 is in QA.  See status above.

YP 2.5 M3 was scheduled for release 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 2594 (last week 2673)

(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


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Yocto Project Status WW12’18

2018-03-19 Thread Jordan, Robin L
Current Dev Position: YP 2.5 M3 final close out.

Next Deadline: YP 2.5 M3 cut off was 2/19/18

*** FEATURE FREEZE for 2.5 has passed ***


SWAT lead is currently Ross.

SWAT team rotation: Armin -> Ross on March 23, 2018

SWAT team rotation: Ross -> Juro on March 30, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   YP 2.4.2 was released: 
https://lists.yoctoproject.org/pipermail/yocto/2018-March/040282.html
  *   Meta-intel 8.1 was released: 
https://lists.yoctoproject.org/pipermail/meta-intel/2018-March/005261.html
  *   We’ve realised we were going to run into problems with distros adopting 
glibc 2.27, if not now, during the next release cycle. We therefore decided to 
head off this problem and try and fix the issues now. Unfortunately, due to 
locale changes in 2.27, it also breaks our eSDK in the current and all previous 
releases. We have fixes in master for this (thanks Ross!) and backports ready 
for rocko and pyro in the -next branches. Morty is proving harder to fix. We 
believe it is likely better to fix these issue even if the changes are invasive 
(they are at least mostly contained to the SDKs).

  *   The gcc 6.x changes were merged into rocko/pyro/morty which means point 
releases are now unblocked by that issue.
  *   The performance issue reported last week was tracked down to a kernel 
change which was reverted.
  *   The new buildbot autobuilder instance is working with basic 
functionality. We therefore plan to run the M3 release build on that 
infrastructure with a view to using it for the main 2.5 release. It was great 
to be able to report an issue upstream and be using their latest code! The 
autobuilder functionality is improved in at least two significant ways already 
which benefit the maintainers.
  *   We really do need to roll M3 now, our current plan is to test the final 
changes in mut and then run M3 with this. It is not a perfect set of features, 
many things simply haven’t made it in as the people doing review are 
overloaded. We’re too far past the freeze deadline to realistically make any 
further progress with this though.
  *   ELC was productive and there was a lot of good discussion between the 
people there about many different things. In particular we have some ideas for 
improving the project’s build infrastructure to allow more builds including 
other layers. More info will follow as we build the plans to make that happen.


Planned upcoming dot releases:

YP 2.3.4 (Pyro) will be built after 2.5 M3

YP 2.2.4 (Morty) will be built after 2.5 M3 once the glibc 2.27 issue is fixed

YP 2.4.3 (Rocko) is planned for post YP 2.5.


Key YP 2.5 Dates are:

YP 2.5 M3 is in feature freeze.  See status above.

YP 2.5 M3 was scheduled for release 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 2673 (last week 2673)

(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


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


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





Robin Jordan

Yocto Project Program Manager

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Yocto Project Status WW11’18

2018-03-12 Thread Jordan, Robin L
Current Dev Position: YP 2.5 M3 final close out.

Next Deadline: YP 2.5 M3 cut off was 2/19/18

*** FEATURE FREEZE for 2.5 has passed ***


SWAT lead is currently Cal.

SWAT team rotation: Cal -> Armin on March 16, 2018

SWAT team rotation: Armin -> Ross on March 23, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   The Embedded Linux Conference is in Portland this week!
  *   YP 2.4.2 RC2 QA report is being discussed and is expected to be released 
this week. 
(https://wiki.yoctoproject.org/wiki/WW10_-_2018-03-05-_Full_Test_Cycle_-_2.4.2_rc2).
  *   We are changing the planning process and Milestone tracking in Bugzilla.  
More details can be found here:  
https://lists.yoctoproject.org/pipermail/yocto/2018-March/040226.html
  *   A new uninative release was made (1.8) because distributions are moving 
to glibc 2.27 and this broke the old uninative. People using uninative should 
upgrade to this.
  *   GCC 6.x with the latest security fixes is currently in rocko/pyro/morty 
-next thanks to Martin and Juro. They are undergoing autobuilder testing now 
but we hope they’ll be merged soon.

  *   Performance metrics indicate that a recent merge has caused a slowdown in 
build times.  It is suspected that the glibc upgrade is the cause of this 
although help would be appreciated to verify and possibly mitigate this.
  *   Flood of last-minute upgrades continuing to be reviewed and merged if 
high reward or low impact.
  *   Go upgrade/improvements were merged.  For 2.5 we will be shipping both 
1.9.4 and 1.10, but plan to drop 1.9.x from master once 1.10 doesn’t present 
compatibility problems.
  *   EFI image refactoring patches were merged. The gist of these are that 
/boot is now under package manager control instead of injected at image 
creation.
  *   A number of patch refresh patches were merged. These are to solve 
problems with patches applied with “fuzz”, where patch will note that the 
context isn’t correct anymore but the differences are hopefully small enough to 
apply anyway.  Sometimes this is useful (other changes causing the target lines 
to move), sometimes it’s actively harmful (patch applied incorrectly, silently 
breaking behaviour). We hope to warn when fuzz is detected during the 2.6 cycle 
so these patches are removing fuzz from oe-core.  Expect a mail to the lists 
soon explaining how to find and remove fuzz.
  *   We are continuing to work on the autobuilder changes and for various 
reasons (inc. changes in people).  We would be in much better shape to switch 
to the new codebase before release, rather than waiting until early 2.6 to pick 
this work up again by which time we would have lost people and context. If we 
are to switch, we need to build M3 with the new infrastructure. We plan to make 
this switch for M3.


Planned upcoming dot releases:

YP 2.3.4 (Pyro) will be built when GCC backports are merged.

YP 2.2.4 (Morty) will be built when GCC backports are merged.

YP 2.4.3 (Roko) is planned for post YP 2.5.


Key YP 2.5 Dates are:

YP 2.5 M3 is in feature freeze.  See status above.

YP 2.5 M3 was scheduled for release 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 2673 (last week 2663)

(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


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


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


Robin Jordan
Yocto Project Program Manager
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Subject: Yocto Project Status WW10’18

2018-03-05 Thread Jordan, Robin L
Subject: Yocto Project Status WW10’18

Current Dev Position: YP 2.5 M3 final close out.
Next Deadline: YP 2.5 M3 cut off was 2/19/18
*** FEATURE FREEZE for 2.5 has passed ***

SWAT team rotation: Rebecca -> Cal on March 9, 2018
SWAT team rotation: Cal -> Armin on March 16, 2018
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:

  *   YP 2.5 M2 was released February 27.
 *   This milestone release includes CVE fixes and 60 recipe upgrades.  It 
incorporates security fixes with upgrades to gcc and kernels to all current 
stable versions.  Headline changes include reproducibility improvements, 
gettext build performance, image generation, and cmake using Ninja by default.  
This release added gobject-introspection tests to testimage, integrated support 
for the Meson build system, Python build/packaging refactoring, and redesigned 
postinstall script handling.
  *   YP 2.2.3 was released February 27.
 *   A total of 97 CVE fixes and other fixes to work with GCC 7 on newer 
host OSs.
 *   We have committed to a 2.2.4 release to integrate all remaining 
security fixes.
  *   YP 2.4.2 RC2 came out of QA today (report at 
https://wiki.yoctoproject.org/wiki/WW10_-_2018-03-05-_Full_Test_Cycle_-_2.4.2_rc2)

  *   YP 2.5 M3 is in final feature freeze. Reviewing last week’s required 
features:
 *   2.27 glibc upgrade has been merged. This meant making SDK changes so 
they’re all ~50M larger now thanks to the need to ship locales. However the 
same underlying code could be reused to generate locale archives in images, 
which will make those smaller.
 *   kernel-devsrc size reduction: the blocking issue has been resolved so 
waiting for an updated patch.
 *   pseudo upgrade has been merged which should solve many issues, and 
Peter is investigating the long-standing host contamination issue.
 *   Still need to resolve the multilib SDK patch series.
 *   Package feed filtering has been merged.
 *   Image EFI configuration rework under review now.
  *   Performance metrics indicate that a recent merge has caused a slowdown in 
build times.  It is suspected that the glibc upgrade is the cause of this 
although help would be appreciated to verify this.
  *   Flood of last-minute upgrades continuing to be reviewed and merged if 
low-impact.
  *   Go upgrade/improvements are under review, possibly we’ll ship both Go 
1.9.4 and 1.10 in 2.5 but do plan to drop 1.9.4 from master as soon as 1.10 
doesn’t present compatibility problems.
  *   We’re continuing to work on the autobuilder changes and for various 
reasons (inc. changes in people).  We would be in much better shape to switch 
to the new codebase before release, rather than waiting until early 2.6 to pick 
this work up again by which time we’d have lost people and context. If we are 
to switch, we need to build M3 with the new infrastructure. We plan to make 
this switch for M3.

Planned upcoming dot releases:
YP 2.3.4 (Pyro) will be built when we figure out gcc backports.
YP 2.2.4 (Morty) will be built when we figure out gcc backports.
YP 2.4.3 (Roko) is planned for post YP 2.5.

Key YP 2.5 Dates are:
YP 2.5 M3 is in feature freeze.  See status above.
YP 2.5 M3 was scheduled for release 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 2663 (last week 2646)
(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

The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status

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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Yocto Project Status WW09’18

2018-02-26 Thread Jordan, Robin L
Current Dev Position: YP 2.5 M3 development

Next Deadline: YP 2.5 M3 cut off was 2/19/18

*** FEATURE FREEZE for 2.5 has passed ***


SWAT team rotation: Stephano -> Maxin John on Feb. 23, 2018

SWAT team rotation: Maxin -> Rebecca on March 2, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   YP 2.5 M2 is through QA and likely to be released early this week.
  *   YP 2.2.3 is through QA and likely to be released early this week.
  *   YP 2.4.2 rc2 was successfully built and is undergoing QA.
  *   YP 2.5 M3 is feature freeze. After discussions with various people we 
concluded that we need:
 *   the 2.27 glibc upgrade
 *   kernel-devsrc size changes
 *   to resolve some of the outstanding pseudo bugs
 *   to resolve the multilib SDK patch series
 *   the package feed filtering patch series (the multilib SDK series 
depends on it)
 *   image EFI configuration rework
  *   We plan to defer:
 *   pkg-conf vs. pkgconfig issues/discussion
 *   profile guided optimisation for python (patch series)
 *   oe-selftest parallelization
  *   We’re continuing to work on the autobuilder changes and for various 
reasons (inc. changes in people).  We would be in much better shape to switch 
to the new codebase before release, rather than waiting until early 2.6 to pick 
this work up again by which time we’d have lost people and context. If we are 
to switch, we need to build M3 with the new infrastructure. We’ll have to make 
a decision on whether we do this during this week.


Planned upcoming dot releases:

YP 2.4.2 (Rocko) is currently in QA 82% complete.   See: 
https://wiki.yoctoproject.org/wiki/2.4_QA_Status

YP 2.3.4 (Pyro) will be built when we figure out gcc backports.

YP 2.2.3 (Morty) rc2 has passed QA and is being prepared for release

YP 2.2.4 (Morty) will be built when we figure out gcc backports.


Key YP 2.5 Dates are:

YP 2.5 M2 has passed QA and is being prepared for release.

YP 2.5 M3 is in feature freeze.  See status above.

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 2646 (last week   2648)

(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


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


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

Robin Jordan
Yocto Project Program Manager
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Yocto Project Status WW08’18

2018-02-20 Thread Jordan, Robin L
Current Dev Position: YP 2.5 M3 development

Next Deadline: YP 2.5 M3 cut off was 2/19/18

*** FEATURE FREEZE for 2.5 is imminent! ***


SWAT team rotation: Tracy -> Stephano on Feb. 16, 2018.

SWAT team rotation: Stephano -> Maxin John on Feb. 23, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   YP 2.5 M2 is 97% through QA. See: 
https://wiki.yoctoproject.org/wiki/2.5_QA_Status
  *   YP 2.2.3 is also mostly through QA. See 
https://wiki.yoctoproject.org/wiki/2.2_QA_Status
  *   We build 2.4.2 rc1 however rapidly moving kernel updates combined with QA 
not having started on rc1 yet meant we decided to build rc2, pulling in further 
kernel security fixes (as well as others like openssl). rc2 is currently being 
built and should enter QA today assuming a successful build.
  *   autobuilder.yoctoproject.org continues to be unavailable as we continue 
to develop the new autobuilder codebase to replace the current heavily 
customized buildbot one.
  *   We managed to shrink the ltp package size which unblocked some patch 
merging. Bruce has been working on changes to kernel-devsrc to significantly 
reduce its size.
  *   The glibc change continues to be blocked on locale issues which may prove 
tricky to resolve and will block M3 as we need the glibc upgrade for various 
reasons.
  *   We have some key decisions to make about the conflicting native of 
pkg-conf and pkgconfig. Maxin has a patch series which exposes the issues.
  *   There are problems with the changes to pseudo’s master branch verses the 
patches we have against the recipe.
  *   Please note that we are very close to M3 which is feature freeze, 
technically, feature freeze was yesterday. We’re not in a position to build M3 
yet but if there are features you expect to see in 2.5, please highlight those 
patches ASAP. We are drawing up a list of “must haves” for the release and if 
we don’t know about it, it likely won’t be on it.


Planned upcoming dot releases:

YP 2.4.2 (Rocko) is currently being built and should enter QA today.

YP 2.3.4 (Pyro) will be built when we figure out gcc backports.

YP 2.2.3 (Morty) rc2 is in QA.

YP 2.2.4 (Morty) will be built when we figure out gcc backports.


Key YP 2.5 Dates are:

YP 2.5 M2 cut off is past, it is in QA.

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 2648 (last week  2610)

(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


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto