yocto.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>,
	<openembedded-core@lists.openembedded.org>
Subject: Current high bug count owners for Yocto Project 4.3
Date: Mon, 1 May 2023 17:51:23 -0700	[thread overview]
Message-ID: <238c01d97c90$38886ce0$a99946a0$@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]

All,

Below is the list as of top 37 bug owners as of the end of WW17 of who have
open medium or higher bugs and enhancements against YP 4.3. There are 124
possible work days left until the final release candidates for YP 4.3 needs
to be released.


Who

Count


michael.opdenacker@bootlin.com

30


david.reyna@windriver.com

27


richard.purdie@linuxfoundation.org

26


randy.macleod@windriver.com

26


bruce.ashfield@gmail.com

25


JPEWhacker@gmail.com

11


pavel@zhukoff.net

9


sakib.sajal@windriver.com

6


tim.orling@konsulko.com

4


sundeep.kokkonda@gmail.com

4


pidge@pidge.org

4


Yash.Shinde@windriver.com

2


sundeep.kokkonda@windriver.com

2


p.lobacz@welotec.com

2


jon.mason@arm.com

2


alexis.lothore@bootlin.com

2


yashinde145@gmail.com

1


tvgamblin@gmail.com

1


throos@amazon.de

1


thomas.perrot@bootlin.com

1


steve@sakoman.com

1


naveen.kumar.saini@intel.com

1


mathew.prokos@gmail.com

1


Martin.Jansa@gmail.com

1


mark.hatle@kernel.crashing.org

1


mark.asselstine@windriver.com

1


louis.rannou@syslinbit.com

1


johannes.schrimpf@blueye.no

1


jens.georg@desy.de

1


geissonator@yahoo.com

1


frederic.martinsons@gmail.com

1


frank.wolff@smile.fr

1


fawzi.khaber@smile.fr

1


fathi.boudra@linaro.org

1


alexandre.belloni@bootlin.com

1


alex.kanavin@gmail.com

1


Grand Total

236

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: 21233 bytes --]

             reply	other threads:[~2023-05-02  0:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02  0:51 sjolley.yp.pm [this message]
2023-05-09  0:30 Current high bug count owners for Yocto Project 4.3 sjolley.yp.pm
2023-05-15 23:01 sjolley.yp.pm
2023-05-23  0:09 sjolley.yp.pm
2023-05-30  0:20 sjolley.yp.pm
2023-06-06  3:24 sjolley.yp.pm
2023-06-13  0:05 sjolley.yp.pm
2023-06-20  0:36 sjolley.yp.pm
2023-06-26 20:52 sjolley.yp.pm
2023-07-03 15:21 sjolley.yp.pm
2023-07-10 16:21 sjolley.yp.pm
2023-07-17 21:45 sjolley.yp.pm
2023-07-24 20:00 sjolley.yp.pm
2023-08-01  7:45 sjolley.yp.pm
2023-08-07 19:05 ` Stephen K Jolley
2023-08-14 21:03 Stephen K Jolley
2023-08-22  0:18 Stephen K Jolley
2023-08-29  1:47 Stephen K Jolley
2023-09-04 23:56 Stephen K Jolley
2023-09-11 21:43 Stephen K Jolley
2023-09-19  4:02 Stephen K Jolley
2023-09-26  1:27 Stephen K Jolley
2023-10-09 23:28 Stephen K Jolley
2023-10-16 23:50 Stephen K Jolley
2023-10-23 12:55 Stephen K 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='238c01d97c90$38886ce0$a99946a0$@gmail.com' \
    --to=sjolley.yp.pm@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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;
as well as URLs for NNTP newsgroup(s).