My objection to the "won't fix" status is that fixing these problems may be difficult. Until we know they are fixed, we don't know if it's possible to fix them in time for the Gutsy general release. It's just wishful thinking to say "this will be in Gutsy final (soon) and the performance issues will definitely be fixed by then (very soon)".
That's the point of bug reports like this: to keep an issue open until it's confirmed fixed. It's not confirmed (in reality) yet... So why is it now "Won't Fix"? You say it's fixed in SVN, but a lot of work was done last time around which was supposed to fix them, that didn't fix the performance problems on some systems, and it didn't affect developer's systems until others tried it. These performance issues need wider feedback. Fixing it might require changes to the kernel. Until now, we don't know if there's a problem with 2.6.2x kernel I/O scheduling interacting badly with Tracker. The recent "if you have lots of non-media files you must be a developer so you can turn it off yourself" does not give me confidence that the problems are taken all that seriously. Especially when turning it off in the GUI doesn't work. But, on those systems where it's a problem, it is quite severe and in a general release would make Ubuntu look bad. "We will not enable by default in the distribution until we have made sure it works well for 99% of users" would be much more confidence inspiring. As would keeping the bug open until it's fixed and there is feedback confirming it, rather than declaring it "won't fix". -- Tracker should not be enabled by default until it doesn't clobber everything https://bugs.launchpad.net/bugs/132741 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
