Hi Stephan,
Perhaps i'm splitting hairs or arguing over semantics here, though. i
I think we're saying the same thing but from two different perspectives. An expectation that the jQuery team will test every plugin isn't a reasonable one nor is it reasonable for anyone to expect an independent plugin author to do the same for their work.
In an ideal world, I think everyone would have a sense of responsibility to support their contributions but thats not how OSS development works on many occasions. You said it perfectly that many authors need to scratch an itch and hence, a plugin is born. This is why we REALLY scrutinize plugins to determine what is an official jQuery plugin. The official plugins have been adopted by the project and will always be upgraded to support the latest jQuery release but apart from that, its up to the community to get involved.
My advice to all who are concerned about this is to engage the plugin authors in some way to motivate them to update their work. If they don't want to, then consider adopting the plugin and enhancing it. That's happened on several occasions which much success.
admit that i have a hard time viewing the world through a normal user's eyes, as 98% of my time is spent in hacker-land, and coders and users often have much different expectations.
Join the club my man! ;) Rey
