Jean-Marc Lasgouttes wrote:
I agree with you that it is necessary to force developers to fix bugs, even small ones.I see you were not the guy who had to try to sort out problems in 1.2.0 or 1.2.1. I can tell you that trying to get bugs fixed when people are more interested in kernel reworks is a real pain.This may be true about big bugs in the kernel. But don't forget that we have manu small bugs/regressions that have been introduced in 1.2.0 and that never got fixed because we have more ambitious things to do. This `small cleanups' phase is also very necessary to have a polished release. There has been important work done during these last months.
When 1.2.0 was released, many new, fundamental features have been introduced that asked for thorough testing. From my point of view, the problem with 1.3.0 is that nobody understands how the inset code works. Everybody is waiting for something to happen but actually no real progress is made (at least this is my impression when reading the mailing list). Finally, we have entered a code freeze where it even seems to be impossible to commit bug fixes! This situation causes a lot of frustration, probably not only for me. I have only one big wish: That 1.3.0 with all its known problems is released as soon as possible. Then, at day 1 after 1.3.0, some of my patch will hopefully their way into 1.3.1cvs.
Michael
