openembedded-core.lists.openembedded.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.1
Date: Mon, 1 Aug 2022 14:36:16 -0700	[thread overview]
Message-ID: <0dae01d8a5ee$bf12f600$3d38e200$@gmail.com> (raw)

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


All,

 

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


Who

Count

 	

michael.opdenacker@bootlin.com

36

 	

ross.burton@arm.com

26

 	

david.reyna@windriver.com

23

 	

bruce.ashfield@gmail.com

21

 	

randy.macleod@windriver.com

16

 	

richard.purdie@linuxfoundation.org

11

 	

saul.wold@windriver.com

10

 	

JPEWhacker@gmail.com

9

 	

sakib.sajal@windriver.com

9

 	

Aryaman.Gupta@windriver.com

7

 	

tim.orling@konsulko.com

6

 	

mhalstead@linuxfoundation.org

4

 	

jon.mason@arm.com

4

 	

akuster808@gmail.com

3

 	

hongxu.jia@windriver.com

2

 	

pavel@zhukoff.net

2

 	

pgowda.cve@gmail.com

2

 	

Qi.Chen@windriver.com

2

 	

tvgamblin@gmail.com

2

 	

sundeep.kokkonda@gmail.com

2

 	

ptsneves@gmail.com

1

 	

aehs29@gmail.com

1

 	

Martin.Jansa@gmail.com

1

 	

nicolas.dechesne@linaro.org

1

 	

thomas.perrot@bootlin.com

1

 	

martin.beeger@online.de

1

 	

Ahmed.Hossam@opensynergy.com

1

 	

behanw@converseincode.com

1

 	

sgw@bigsur.com

1

 	

alexandre.belloni@bootlin.com

1

 	

ola.x.nilsson@axis.com

1

 	

raj.khem@gmail.com

1

 	

mostthingsweb@gmail.com

1

 	

shachar@vdoo.com

1

 	

luca.ceresoli@bootlin.com

1

 	

alejandro@enedino.org

1

 	

open.source@oleksandr-kravchuk.com

1

 	

Grand Total

214

 	

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

             reply	other threads:[~2022-08-01 21:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 21:36 sjolley.yp.pm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-11  6:37 Current high bug count owners for Yocto Project 4.1 sjolley.yp.pm
2022-10-04  2:35 sjolley.yp.pm
2022-09-27  0:07 sjolley.yp.pm
2022-09-19 22:01 sjolley.yp.pm
2022-09-13  0:39 sjolley.yp.pm
2022-09-06  0:43 sjolley.yp.pm
2022-08-29 19:48 sjolley.yp.pm
2022-08-23  0:37 sjolley.yp.pm
2022-08-15 20:58 sjolley.yp.pm
2022-08-08 23:19 sjolley.yp.pm
2022-07-18 20:03 sjolley.yp.pm
2022-07-11 22:11 sjolley.yp.pm
2022-07-04 20:59 sjolley.yp.pm
2022-06-27 22:47 sjolley.yp.pm
2022-06-20 23:27 sjolley.yp.pm
2022-06-14 14:16 sjolley.yp.pm
2022-06-07 15:22 sjolley.yp.pm
2022-05-30 23:01 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='0dae01d8a5ee$bf12f600$3d38e200$@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).