Status ====== We are in Stage 3. When we reach 100 open regressions, we will go to regression-only mode; one of the release managers will announce the exact time the mode is entered. When we approach the 4.3.0 release, we will create a branch, and open Stage 1 for 4.4.0.
Quality Data ============ Significant progress has been made during the last week; I also downgraded a couple of old bugs that had been at P2 since submission without a priority ever being assigned by an RM, as well as SUSPENDED bugs waiting for standards committee decisions (which it does not make sense to treat as release-critical). Thanks to everyone who helped with fixing bugs. Priority # Change from Last Report -------- --- ----------------------- P1 12 - 6 P2 86 - 6 P3 3 + 1 -------- --- ----------------------- Total 101 - 9 5 out of the 12 P1 bugs are regressions since 4.2; the rest are regressions from earlier releases. There are 41 P4 regressions and 86 P5 regressions in 4.3; although not release-critical, they can still be fixed at any time except when the branch is frozen for releases. There are 4529 open bugs in total (although this includes bugs in areas such as the website, bugs fixed on trunk but open for 4.1 or 4.2, and enhancement requests). Component # --------- --- c++ 41 tree-optimization 18 middle-end 16 target 7 debug 6 rtl-optimization 4 bootstrap 2 c 2 inline-asm 1 other 1 preprocessor 1 regression 1 testsuite 1 Issues ====== Clearly, the C++ front end has the greatest number of (P3 or above) regressions, followed by tree-optimization and middle-end; work on these areas can have the most effect in reducing the number of regressions. 21 regressions (P3 or above) are in ASSIGNED state, in some cases since 2004. If you have regressions assigned to yourself, please ensure they have up-to-date information on your work on the bugs, or unassign them if you are no longer working on a fix. Previous Report =============== http://gcc.gnu.org/ml/gcc/2008-01/msg00136.html -- Joseph S. Myers [EMAIL PROTECTED]
