new version policies - specifically RE: sibling selector in 1.3.2
Pardon me for being a little late to this particular party :)
I just ran in to the "Broken sibling selector in 1.3.2" bug that was
discovered and fixed at the end of March (7 months ago!). I've worked
around it by removing the blocks of code specified in the bug report
and re-minifying it. But I wonder why I had to do that.
Why not release a version 1.3.3 (or 1.3.2.1) that fixes this? It's
seems to be a very simple fix for a relatively major feature and could
potentially save a lot of debugging time. Should *every* bug get a
point release? Of course not. But 1.3.2 has been the 'latest stable
release' for quite a while, no?
Honestly, it may be close enough to 1.3.3 (or whatever the next big
version is) for this particular issue to matter, but for future
development, this would make jQuery seem even more "production-ready"
than it already is.
Just for context, I actually had to upgrade from 1.3.1 in order to fix
the "clone of a clone" issue in IE.
_jason
--
I just ran in to the "Broken sibling selector in 1.3.2" bug that was
discovered and fixed at the end of March (7 months ago!). I've worked
around it by removing the blocks of code specified in the bug report
and re-minifying it. But I wonder why I had to do that.
Why not release a version 1.3.3 (or 1.3.2.1) that fixes this? It's
seems to be a very simple fix for a relatively major feature and could
potentially save a lot of debugging time. Should *every* bug get a
point release? Of course not. But 1.3.2 has been the 'latest stable
release' for quite a while, no?
Honestly, it may be close enough to 1.3.3 (or whatever the next big
version is) for this particular issue to matter, but for future
development, this would make jQuery seem even more "production-ready"
than it already is.
Just for context, I actually had to upgrade from 1.3.1 in order to fix
the "clone of a clone" issue in IE.
_jason
--
Topic Participants
pappy74
John Resig