From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW02
Date: Mon, 10 Jan 2022 14:42:50 -0700 [thread overview]
Message-ID: <0e2301d8066b$04880500$0d980f00$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2924 bytes --]
All,
YP M+ or high bugs which moved to a new milestone in WW02 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=8191> 8191
apply kernel config fragments to arbitrary kernels
randy.macleod@windriver.com
bruce.ashfield@gmail.com
3.5 M1
3.5 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=12937> 12937
Consistent naming scheme for deployed artifacts
randy.macleod@windriver.com
Martin.Jansa@gmail.com
3.5 M1
3.5 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13051> 13051
allow Open Container compliant "images" to be generated from oe images (container or not)
randy.macleod@windriver.com
bruce.ashfield@gmail.com
3.5 M1
3.5 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13360> 13360
kernel-dev: package full kernel source and headers for reference purposes
randy.macleod@windriver.com
bruce.ashfield@gmail.com
3.5 M1
3.5 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13731> 13731
Cross canadian GCC fails to find header files when using tclibc-newlib
randy.macleod@windriver.com
alejandro@enedino.org
3.5 M1
3.5 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14303> 14303
Result of build is not stored in testresult.json with resulttool
randy.macleod@windriver.com
jay.shen.teoh@intel.com
3.5 M1
3.5 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14348> 14348
Layer dependencies not updated
randy.macleod@windriver.com
bluelightning@bluelightning.org
3.5 M1
3.5 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14357> 14357
No PDF and EPUB versions of the manuals available on the website
randy.macleod@windriver.com
mhalstead@linuxfoundation.org
3.5 M1
3.5 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14394> 14394
Add a banner on the old documentation docs
randy.macleod@windriver.com
mhalstead@linuxfoundation.org
3.5 M1
3.5 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14539> 14539
Remove vague "BSD" license
randy.macleod@windriver.com
ross@burtonini.com
3.5 M1
3.5 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14552> 14552
Timeout reported as "ERROR: Exit status is 9" which is not very helpful
randy.macleod@windriver.com
limon.anibal@gmail.com
3.5 M1
3.5 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14573> 14573
boost doesn't build for armv5
randy.macleod@windriver.com
jon.mason@arm.com
3.5 M1
3.5 M3
Thanks,
Stephen K. Jolley
Yocto Project Program Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com <mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 32394 bytes --]
next reply other threads:[~2022-01-10 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 21:42 sjolley.yp.pm [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-13 6:39 M+ & H bugs with Milestone Movements WW02 Stephen K Jolley
2025-01-14 8:21 Stephen K Jolley
2024-01-15 19:56 Stephen K Jolley
2023-01-17 3:18 sjolley.yp.pm
2022-01-25 3:14 sjolley.yp.pm
2021-01-12 0:16 Stephen Jolley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='0e2301d8066b$04880500$0d980f00$@gmail.com' \
--to=sjolley.yp.pm@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox