All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jolley, Stephen K" <stephen.k.jolley@intel.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Unassigned Bugs - Help Needed
Date: Mon, 16 Jul 2018 20:19:29 +0000	[thread overview]
Message-ID: <9ADD3FDE8B189B4AA2F8A3C711F8155EC73633A2@fmsmsx111.amr.corp.intel.com> (raw)

[-- 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 --]

             reply	other threads:[~2018-07-16 20:19 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 20:19 Jolley, Stephen K [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-08 16:31 Yocto Project Unassigned Bugs - Help Needed 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-09-03 15:53 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-09 14:59 Jolley, Stephen K

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=9ADD3FDE8B189B4AA2F8A3C711F8155EC73633A2@fmsmsx111.amr.corp.intel.com \
    --to=stephen.k.jolley@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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.