I hear what you're saying, Rey... and please don't take my comments as a knock on the core team or plug-in authors. I benefit greatly from the efforts of all you guys without having to pay a dime!
And I know it takes time to test and time is money! That's why I said I'd be willing to pay a monthly fee to access information that immediately provided feedback about any current core or plug-in version and it's relationship to all other core versions and plug-ins and have that fee go to reimburse the core team and plug-in authors for the time spent in testing and inputting the test results into the system. And it would save me a lot of time trying to track down the information myself. I think what we're seeing are natural growing pains of a technology that is really taking off. But like any good business, for it to be sustainable, it's got to have organization which will allow newcomers to join the community without being overwhelmed with the options and compatibilities. I'd be willing to develop an "information clearinghouse" if it would be utilized. It would greatly help me, if, say, I develop something for a website and a month later saw a new feature or plug-in for jQ that I wanted to put into that month-old website. I would like a one-stop location to go to find out in a moment whether or not a particular plug-in would require a core upgrade and if plug-ins on which the plug-in I want to use is dependent are compatible with a new core upgrade. It's just a matter of building a relational database and inputting the necessary information. The core team and plug-in authors could handle that as they get test results. Rick -----Original Message----- From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Rey Bango Sent: Saturday, July 28, 2007 11:13 AM To: jquery-en@googlegroups.com Subject: [jQuery] Re: How does everyone handle the constant updating of jQuery and plug-ins? Hi Rick, This is definitely a concern shared by many and believe me that we to great lengths to ensure that things don't break. Plugin compatibility is so important yet one of the things that we've found during the development process is that few plugin authors actually check for issues when we announce a new version of jQuery. The majority wait until after the final version is released and only after someone has reported an issue. One of the things that we *always* do is announce alpha, beta and release candidates to give ample time for everyone, both developers and plugin authors, a chance to see if anything breaks. And the code is in SVN so there's no reason for someone to not be able to test it. As with any development effort, testing is the part that everyone hates but we really need you guys in the community to pound on the early releases to ensure that your code doesn't break. The jQuery team is small as it is and we like it that way because it allows us to have a streamlined approach to things. So unfortunately, apart from the official plugins, we need to continue to rely on the plugin authors and the community to test things out. With so many plugins in the repo, its just too big of a task to test all of them out. Rey... Rick Faircloth wrote: > We need some kind of system where plug-ins are tested and deemed > compatible with this version or that version of the core and not with > some other version.
