GCC 4.5 was not in a good shape as of the middle of March with it still not being ready due to 16 outstanding P1 regressions, but over the past two weeks, developers have feverishly been fixing these bugs and the count is now down to zero. For P2 regressions, 17 of them have been fixed too over this time span, which brings the second-tier bugs down to a count of 81. There is also one new P3 regression bringing its count to three...
But there is such a thing as software without known bugs. Of course it's not practical to always solve all confirmed bugs before a release. But it's theoretically possible to do bugfixes until the bug tracker is empty. I'm curious what would happen if all software projects would pick up a policy: no new features until the confirmed bug list is empty.
But there is such a thing as software without known bugs.
only if the developers are totally ignorant, there are no testers/users, or there's some weird definition of "bug" that allows one to classify all bug reports as invalid.
Show me one large project with an empty bug tracker before release.
Originally Posted by Remco
I'm curious what would happen if all software projects would pick up a policy: no new features until the confirmed bug list is empty.
No new releases for the next 5 years. As a consequence, distributions start randomly shipping git versions. All hell breaks loose.
Oh, and no Linux-user is allowed to buy new hardware, since new drivers = features.