Attending: DaveMethvin, gibson042, markelog, arthurvr

link jQuery 3.0 beta

• Still a LOT to do
  • https://github.com/jquery/jquery/issues?q=is%3Aopen+is%3Aissue+milestone%3A3.0.0+no%3Aassignee

link Pull Requests and Issues

• indexOf

• Seems good to have a consistent standard
• Would need to be addressed in the style guide?
• In the meantime, land the two PRs

• https://github.com/jquery/jquery/pull/1980

• land this, we can tweak

• https://github.com/jquery/jquery/pull/1975

• Can we eliminate $.support.cors and use XHR as the default transport if no other transport works?
• Would eliminate a lot of special cases
• Pinged @jaubourg on the possibility

• Skip PATCH tests on BrowserStack

• too many spurious fails from their setups for some reason

Attending: DaveMethvin, gibson042, arthurvr, m_gol, timmywil (12:45)

link Reminder: 3.0 in two weeks!

• Need owners for several tickets
• Need to land exising PRs

link Issues and PRs

• https://github.com/jquery/jquery/issues/1969
  • Is unescaped \f valid in an XHTML document attribute value?
  • Is there some way we can avoid constant XHTML issues? Can we test in XHTML perhaps for an occasional run?
  • m_gol to look at https://github.com/jquery/jquery/issues/1731
• https://github.com/jquery/jquery/issues/1967
  • jQuery.support.cors is in relatively wide use (but not formally documented) for situations like PhoneGap and IE local apps
  • Can this be fixed by selecting XHR as a default transport?
  • Continue discussion on the ticket
• https://github.com/jquery/jquery/issues/1956
  • Get using .html() (avoiding encoding) and set as .text()?

• Asking on the ticket why that can't be done

Attending: DaveMethvin, gibson042, gnarf, m_gol, jaubourg, markelog

link 1.11.2/2.1.3 release

• Done

link Issues and PRs

• Format of // Support: comments
  • https://github.com/jquery/contribute.jquery.org/issues/95
  • Spaces around the numbers and symbols, consistent with JS spacing
• Documenting a ready promise
  • https://github.com/jquery/api.jquery.com/pull/530
  • Currently on jQuery.ready, but that's an internal method
  • m_gol has https://github.com/jquery/jquery/issues/1778
  • Revisit after that ticket is resolved
• Text of a script tag
  • https://github.com/jquery/jquery/issues/1956
• Smoke-testing on Node, not assuming the browser env in source
  • PR: https://github.com/jquery/jquery/pull/1949

link Code coverage

• markelog to create an issue
  • https://github.com/jquery/jquery/issues/1965

Attending: DaveMethvin, m_gol, gibson042, markelog, timmywil

link 1.11.2/2.1.2 release

• All patches landed? They should all be here:

• https://github.com/jquery/jquery/issues?q=milestone%3A1.11.2%2F2.1.2

• Trac tickets listed under a single GH issue

• https://github.com/jquery/jquery/pull/1662 was master only

• Sizzle has been updated in master, compat, 2.1-stable, and 1.11-stable
• Add Ajax URL sanitization?

• https://github.com/jquery/jquery/issues/1875
• No, let's leave until 3.0, there are compat risks

• Release ASAP
• Need blog post draft
• Has jquery-release been updated to not copy -latest? I think so

• (in general, any changes to jquery-release needed?)

link 3.0 release - target mid-January

• Major blockers or unassigned tickets?
• Should we switch to ES6 module format for authoring?

• Can still generate both the monolithic file and AMD from that
• Move AMD modules to dist/AMD
• Breaks the build process, can’t use r.js or var modules
• Can’t load modules when testing
• Decided to not change authoring for 3.0 … wait for 4.0, better tooling and/or browser support before using ES6 for authoring

• QUnit ticket: https://github.com/jquery/qunit/issues/707

link Issues vs Pull Requests

• Let's use issues (only) for changelog
• PRs should have one or more issues, unless they're housekeeping (e.g. typos and such) in which case we don't need an issue
• Need a commit message format change here?
• gibson042 has Component name enforcement

• https://github.com/jquery/jquery/pull/1909

• Support for jquery-release to build changelog

• https://github.com/jquery/jquery-release/issues/1

link Issues and PRs

• Promises/A+ compat

• https://github.com/jquery/jquery/pull/1821
• gibson042 to work on a PR
• maximum backcompat, allow setting context, multiple resolved values, etc. (Promise/A compat for code that draws inside the standard lines)
• Use a plugin to handle the error cases?
• Might be able to use try/finally now that IE7 has been dropped

• Plain Objects

• https://github.com/jquery/jquery/issues/1776
• Do we support animation on Object
• https://github.com/jquery/api.jquery.com/issues/600
• Are the docs/units correct and complete compared to code?
• https://github.com/jquery/jquery/pull/1668
• Should we hide the expando on plain objects? Let's try exposing it and see if anyone depends on it
• Should we add .animate() and .queue() to the list of things supported for plain objects?
• .queue - yes, support on plain objects, little impact
• .animate() - let's look at velocity.js, although it may be as simple as guarding stuff with .nodeType checks