All of lore.kernel.org
 help / color / mirror / Atom feed
* Yocto Project Unassigned Bugs - Help Needed
@ 2018-09-03 15:53 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-09-03 15:53 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 313 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6327 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-04-08 16:31 sjolley.yp.pm
  0 siblings, 0 replies; 37+ messages in thread
From: sjolley.yp.pm @ 2019-04-08 16:31 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 281 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.9', "2.99" and "Future", the more pressing/urgent issues being in
"2.7" and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

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

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-04-01 22:17 sjolley.yp.pm
  0 siblings, 0 replies; 37+ messages in thread
From: sjolley.yp.pm @ 2019-04-01 22:17 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 287 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.9', "2.99" and "Future", the more pressing/urgent issues being in
"2.7" and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

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

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-03-25 16:43 sjolley.yp.pm
  0 siblings, 0 replies; 37+ messages in thread
From: sjolley.yp.pm @ 2019-03-25 16:43 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 296 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.9', "2.99" and "Future", the more pressing/urgent issues being in
"2.7" and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

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

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-03-18 19:30 sjolley.yp.pm
  0 siblings, 0 replies; 37+ messages in thread
From: sjolley.yp.pm @ 2019-03-18 19:30 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 296 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

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

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-03-11 19:58 sjolley.yp.pm
  0 siblings, 0 replies; 37+ messages in thread
From: sjolley.yp.pm @ 2019-03-11 19:58 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 295 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

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

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-03-04 16:01 sjolley.yp.pm
  0 siblings, 0 replies; 37+ messages in thread
From: sjolley.yp.pm @ 2019-03-04 16:01 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 296 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

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

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-02-25 19:39 sjolley.yp.pm
  0 siblings, 0 replies; 37+ messages in thread
From: sjolley.yp.pm @ 2019-02-25 19:39 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 294 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

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

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-02-20  2:01 sjolley.yp.pm
  0 siblings, 0 replies; 37+ messages in thread
From: sjolley.yp.pm @ 2019-02-20  2:01 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 295 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

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

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: Yocto Project Unassigned Bugs - Help Needed
  2019-02-11 17:19 sjolley.yp.pm
@ 2019-02-13  1:56 ` nick
  0 siblings, 0 replies; 37+ messages in thread
From: nick @ 2019-02-13  1:56 UTC (permalink / raw)
  To: sjolley.yp.pm, yocto, openembedded-core



On 2019-02-11 12:19 p.m., sjolley.yp.pm@gmail.com wrote:
> All,
> 
>  
> 
> The triage team meets weekly and does its best to handle the bugs reported
> into the Bugzilla. The number of people attending that meeting has fallen,
> as have the number of people available to help fix bugs. One of the things
> we hear users report is they don't know how to help. We (the triage team)
> are therefore going to start reporting out the currently 294 unassigned
> bugs.
> 
>  
> 
> We're hoping people may be able to spare some time now and again to help out
> with these.
> 
>  
> 
> Bugs are split into two types, "true bugs" where things don't work as they
> should and "enhancements" which are features we'd want to add to the system.
> 
>  
> 
> There are also roughly four different "priority" classes right now, "2.7",
> "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
> and then "2.8".
> 
>  
> 
> Please review this link and if a bug is something you would be able to help
> with either take ownership of the bug, or send me
> (Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
> with the bug number you would like and I will assign it to you (please make
> sure you have a Bugzilla account).
> 
>  
> 
> The list is at:
> https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs
> 
>  
> 
> Thanks,
> 
>  
> 
> Stephen K. Jolley
> 
> Yocto Project Program Manager
> 
> INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 
> 
> *    Cell:                (208) 244-4460
> 
> * Email:                             stephen.k.jolley@intel.com
> 
>  
> 
> 
> 

Stephen,

I would be glad to help fix them. As I've newer to Yocto internals is there a 
list of trivial bugs or not just to help me get my feet wet?

Nick


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-02-11 17:19 sjolley.yp.pm
  2019-02-13  1:56 ` nick
  0 siblings, 1 reply; 37+ messages in thread
From: sjolley.yp.pm @ 2019-02-11 17:19 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 294 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 

*    Cell:                (208) 244-4460

* Email:                             stephen.k.jolley@intel.com

 


[-- Attachment #2: Type: text/html, Size: 6421 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-02-04 17:39 sjolley.yp.pm
  0 siblings, 0 replies; 37+ messages in thread
From: sjolley.yp.pm @ 2019-02-04 17:39 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 294 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(Stephen.k.jolley@intel.com <mailto:Stephen.k.jolley@intel.com> ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 

*    Cell:                (208) 244-4460

* Email:                             stephen.k.jolley@intel.com

 


[-- Attachment #2: Type: text/html, Size: 6402 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-01-28 17:23 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2019-01-28 17:23 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 294 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and then "2.8".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6422 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-01-21 20:10 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2019-01-21 20:10 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 295 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and then "2.8".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6452 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-01-14 17:35 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2019-01-14 17:35 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 295 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and then "2.8".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6452 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2019-01-07 20:43 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2019-01-07 20:43 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 295 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and then "2.8".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6452 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-12-10 19:01 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-12-10 19:01 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 296 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and then "2.8".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6452 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-12-03 16:08 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-12-03 16:08 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 297 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and then "2.8".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6452 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-11-26 20:22 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-11-26 20:22 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 297 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and then "2.8".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6422 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-11-19 16:43 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-11-19 16:43 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 297 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and then "2.8".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6422 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-11-12 16:27 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-11-12 16:27 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 296 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and then "2.8".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6452 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-11-05 16:28 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-11-05 16:28 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 305 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and then "2.8".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6452 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-10-29 15:02 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-10-29 15:02 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 309 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly five different "priority" classes right now, "2.6", "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.6" and then "2.7".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6439 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-10-22 15:33 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-10-22 15:33 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 305 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly five different "priority" classes right now, "2.6", "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.6" and then "2.7".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6439 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-10-15 15:01 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-10-15 15:01 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 303 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly five different "priority" classes right now, "2.6", "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.6" and then "2.7".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6469 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-10-08 16:18 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-10-08 16:18 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 300 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly five different "priority" classes right now, "2.6", "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.6" and then "2.7".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6439 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-10-01 15:42 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-10-01 15:42 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 308 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly five different "priority" classes right now, "2.6", "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.6" and then "2.7".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6469 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-09-24 15:33 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-09-24 15:33 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 308 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly five different "priority" classes right now, "2.6", "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.6" and then "2.7".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com<mailto:Stephen.k.jolley@intel.com>) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,


Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6499 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-09-10 17:38 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-09-10 17:38 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 313 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly five different "priority" classes right now, "2.6", "2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.6" and then "2.7".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6391 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-08-27 15:49 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-08-27 15:49 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 313 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6357 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-08-20 17:42 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-08-20 17:42 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 314 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6357 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-08-13 16:41 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-08-13 16:41 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 315 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6327 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-08-06 16:55 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-08-06 16:55 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 323 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6357 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-07-30 15:13 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-07-30 15:13 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 323 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6327 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-07-24 16:08 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-07-24 16:08 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The numbers of people attending that meeting have fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 327 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6328 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-07-16 20:19 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-07-16 20:19 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The numbers of people attending that meeting have fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 327 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6358 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Yocto Project Unassigned Bugs - Help Needed
@ 2018-07-09 14:59 Jolley, Stephen K
  0 siblings, 0 replies; 37+ messages in thread
From: Jolley, Stephen K @ 2018-07-09 14:59 UTC (permalink / raw)
  To: yocto, openembedded-core

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

All,



The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The numbers of people attending that meeting have fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 327 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out with these.



Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.



There are also roughly three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6".



Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (Stephen.k.jolley@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account).

The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*    Cell:                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 6338 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

end of thread, other threads:[~2019-04-08 16:33 UTC | newest]

Thread overview: 37+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-09-03 15:53 Yocto Project Unassigned Bugs - Help Needed Jolley, Stephen K
  -- strict thread matches above, loose matches on Subject: below --
2019-04-08 16:31 sjolley.yp.pm
2019-04-01 22:17 sjolley.yp.pm
2019-03-25 16:43 sjolley.yp.pm
2019-03-18 19:30 sjolley.yp.pm
2019-03-11 19:58 sjolley.yp.pm
2019-03-04 16:01 sjolley.yp.pm
2019-02-25 19:39 sjolley.yp.pm
2019-02-20  2:01 sjolley.yp.pm
2019-02-11 17:19 sjolley.yp.pm
2019-02-13  1:56 ` nick
2019-02-04 17:39 sjolley.yp.pm
2019-01-28 17:23 Jolley, Stephen K
2019-01-21 20:10 Jolley, Stephen K
2019-01-14 17:35 Jolley, Stephen K
2019-01-07 20:43 Jolley, Stephen K
2018-12-10 19:01 Jolley, Stephen K
2018-12-03 16:08 Jolley, Stephen K
2018-11-26 20:22 Jolley, Stephen K
2018-11-19 16:43 Jolley, Stephen K
2018-11-12 16:27 Jolley, Stephen K
2018-11-05 16:28 Jolley, Stephen K
2018-10-29 15:02 Jolley, Stephen K
2018-10-22 15:33 Jolley, Stephen K
2018-10-15 15:01 Jolley, Stephen K
2018-10-08 16:18 Jolley, Stephen K
2018-10-01 15:42 Jolley, Stephen K
2018-09-24 15:33 Jolley, Stephen K
2018-09-10 17:38 Jolley, Stephen K
2018-08-27 15:49 Jolley, Stephen K
2018-08-20 17:42 Jolley, Stephen K
2018-08-13 16:41 Jolley, Stephen K
2018-08-06 16:55 Jolley, Stephen K
2018-07-30 15:13 Jolley, Stephen K
2018-07-24 16:08 Jolley, Stephen K
2018-07-16 20:19 Jolley, Stephen K
2018-07-09 14:59 Jolley, Stephen K

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.