On Monday 23 February 2009, Kevin Kofler wrote: > Timothy Murphy wrote: > > KNode crashes about 50% of the time when I post something. > > I know this has been reported as a bug, > > but I wondered if anyone has worked out when it happens, > > and if so whether it is possible to circumvent it? > > https://bugs.kde.org/show_bug.cgi?id=182322 > > This will be fixed in kdelibs-4.2.0-11.fc10, now building in Koji. > > This was fixed upstream back on January 29! We need more efficient ways to > identify serious bugs such as this and their fixes so we can get the fixes > backported in a timely manner. Having KNode completely broken a month after > upstream fixed the problem is not acceptable! > > Some questions we should ask ourselves: > * Why was this not caught before 4.2.0 got pushed to testing? The update > was only pushed to testing on February 5, if we had known about the issue > and the fix we could have fixed it right away. > * Why was this not caught when 4.2.0 was still in testing? The update was > only pushed to stable on February 13, if we had known about the issue and > the fix we could have fixed it before the update hit stable. > * Once the bug was finally noticed (after the update hit stable), why did > it take so long to find out that this is already fixed upstream and the > revision? (Or if anybody already knew about it, why didn't you backport the > fix or ask us to backport it? KNode being entirely unusable sure deserves > an immediate fix!) > I'd have to check, but I'm pretty sure I reported this loudly before the release.
