All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>
Subject: Current high bug count owners for Yocto Project 3.4
Date: Mon, 19 Apr 2021 17:52:29 -0700	[thread overview]
Message-ID: <06a701d7357f$71595e80$540c1b80$@gmail.com> (raw)

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

All,

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


Who

Count


richard.purdie@linuxfoundation.org

35


ross@burtonini.com

25


david.reyna@windriver.com

23


bruce.ashfield@gmail.com

20


bluelightning@bluelightning.org

16


akuster808@gmail.com

12


timothy.t.orling@intel.com

12


mark.morton@windriver.com

11


JPEWhacker@gmail.com

10


sakib.sajal@windriver.com

10


yifan.yu@windriver.com

10


trevor.gamblin@windriver.com

10


kai.kang@windriver.com

8


hongxu.jia@windriver.com

7


raj.khem@gmail.com

6


randy.macleod@windriver.com

6


chee.yang.lee@intel.com

6


Qi.Chen@windriver.com

6


mingli.yu@windriver.com

5


stacygaikovaia@gmail.com

4


nicolas.dechesne@linaro.org

3


saul.wold@windriver.com

3


idadelm@gmail.com

3


yi.zhao@windriver.com

3


mostthingsweb@gmail.com

3


michael.opdenacker@bootlin.com

2


jaewon@xilinx.com

2


jon.mason@arm.com

2


pokylinux@reliableembeddedsystems.com

2


alejandro@enedino.org

2


jeanmarie.lemetayer@gmail.com

2


matthewzmd@posteo.net

2


ydirson@free.fr

2


shachar@vdoo.com

1


kexin.hao@windriver.com

1


yoctoproject@cookiesoft.de

1


open.source@oleksandr-kravchuk.com

1


dorindabassey@gmail.com

1


twoerner@gmail.com

1


mister_rs@web.de

1


changqing.li@windriver.com

1


john.kaldas.enpj@gmail.com

1


Martin.Jansa@gmail.com

1


kergoth@gmail.com

1


mshah@mvista.com

1


mhalstead@linuxfoundation.org

1


steve@sakoman.com

1


liezhi.yang@windriver.com

1


devendra.tewari@gmail.com

1


naveen.kumar.saini@intel.com

1


matt.ranostay@konsulko.com

1

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

             reply	other threads:[~2021-04-20  0:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  0:52 Stephen Jolley [this message]
2021-04-27  0:01 Current high bug count owners for Yocto Project 3.4 Stephen Jolley
2021-05-04  1:10 Stephen Jolley
2021-05-10 23:40 Stephen Jolley
2021-05-18  1:59 Stephen Jolley
2021-05-25  2:30 Stephen Jolley
2021-05-31 23:44 Stephen Jolley
2021-06-08  0:27 Stephen Jolley
2021-06-15  0:19 Stephen Jolley
2021-06-21 19:13 Stephen Jolley
2021-06-29  2:18 Stephen Jolley
2021-07-06 14:42 Stephen Jolley
2021-07-13 14:48 Stephen Jolley
2021-07-19 18:38 Stephen Jolley
2021-08-10  0:48 Stephen Jolley
2021-08-17  3:16 Stephen Jolley
2021-08-23 23:02 Stephen Jolley
2021-08-31  0:05 Stephen Jolley
2021-09-06 20:39 Stephen Jolley
2021-09-13 21:55 Stephen Jolley
2021-09-20 22:00 Stephen Jolley
2021-09-27 22:05 sjolley.yp.pm
2021-10-05  0:33 sjolley.yp.pm
2021-10-11 23:11 sjolley.yp.pm

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='06a701d7357f$71595e80$540c1b80$@gmail.com' \
    --to=sjolley.yp.pm@gmail.com \
    --cc=yocto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.