Poky Project Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: poky@yoctoproject.org
Subject: Re: Fixes for bugs with 1.0 M3 target milestones?
Date: Fri, 04 Feb 2011 09:33:06 -0800	[thread overview]
Message-ID: <4D4C3852.6090406@linux.intel.com> (raw)
In-Reply-To: <20110204092905.45870D2B4BD@gemini.denx.de>

On 02/04/2011 01:29 AM, Wolfgang Denk wrote:
> Hi,
>
> I notice that there are a number of bugs open that are (1) more or
> less directly visible to the "end user" or "customer" (i. e. not only
> "build problems" that are mostly visible to engineering) and that (2)
> are marked with a "1.0 M3" target milestone, for example:
>
> Bug 154 - libtool has incorrect paths embedded
> Bug 227 - meta/packages/meta/*toolchain*
> Bug 336 - [QT] fotowall display abnormal on eMenlow
> Bug 348 - [QT] fotowall segfaults with "Painter not active"
> Bug 412 - lttv can't be loaded in GUI mode
> Bug 443 - zypper encounter segfault when startup with qemuppc
> Bug 452 - [Qt] qtdemo warning: missing Qt database driver
> Bug 555 - After untar sdk tarball to /opt/poky, My root folder's user info is changed!
> Bug 580 - poky-qemu does not make proper use of CROSSPATH (breaking distcc)
> Bug 603 - [Netbook]Connection preferences did not enable wireless networks
> Bug 610 - no rootfs and dtb file in qemumpc8315e-rdb milestone build
> Bug 615 - [multimedia] video player reports error when open video files
> Bug 616 - [multimedia] No sound from machine when playing audio files
> Bug 658 - The bottom icons on Applications and All screen are cut-off in qemu.
> Bug 659 - The gcc/g++ is not built in the poky-image-sdk-routerstationpro-.*
>
> [this is just a selection, mostly bugs that are on my own radar, too]
>
> Bugs that affect basic functionality (video player mnot working,
> audio player not working, fotowall not working) are pretty much of
> show stoppers; also bugs that impair the general appearance (like the
> cut-off icons) result in poor first impressions.
>
Agreed.

> With the "1.0 M3" target milestone not being too far away I wonder if
> these bugs will really be fixed until then? Some of these bug reports
> are actually pretty old...
>
Thanks for your input, you are correct 1.0 M3 is right around the corner 
and a number of these bugs are not even close to being fixed.  We are 
going to be focusing M4, which is from now until mid-March on bug fixing.

I will be working the IRC channel (#yocto) weekly on a bug scrub, I will 
take this input and ensure these get marked for M4.  If you have any 
suggested fixes, please feel free to submit patches.

On that note, if you do submit patches with Bug fixes, please add the 
following to your commit message:  [BUGID #NNN].  We have a scanner for 
this format.



Sau!

> Thanks!
>
> Wolfgang Denk
>



      reply	other threads:[~2011-02-04 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04  9:29 Fixes for bugs with 1.0 M3 target milestones? Wolfgang Denk
2011-02-04 17:33 ` Saul Wold [this message]

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=4D4C3852.6090406@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=poky@yoctoproject.org \
    --cc=wd@denx.de \
    /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