All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Yocto Project Discussion <yocto@yoctoproject.org>,
	 "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Bugzilla has returned - Bug Triage Plans
Date: Thu, 27 Jan 2011 16:41:40 -0800	[thread overview]
Message-ID: <4D4210C4.6080306@linux.intel.com> (raw)


Folks,

Apologies for the extended absence of bugzilla.yoctoproject.org, it is 
back up now and working.

As we head into the next phase of Poky / Yocto Metadata 1.0, we need to 
have people evaluate the existing bugs and determine if they can be 
fixed for 1.0 or need to be marked for the next release.

Currently there are 170 open bugs, we need to go through these and 
ensure that their Importance and Target Milestones are correct.

I will be holding a Bug Triage meeting via the #yocto IRC Channel at two 
times, in order to accommodate the global nature of the Yocto Project. 
These will be about :30 to :45 minute meetings.

Tue February 1st @ 17:30 GMT / Tue 09:30 PST / Wed 01:00 China
Wed February 2st @ 07:00 GMT / Tue 23:00 PST / Wed 15:00 China

Please join the team to discuss any bugs that you have an interest in. I 
will be the "bug caller" at those times in order to facilitate some 
semblance of order.

You can also send email or place a bugzilla comment directly for those 
bugs that are important to you or your project.

Thanks for your support of the Yocto Project

-- 
     Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System



             reply	other threads:[~2011-01-28  0:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28  0:41 Saul Wold [this message]
2011-01-28  0:57 ` [yocto] Bugzilla has returned - Bug Triage Plans Zhang, Jessica
2011-01-28  0:57   ` Zhang, Jessica

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=4D4210C4.6080306@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=poky@yoctoproject.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.