All of lore.kernel.org
 help / color / mirror / Atom feed
From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>
Subject: Current high bug count owners for Yocto Project 3.5
Date: Mon, 17 Jan 2022 15:36:29 -0700	[thread overview]
Message-ID: <10c501d80bf2$abd1e380$0375aa80$@gmail.com> (raw)

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

All,

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


Who

Count


ross@burtonini.com

37


michael.opdenacker@bootlin.com

36


randy.macleod@windriver.com

23


david.reyna@windriver.com

22


bruce.ashfield@gmail.com

16


tim.orling@konsulko.com

14


trevor.gamblin@windriver.com

12


sakib.sajal@windriver.com

12


richard.purdie@linuxfoundation.org

9


kai.kang@windriver.com

7


mhalstead@linuxfoundation.org

7


bluelightning@bluelightning.org

6


saul.wold@windriver.com

6


JPEWhacker@gmail.com

5


hongxu.jia@windriver.com

4


chee.yang.lee@intel.com

4


kiran.surendran@windriver.com

3


Qi.Chen@windriver.com

3


jon.mason@arm.com

3


alexandre.belloni@bootlin.com

2


raj.khem@gmail.com

2


pgowda.cve@gmail.com

2


pokylinux@reliableembeddedsystems.com

2


mshah@mvista.com

2


alejandro@enedino.org

2


open.source@oleksandr-kravchuk.com

1


yf3yu@uwaterloo.ca

1


akuster808@gmail.com

1


yi.zhao@windriver.com

1


jay.shen.teoh@intel.com

1


limon.anibal@gmail.com

1


jonathan.richardson@broadcom.com

1


aehs29@gmail.com

1


kexin.hao@windriver.com

1


matthewzmd@posteo.net

1


thomas.perrot@bootlin.com

1


mark.hatle@kernel.crashing.org

1


Martin.Jansa@gmail.com

1


mingli.yu@windriver.com

1


TicoTimo@gmail.com

1


shachar@vdoo.com

1


nicolas.dechesne@linaro.org

1


john.kaldas.enpj@gmail.com

1


mostthingsweb@gmail.com

1


Grand Total

260

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

             reply	other threads:[~2022-01-17 22:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 22:36 sjolley.yp.pm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-18 19:52 Current high bug count owners for Yocto Project 3.5 sjolley.yp.pm
2022-04-11 23:34 sjolley.yp.pm
2022-04-05  0:37 sjolley.yp.pm
2022-03-29  0:43 sjolley.yp.pm
2022-03-21 23:57 sjolley.yp.pm
2022-03-14 23:11 sjolley.yp.pm
2022-03-08 16:18 sjolley.yp.pm
2022-03-01 16:30 sjolley.yp.pm
2022-02-21 23:33 sjolley.yp.pm
2022-02-15  0:52 sjolley.yp.pm
2022-02-07 23:59 sjolley.yp.pm
2022-02-01  2:40 sjolley.yp.pm
2022-01-25  3:07 sjolley.yp.pm
2022-01-10 21:35 sjolley.yp.pm
2022-01-03 22:32 sjolley.yp.pm
2021-12-27 23:08 sjolley.yp.pm
2021-12-20 22:58 sjolley.yp.pm
2021-12-13 22:19 sjolley.yp.pm
2021-12-06 21:33 sjolley.yp.pm
2021-11-29 22:11 sjolley.yp.pm
2021-11-22 22:25 sjolley.yp.pm
2021-11-16  0:06 sjolley.yp.pm
2021-11-08 23:31 sjolley.yp.pm
2021-11-01 20:40 sjolley.yp.pm
2021-10-25 22:43 sjolley.yp.pm
2021-10-18 17:39 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='10c501d80bf2$abd1e380$0375aa80$@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 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.