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.
