Attending: DaveMethvin, gibson0421, markelog, m_gol

link Issues and PRs

• https://github.com/jquery/jquery/issues/1874
  • save the function wrapper (Sizzle)
• http://bugs.jquery.com/ticket/4320
  • Is this still needed for IE8+?
  • markelog can not repro in IE8 using the test case attached
• https://github.com/jquery/api.jquery.com/issues/597
  • misplaced, asked him to post on our shadowroot ticket
• https://github.com/jquery/jquery/issues/1784
  • not clear how to handle this
  • new APIs?
  • special behavior when context is a shadow root?
  • continue to wait for stds/impl guidance before changing stuff
• https://github.com/jquery/jquery/issues/1875
  • Seems good
• https://github.com/jquery/jquery/pull/1879
  • Nope, too much of a special case and we don't want globals
• Distribution issues - https://github.com/tildeio/rsvp.js/issues/327
  • worth a read
  • Author in ES6, compile to AMD/CommonJS?
  • https://github.com/esnext/es6-module-transpiler
• Plain objects
  • Very few methods work on it http://api.jquery.com/jquery/
  • Let's deprecate in 3.0 and remove later
• https://github.com/jquery/jquery/pull/1847
  • Yep!
• https://github.com/jquery/jquery/pull/1821
  • Promises/A+ compat
  • let's land that as-is and work on gibson042 enhancement

Attending: gibson0421, m_gol, timmywil

link Sizzle issues:

• https://github.com/jquery/sizzle/issues/290 - new buggyQSA test

link Issues and PRs

• 3.0 milestone: What can be landed now?
  • Assign 3.0 milestone when accepting for 3.0
• Promises/A+ compat
  • https://github.com/jquery/jquery/pull/1821
• gibson042 proposing a change for chained .done()
• m_gol to look into better integration with tests
• Landing https://github.com/jquery/jquery/pull/1837

link Shadow DOM support

• .offset() https://github.com/jquery/jquery/issues/1784
• Sizzle roots https://github.com/jquery/sizzle/issues/296
• Wait for guidance from standards and impls

Attending: DaveMethvin, markelog, timmywil

link Additional issue tracker things

• wontfix? (done)
• cantfix?
• needs review (team needs to review the issue/PR) (done)
• I don't think we want "fixed" or "notabug", too noisy and not particularly useful to search
• "valid and fixed" issues should be assigned to a milestone, be sure they are when committing code that closes an issue
• Always set a milestone when assigning an issue, and always assign the issue before closing with a fix/patch
• Always create an issue for a PR, so the issues have a complete list of the problems solved

link Branch naming still needs to be done

• rename "1.x-master" to "compat"
• also change name in package.json - “jquery-compat”
• handle 4 remaining PRs to 1.x-master, then remove the branch; PRs:
  • https://github.com/jquery/jquery/pull/1506
  • https://github.com/jquery/jquery/pull/1652
  • https://github.com/jquery/jquery/pull/1664
  • https://github.com/jquery/jquery/pull/1704
• don’t merge anything to 1.x-master from now on
• Both versions need package.json rename to 3.0.0-pre

link Issues and PRs in the 3.0 milestone

• What can be landed now?
• Promises/A+ compat
  • https://github.com/jquery/jquery/pull/1821
• gibson042 proposing a change for chained .done()
• m_gol to look into better integration with tests

link $.xhr -- replaced by $.fetch

• Let's do this as a plugin with its own schedule

link Issues and Pull Requests

• Assign milestones to all issues