Minor release for improved warnings and fixes

[Krinkle]

Would be nice if a new minor release could be cut so that the improved warnings from dc1d703 (#204) goes out.

---

The minor release from current master would contain:

• Build: add UMD support. Build: add UMD support #206
• Core: Warn on use of jQuery.holdReady(). Core: Warn on use of jQuery.holdReady() #247
• Core: Don't use .apply() on console.log to satisfy IE9. Core: Don't use .apply() on console.log to satisfy IE9 #241
• Data: Fix support object as second argument. Data: Support object as second argument #235
• Docs: Clarify wording around deprecated/removed methods. Docs: Clarify wording around deprecated/removed methods #208
• Effects: Fix for old style easing definitions compatibility. Bugfix/easing compatibility #234
• Effects: Warn on use of jQuery.fx.interval. Effects: Warn and fill jQuery.fx.interval #216
• Event: Warn and fill jQuery.event.props.concat for jQuery Mobile pre-1.5. Event: Detect jQuery Mobile pre-1.5 use of jQuery.event.props.concat #209
• Event: Warn about late use of $(window).on("load"...). Event: Warn about late use of $(window).on("load"...) #217
• Event: Use window.document to get to document. 9e3dfcb
• Event: Warn for deprecated event aliases. Event: Warn and fill event aliases #243

[dmethvin]

Yeah, a 3.2 release seems like a good idea. See #220 for why isArray isn't being warned. It's a major pain to do those warnings when there are internal uses inside jQuery itself. The positional selectors one would be really annoying since they're frequently used and I'm not sure we're ever going to remove them.

[mgol]

I think we should warn only in jQuery 3.2.0+ then, better than nothing!

[Krinkle]

From #246 (comment)

@dmethvin wrote:
Right but in general we have said that jQuery Migrate 3.x works with jQuery 3.x. If you used an older jQuery than 3.2 it would be throwing warnings frequently. Is that considered okay? In the past we tried to avoid that.

It also complicates our test matrix since we couldn't test Migrate 3.2 with a jQuery older than 3.2 and assert no warnings.

@Krinkle wrote:
@dmethvin No, I agree 3.x/3.x compat should be kept. It's our responsibility to keep that flexibility supported to reduce user confusion and upgrade smoothness. If we do want to add the warnings before Migrate 4, it would have to involve a version check.
Personally, I the complexity of a version check is worth it. The earlier the better. It would give platforms like WordPress and MediaWiki the opportunity to warn about these methods much earlier to end-users; instead of only after jQuery 4 is released.
The more users we (indirectly) enable to comfortably migrate early, the better our position is to change things in the jQuery 4 API for the benefit of everyone.

[Krinkle]

@dmethvin Added a release note draft to the start comment.
Is there anything still blocking a minor release?

[dmethvin]

Sorry @Krinkle, I'm not sure exactly what needs to be done at the moment. I need a day to go through and see where things stand. If we're going to catch all the jQuery 3.2.0 deprecations I think there are a few things left and some may not have issues yet, but that would be part of the review.

[Krinkle]

@dmethvin If we can get all jQuery 3.2.0 additions finalised soon, that'd be great. But if not, could we consider not blocking on that, and perhaps have a release with a 3.0.x or 3.1.x version number first, to get these fixes released soon?

[dmethvin]

SGTM, we can do another release later.