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.3
Date: Mon, 9 Nov 2020 16:06:48 -0800	[thread overview]
Message-ID: <0e2b01d6b6f5$6275ac10$27610430$@gmail.com> (raw)

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

All,

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


Who

Count


richard.purdie@linuxfoundation.org

34


ross@burtonini.com

22


david.reyna@windriver.com

21


bruce.ashfield@gmail.com

19


bluelightning@bluelightning.org

19


timothy.t.orling@intel.com

12


JPEWhacker@gmail.com

12


sakib.sajal@windriver.com

11


mark.morton@windriver.com

11


akuster808@gmail.com

9


trevor.gamblin@windriver.com

9


kai.kang@windriver.com

8


Qi.Chen@windriver.com

6


stacy.gaikovaia@windriver.com

5


raj.khem@gmail.com

5


randy.macleod@windriver.com

4


rpjday@crashcourse.ca

4


mingli.yu@windriver.com

4


mostthingsweb@gmail.com

4


idadelm@gmail.com

4


chee.yang.lee@intel.com

4


yi.zhao@windriver.com

3


alejandro@enedino.org

3


hongxu.jia@windriver.com

3


ydirson@free.fr

3


jeanmarie.lemetayer@gmail.com

2


mark.hatle@kernel.crashing.org

2


matthewzmd@posteo.net

2


kergoth@gmail.com

2


saul.wold@windriver.com

2


jpuhlman@mvista.com

2


jaewon@xilinx.com

2


jon.mason@arm.com

2


Martin.Jansa@gmail.com

1


kai.ruhnau@live.com

1


jason.wessel@windriver.com

1


nicolas.dechesne@linaro.org

1


liezhi.yang@windriver.com

1


ankur.tyagi85@gmail.com

1


jbb5044@gmail.com

1


dl9pf@gmx.de

1


aehs29@gmail.com

1


kamensky@cisco.com

1


anuj.mittal@intel.com

1


liu.ming50@gmail.com

1


apoorvsangal@gmail.com

1


joe.slater@windriver.com

1


fede@evolware.org

1


maxime.roussinbelanger@gmail.com

1


mhalstead@linuxfoundation.org

1


kexin.hao@windriver.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: 34322 bytes --]

             reply	other threads:[~2020-11-10  0:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10  0:06 Stephen Jolley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-13  0:29 Current high bug count owners for Yocto Project 3.3 Stephen Jolley
2021-04-06  3:54 Stephen Jolley
2021-03-29 22:38 Stephen Jolley
2021-03-22 20:43 Stephen Jolley
2021-03-15 19:09 Stephen Jolley
2021-03-08 16:17 Stephen Jolley
2021-03-02  2:44 Stephen Jolley
2021-02-22 22:08 Stephen Jolley
2021-02-15 23:12 Stephen Jolley
2021-02-09  0:27 Stephen Jolley
2021-02-02  1:57 Stephen Jolley
2021-01-26 15:42 Stephen Jolley
2021-01-19  1:15 Stephen Jolley
2021-01-12  0:10 Stephen Jolley
2021-01-04 18:34 Stephen Jolley
2020-12-29  4:50 Stephen Jolley
2020-12-22  0:34 Stephen Jolley
2020-12-15  3:07 Stephen Jolley
2020-12-08  3:13 Stephen Jolley
2020-12-01  1:52 Stephen Jolley
2020-11-24 22:20 Stephen Jolley
2020-11-17  1:16 Stephen Jolley
2020-11-02 22:30 Stephen Jolley
2020-10-26 21:50 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='0e2b01d6b6f5$6275ac10$27610430$@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.