If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Often in software engineering, fixing minor bugs can cause regressions or the introduction of major bugs.
Early in the process you define target levels for each category of bug before release.
Aiming for no known bugs is often not realistic with complex software. Each bug fix cycle introduces new bugs. You asymptotically reach 0 bugs if you are lucky. Otherwise the cycle never ends and you don't release in a timely manner.
What I mean is that there are dozens of P2 bugs still open! They only fixed for now the P1.
In GCC there are many bugs open sinece 4.0 release.
I wish LLVM, Clang and friends will reach a stable and ready to use status soon.
The same problems apply for LLVM aswell, the reason 2.7's release has been pushed forward is due to release blockers, and just like gcc they have non-critical bugs hanging around from previous releases. It's just a fact with big complex projects, have you ever looked at a Microsoft Visual Studio service pack?
No. KDE 4 has only the "KDE" name in common with KDE 3. It's not a new version. It's a new project altogether.
Also wrong, acutally many projects were able to share lots of code and only rewrite small portions. Just look at KIO e.g. -- one of the core libs of KDE -- a lot of old code in there. And that says nothing about the quality.
It is possible that there were no "new" known bugs in the kde 3.5.10 release, since that was a relativly minor bugfix release. But it's ridiculous to claim that there aren't any older ones still hanging around. And LLVM/Clange/etc. are going to have the exact same thing happen to them. It happens to every major project out there, the only way to avoid it is to spend 5+ years frozen with no new features and only bugfixes, and if that were to ever happen people would just abandon the old project and create a fork that did take new features so that it wasn't falling so far behind the competition.