From: Sakib Sajal <sakib.sajal@windriver.com>
To: Yocto-mailing-list <yocto@lists.yoctoproject.org>
Cc: alexandre.belloni@bootlin.com,
Bruce Ashfield <bruce.ashfield@gmail.com>,
daiane.angolini@foundries.io,
"jpewhacker@gmail.com" <jpewhacker@gmail.com>,
luca.ceresoli@bootlin.com, Pavel Zhukov <pavel.zhukov@huawei.com>,
Randy MacLeod <randy.macleod@windriver.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Khem Raj <raj.khem@gmail.com>,
ross@burtonini.com,
"sjolley.yp.pm@gmail.com" <sjolley.yp.pm@gmail.com>,
Steve Sakoman <steve@sakoman.com>,
tim.orling@konsulko.com, sakib.sajal@windriver.com,
akuster808 <akuster808@gmail.com>,
valery.chernous@gmail.com, Zheng Qiu <zheng.qiu@windriver.com>,
tgamblin@baylibre.com
Subject: [yocto] Minutes: Yocto Project Weekly Triage Meeting 02/06/2023
Date: Thu, 1 Jun 2023 11:17:57 -0400 [thread overview]
Message-ID: <839deb9f-1922-fe3d-64fd-51fafed87291@windriver.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage
*Attendees: *Richard Purdie, Steve Sakoman, Stephen Jolley, Bruce
Ashfield, Joshua Watt, Trevor Gamblin, Randy Macleod, Alexandre Belloni,
Tim Orling, Thomas Roos, Yoann Congal, Michael Opdenacker, Ryan Eatmon
*ARs:**
*
- Trevor to create followup bug to 15129
- Nat to look at 6986
**
*Notes:
*
*
*
*Medium+ 4.3 Unassigned Enhancements/Bugs: *72 (Last week 72)
*Medium+ 4.99 Unassigned Enhancements/Bugs: *44**(Last week 44)
*AB Bugs: *70 (Last week 72)
[-- Attachment #2: Type: text/html, Size: 1466 bytes --]
next reply other threads:[~2023-06-01 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 15:17 Sakib Sajal [this message]
2023-06-01 18:35 ` [yocto] Minutes: Yocto Project Weekly Triage Meeting 02/06/2023 Trevor Gamblin
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=839deb9f-1922-fe3d-64fd-51fafed87291@windriver.com \
--to=sakib.sajal@windriver.com \
--cc=akuster808@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bruce.ashfield@gmail.com \
--cc=daiane.angolini@foundries.io \
--cc=jpewhacker@gmail.com \
--cc=luca.ceresoli@bootlin.com \
--cc=pavel.zhukov@huawei.com \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross@burtonini.com \
--cc=sjolley.yp.pm@gmail.com \
--cc=steve@sakoman.com \
--cc=tgamblin@baylibre.com \
--cc=tim.orling@konsulko.com \
--cc=valery.chernous@gmail.com \
--cc=yocto@lists.yoctoproject.org \
--cc=zheng.qiu@windriver.com \
/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;
as well as URLs for NNTP newsgroup(s).