I'm surprised at the people who balk at the status "wontfix". I've been coding for 25 years, and a status of "wontfix" means all sorts of things from: "not our problem" , to "not in the spirit of our code", to "not a bug", etc. It's not a personal attack / doling out punishment, and it certainly isn't malicious refusal to help; it's a professional final decision & moving on. As soon as I saw that status, I thought--oh, okay, not jQuery's problem.
Further, experience tells us that warnings are exactly that: a program saying "Hey, by the way, in case you didn't mean to do this, I think I maybe found a problem, but if it works the way you expect, never mind, because, written by a human, I'm, NOT, AS, SMART, AS, A, HUMAN." I hope every one of you has to write a (pick a language) program someday that throws warnings and you're forced to decide whether your principles prevent you from continuing to use that language (because no good language, like C, or Java, or PHP, used in millions upon millions of devices, would ever throw warnings), or evaluate the warnings as "oh, that's just the compiler being silly; that's not a problem, actually", and (if necessary, explaining to your client's satisfaction because you own your experience) keep your job. What about all the expert programmers who just dispense with the nonsense and hide warnings from you? The warnings are still there, but now we're treading on bad policy. Suddenly, one group shuts up because they (wrongly) think there's nothing they should condider (whether or not is actually important), and another group chimes in because it's "unprofessional" to hide warnings that would be nice to know (but still aren't important).
Back to the subject, I am NOT part of the jQuery team, or at all related to the project; I am a code consumer. From my perspective, punishing experienced developers (by, e.g., refusing to use the new version) for implementing a *common/tried/true* bug-tracking system in *complimentary* code that other, experienced developers have little problem adjusting to simply means that you're limiting yourself to marginal programming, relegated to a set of doubtful hires, because we're looking for a little more experience in the people we hire. Even if you're not in the running for a programmer's job, it's like walking into a police station and complaining about the bulletproof glass because it doesn't suit you--but it's a police station (!) with its practical realities and its own culture. When in Rome (programmer's land), do as the Romans (programmers) do. If visitors need to take this observation personally, okay, but there's no reason for it (for me, the complainers, or the developers): "wontfix" is entirely the wrong target, and I'm grateful--at 5AM, trying to finish a project--for the efficiency. Thank you, dev team, for the excellent work, excellent code, and for sticking with jQuery for all this time.