>Large scale software projects like Fedora, Debian, Ubuntu, GTK, KDE, MySQL, and numerous others have a good response time in answering and supplying critical fixes that are affecting their users. However, the various Eclipse projects have a varying degree of success when responding to similar issues. In particular, with the latest release of Ubunutu there is a known problem with some button handling and GTK with Eclipse. Some say it’s a GTK problem other’s say it’s an Eclipse problem. However there is a fix in place, but unfortunately it is only currently available for 3.6. Some of the above mentioned distributions have gone and back ported the patch, but there are still numerous people that get their distributions from Eclipse.
The Eclipse developers knew about the problem before the release of Karmic Koala that contained the upgraded GTK which the eclipse platform has problems with in 3.5, and they could have had a patch ready to go on the day of release. I realize that we only have so many resources, but it is stumbles like this that I think give us a black eye now and then. With P2 we have the ability to role out patches in a more timely manner. Unfortunately, currently the earliest somebody can get this patch is either to roll it themselves, or hopefully it’ll be include in the next maintenance release (Feburary time frame).
Part of building a community is making sure that you respond timely to it’s needs. Bugs of this sort should be given higher priority than they sometimes are. If this port is in the works, then we need to announce it in as wide a forum as is possible. Responding to critical useability issues should be a priority of every project. With out your users, there is no community and no project.