yes, all the usual rules for a drupal patch apply - don't break anything in any browser. this is indeed a more onerous test for jquery upgrade that a php patch. but once the tests are passed, i think the patch is committable. my .02 On 1/13/08, Gábor Hojtsy <gabor@hojtsy.hu> wrote:
On Jan 12, 2008 5:55 AM, Moshe Weitzman <weitzman@tejasa.com> wrote:
On 1/11/08, Larry Garfield <larry@garfieldtech.com> wrote:
Seriously though, jQuery 1.2.2 is supposed to be just a bug-fix release. Given that we're in RC status, should we be upgrading as well, to keep the bug count down, or avoiding it because OMG that would be changing code in an RC?
Or put more pragmatically... Were someone to write a 1.2.2 patch for Drupal 6, would it be considered?
Yes ... Further I think that a pure bug fix release of Jquery is acceptable even after 6 goes out. We wouldn't rush out a release just for that, but i expect such a patch would be accepted.
IMHO we should consider on the grounds of Drupal functionality. Such a patch would need all JS functionality tested in "all" browsers (== the browsers people tested previous JS functionality in).
Gabor