From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f50.google.com (mail-pl0-f50.google.com [209.85.160.50]) by mail.openembedded.org (Postfix) with ESMTP id 2334B789D5 for ; Mon, 19 Mar 2018 19:22:24 +0000 (UTC) Received: by mail-pl0-f50.google.com with SMTP id x4-v6so1904782pln.7 for ; Mon, 19 Mar 2018 12:22:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=UGhGCspsX2Rm9FigVS9OHI5x2gERakaOVYjMh6x7nAE=; b=WPhHEtBrIUYJQGYebtJUR5WtaD1YbZ7v06faZjL5I+DUxyd23m65PCMw6tnGQHSJkm b1Jc+1BTphOj1vrMkQ8dhelS8CbGY/fQGkZWRAvn2VDrS+CDeLizKfirFfdi2QieqbpM FSdhCxWImHFMWe4LSjrsue3iMso6Ans2ZNd+zFNcqEsKJat8J8IEqBPxfg+4TeIwRLjQ YM/pDOxRAuGmV1mwzK6SLqA1htsX3ymRXBeWMEI1KKIsup+HNg2mgk4CWRsiJLzrf6Z7 eKROHRB/J5l9yAfXbxDcrJI447oQi51AFnBWCB0pTItr5D9kJ8awFJvMd6epvTkSgCk6 oMXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=UGhGCspsX2Rm9FigVS9OHI5x2gERakaOVYjMh6x7nAE=; b=SwohZOzU5Hfsko/uH9cg+1D485VG6HW92HgYxYIReOgxoZ+m9GNg8DwdgL334T2rT4 mj34Yzf5Bir7Pw2zm1ceoMPMpvAs0QVWkcENTA4veEBluLz+p9hIOpkurxGF9BPVrqQa a6LyAwla3JqOavswdOGHGDRRM/BYafJ2ZB1wuUrs1SFbh8KFIjnRCLGH1bvI+b143sJP vnhK/yAAYj7H3Hl5SMXxSW7O3+uTt3ZbRqQxcqK+DzUHO2L6OTNNqemO71iR6SXI9Jh/ lo7ZL26rP0iWjYS9ECxYslc7J7zKXe0Lin4QlXeaGyEhygtEGHoiKM0AqaHKWJ8oiBhO DNZA== X-Gm-Message-State: AElRT7GZp6xk1lBHJPtAbK8LDqIbVjc7L5gYnM4gIY6e32qOVjh2rF/A XD8qBkv6dt2dqcyB+0krt2Mt9Q== X-Google-Smtp-Source: AG47ELuf8C5anHf3Ai62BAQAVZGtqCpoO0g5jERGSgdyAIxa2hjfYoM3xqbSC8qpr1Bmuo+sM+H7oA== X-Received: by 2002:a17:902:51ad:: with SMTP id y42-v6mr10457797plh.314.1521487346291; Mon, 19 Mar 2018 12:22:26 -0700 (PDT) Received: from ?IPv6:2601:202:4000:1184:4088:e426:a566:fc98? ([2601:202:4000:1184:4088:e426:a566:fc98]) by smtp.gmail.com with ESMTPSA id j23sm1085779pfi.78.2018.03.19.12.22.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Mar 2018 12:22:25 -0700 (PDT) To: "Jordan, Robin L" , "yocto@yoctoproject.org" , "openembedded-core@lists.openembedded.org" References: From: akuster808 Message-ID: Date: Mon, 19 Mar 2018 12:22:24 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Subject: =?UTF-8?B?UmU6IFlvY3RvIFByb2plY3QgU3RhdHVzIFdXMTLigJkxOA==?= X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 19:22:25 -0000 Content-Type: multipart/alternative; boundary="------------548A70ACEB132035F048EC81" Content-Language: en-US --------------548A70ACEB132035F048EC81 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit On 03/19/2018 08:45 AM, Jordan, Robin L wrote: > > 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. > Does this include package updates? Do we have a place identified for new changes (2.6) while 2.5 stabilizes. - armin > 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 > >   > > > --------------548A70ACEB132035F048EC81 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit



On 03/19/2018 08:45 AM, Jordan, Robin L wrote:

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.

Does this include package updates?

Do we have a place identified for new changes (2.6) while 2.5 stabilizes.

- armin


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

 




--------------548A70ACEB132035F048EC81-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 31FC3E00708; Mon, 19 Mar 2018 12:22:28 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (akuster808[at]gmail.com) * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [209.85.160.46 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-pl0-f46.google.com (mail-pl0-f46.google.com [209.85.160.46]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id EA9F1E00708 for ; Mon, 19 Mar 2018 12:22:26 -0700 (PDT) Received: by mail-pl0-f46.google.com with SMTP id n15-v6so3116843plp.12 for ; Mon, 19 Mar 2018 12:22:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=UGhGCspsX2Rm9FigVS9OHI5x2gERakaOVYjMh6x7nAE=; b=WPhHEtBrIUYJQGYebtJUR5WtaD1YbZ7v06faZjL5I+DUxyd23m65PCMw6tnGQHSJkm b1Jc+1BTphOj1vrMkQ8dhelS8CbGY/fQGkZWRAvn2VDrS+CDeLizKfirFfdi2QieqbpM FSdhCxWImHFMWe4LSjrsue3iMso6Ans2ZNd+zFNcqEsKJat8J8IEqBPxfg+4TeIwRLjQ YM/pDOxRAuGmV1mwzK6SLqA1htsX3ymRXBeWMEI1KKIsup+HNg2mgk4CWRsiJLzrf6Z7 eKROHRB/J5l9yAfXbxDcrJI447oQi51AFnBWCB0pTItr5D9kJ8awFJvMd6epvTkSgCk6 oMXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=UGhGCspsX2Rm9FigVS9OHI5x2gERakaOVYjMh6x7nAE=; b=d97AQEuBUd50NZuYHhW41Gln0wInXKn9ibYMrX4HvD87UeiPjJA1f1SuxrhnmpZDhS ShanVrK3ytdb5VqDVWTjd9bI6wRlbm8oirF/DNdCKHHtew5LEFHXs5ncRMF07YY/FKto VVnF1of8dehZ+k0JGlhznT+MIAjhOF5JyWxRYopmq1A0RVvMYRfegj0fKy2D/xFhqYkD VbHM57lLpBahA71rNAs0qDh1jhxefe+3n+0DqLfq7gEg4fRM1nO9Z3w5Dpt9g/1D1zfS oPKrtYlZdNO6hm/QsQEs5+FWQFFt7S+448sAmT3uTRweEyvwGlqncJNkumrOMfROQz1U MHEg== X-Gm-Message-State: AElRT7HHV8KOK96Q912E8utoSaigpznubddgWzl3tWiSp+9iHgq+iJ0j 2Mw81eh7LMvuhk/M3YHapVM= X-Google-Smtp-Source: AG47ELuf8C5anHf3Ai62BAQAVZGtqCpoO0g5jERGSgdyAIxa2hjfYoM3xqbSC8qpr1Bmuo+sM+H7oA== X-Received: by 2002:a17:902:51ad:: with SMTP id y42-v6mr10457797plh.314.1521487346291; Mon, 19 Mar 2018 12:22:26 -0700 (PDT) Received: from ?IPv6:2601:202:4000:1184:4088:e426:a566:fc98? ([2601:202:4000:1184:4088:e426:a566:fc98]) by smtp.gmail.com with ESMTPSA id j23sm1085779pfi.78.2018.03.19.12.22.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Mar 2018 12:22:25 -0700 (PDT) To: "Jordan, Robin L" , "yocto@yoctoproject.org" , "openembedded-core@lists.openembedded.org" References: From: akuster808 Message-ID: Date: Mon, 19 Mar 2018 12:22:24 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Subject: =?UTF-8?B?UmU6IFtPRS1jb3JlXSBZb2N0byBQcm9qZWN0IFN0YXR1cyBXVzEy4oCZMTg=?= X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 19:22:28 -0000 Content-Type: multipart/alternative; boundary="------------548A70ACEB132035F048EC81" Content-Language: en-US --------------548A70ACEB132035F048EC81 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit On 03/19/2018 08:45 AM, Jordan, Robin L wrote: > > 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. > Does this include package updates? Do we have a place identified for new changes (2.6) while 2.5 stabilizes. - armin > 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 > >   > > > --------------548A70ACEB132035F048EC81 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit



On 03/19/2018 08:45 AM, Jordan, Robin L wrote:

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.

Does this include package updates?

Do we have a place identified for new changes (2.6) while 2.5 stabilizes.

- armin


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

 




--------------548A70ACEB132035F048EC81--