I want to ask how I can find the bugs in bugzilla which are listed in the "Quality Data" Table. It feels that there are more bugs which are not listed. For example: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57694 Actually the compiler returns "not implemented" while compiling the given example code but it seems that this bug is not tracked in the actual quality data.
my question is: Which is the selection criteria that a bug is related to the release. What is maybe the missing information in a bug report to add the bug to that list. Can I help by give some more example code or any other "simple" things to support the process a bit? Regards Klaus > Status > ====== > > The trunk is still in Stage 4, which means only patches fixing regressions > and documentation issues are appropriate. > > Comparing to last year's status reports, we are something in between a > fortnight and month behind the last year's schedule, but if enough attention > is given to the remaining P1 blockers, we could still release around the > beginning of April. > > The list of secondary architectures has changed recently, so to remind people > I'm including it here: > > The primary platforms are: > > arm-linux-gnueabi > i386-unknown-freebsd > i686-pc-linux-gnu > mipsisa64-elf > powerpc64-unknown-linux-gnu > sparc-sun-solaris2.10 > x86_64-unknown-linux-gnu > > The secondary platforms are: > > aarch64-elf > powerpc-ibm-aix7.1.0.0 > i686-apple-darwin > i686-pc-cygwin > i686-mingw32 > s390x-linux-gnu > > > Quality Data > ============ > > Priority # Change from last report > -------- --- ----------------------- > P1 9 - 23 > P2 75 - 12 > P3 15 - 6 > -------- --- ----------------------- > Total 99 - 41 > > > > Previous Report > =============== > > http://gcc.gnu.org/ml/gcc/2014-02/msg00013.html > > > The next report will be sent by me again, hopefully announcing > the first GCC 4.9.0 release candidate soon. >
