Skip to contentSkip to conversation

Fixes for bugs with 1.0 M3 target milestones?

DISCUSSION Wolfgang Denk 2 participants 2 messages Feb 4, 2011

lore
Share & tools
lore
#0 lore raw

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.

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!

Wolfgang Denk

Signature · 5 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected]
Always borrow money from a pessimist; they don't expect  to  be  paid
back.
#1 lore raw
Quoted 23 lines · Wolfgang Denk

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-.*

Quoted 7 lines

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

Quoted 4 lines

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!

Quoted 4 lines

Thanks!

Wolfgang Denk