Attending: DaveMethvin, timmywil, m_gol

link 1.11.1 / 2.1.1 RC2

• Shipped last week
• Any feedback or bugs?

link 1.11.1 / 2.1.1 final

• Release? How about Thursday 5/1
• Code changes to land:

• http://bugs.jquery.com/ticket/14824 (markelog)
• https://github.com/jquery/jquery/pull/1566
• http://bugs.jquery.com/ticket/14894 (dave)
• Build/Test changes aren't blockers
• (Let's stay conservative here)

link Sizzle pulls

• https://github.com/jquery/sizzle/pull/259
• https://github.com/jquery/sizzle/pull/260

link Velocity: replacement for $.animate

• http://julian.com/research/velocity/
• MIT licensed
• Wonder how compat it is?
• Related: Should we bring back requestAnimationFrame?

link 1.12/2.2 planning

• Tickets and pulls already tagged
• Who wants what?
• Take a look and let's discuss next week
• We'll do async

Attending: DaveMethvin, timmywil, markelog, gibson042

link 1.11.1 / 2.1.1 RC

• m_gol did RC1
• I published an RC1 blog post for about 5 minutes
• I missed the update required to Sizzle (but there was a ticket)
• gibson042 landed it Friday
• Dave set up a VM, can (or will try to) publish the beta today
• To simplify, let's call this RC2 and not speak of RC1 :-)

link "browser" KEYWORD for npm

• https://github.com/npm/npm/issues/4321#issuecomment-40880868
• Dave will open a ticket

link Open tickets for .1 release

• IE11 being stupid

• http://bugs.jquery.com/ticket/14894
• Dave will fix

• Way to prevent accidental release without latest Sizzle

• http://bugs.jquery.com/ticket/14915
• Some of this is just procedure, and not code
• timmywil to land later this week before final release

• slideUp/Down on inline elements

• http://bugs.jquery.com/ticket/14824
• markelog to investigate

• We're getting a ton of spam on the tracker

• Ideas on how to reduce it?
• Delete the spammy posts when you see them
• Lots of fake logins being created as well

Attending: DaveMethvin, m_gol, markelog, gibson042

link 1.11.1 / 2.1.1

• Bugs or feedback since release?
• Open tickets for release

• http://bugs.jquery.com/query?status=%21closed&status=%21pending&group=milestone&report=3&order=priority

• ship date for next beta?

• thursday 17th

link Ticket/pull discussion

• Multiple args for jQuery.merge

• http://bugs.jquery.com/ticket/14982
• https://github.com/jquery/jquery/pull/1556
• Not really a fan unless we can use it
• close plugin

• DOMNodeRemoved text node

• http://bugs.jquery.com/ticket/14986
• https://github.com/jquery/jquery/pull/1558
• let them do it with a hook

• Event capturing support

• http://bugs.jquery.com/ticket/14953
• Lots of implications, e.g. trigger()ing
• close wontfix

• Changes to tags for Bower?

• https://github.com/jquery/jquery/pull/1542
• Doesn't seem like we need any changes
• nope, no changes and close the PR

• npm 1.x tag

• https://github.com/jquery/jquery/pull/1553
• good as-is

• Karma!

• https://github.com/jquery/sizzle/pull/236
• https://github.com/jquery/jquery/pull/1517
• https://github.com/jquery/jquery/pull/1555
• markelog to land

Attending: DaveMethvin, m_gol, timmywil, markelog

link 1.11.1 / 2.1.1

• Bugs or feedback since release?
• Open tickets

• http://bugs.jquery.com/query?status=%21closed&status=%21pending&group=milestone&report=3&order=priority

link Forum thread: http://forum.jquery.com/topic/matchers-and-pseudos

• timmywil and/or gibson042 comment?

• isn’t this just https://github.com/jquery/sizzle/issues/254?
• yes, i think it is!

link http://bugs.jquery.com/ticket/1477

• May be a cantfix
• I hate focus issues. A LOT.

link Karma

• markelog finishing this up soon

link Browser support

• m_gol to add iOS6 and Android 4.0+ to support page
• Need to fix Android 2.3 on unit tests
• Need a solution for WWA support to avoid regressions!

Attending: DaveMethvin, m_gol, gibson042, markelog, timmywil

link 1.11.1 / 2.1.1

• Need a shipper! Dave can't run jquery-release on Windows
• m_gol to do a release
  • Done! (during the meeting)
• m_gol points out we're failing tests on IE7 (inline block)
  • http://swarm.jquery.org/result/1713098
  • gibson042 to clean it up -- done
• Dave will do the blog post
  • http://blog.jquery.com/2014/03/24/jquery-1-11-1-beta-1-and-2-1-1-beta-1-released/
• Once we ship, let's hope for some feedback

Attending: DaveMethvin, gibson042, m_gol, markelog, timmywil

link 1.11.1 / 2.1.1

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

• Create new ticket to rewrite XML tests to avoid them being cross-document
• The PR to be nixed in favor of removing cross-doc manip in tests
• Ticket: http://bugs.jquery.com/ticket/14796

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

• Looks like we do need to fix this
• dmethvin to land

• http://bugs.jquery.com/ticket/14038

• Push to 2.2 because it's ugly

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

• Just document cssNumber?
• Don't want to embed non-W3C vendor-specific properties
• Related PR landed: https://github.com/jquery/jquery/pull/1536

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

• m_gol to write a test failing in IE8

• http://bugs.jquery.com/ticket/14882

• let’s blacklist iOS7 and wait (forever) for a real bug report

• http://bugs.jquery.com/query?status=assigned&status=new&status=open&status =reopened&group=milestone&report=3&order=priority

• Please land your fixes ASAP

link Old browser job

• Still broken, it's an infra problem most likely

link Failing oldIE tests -- how to fix?

• Wait until we switch to karma

link Browser support blog post

• Still need UI team input

Attending: DaveMethvin, markelog, gibson042

link 1.11.1 / 2.1.1

• https://github.com/jquery/jquery/pull/1514
• Create new ticket to rewrite XML tests to avoid them being cross-document
• Dave to create new ticket
• https://github.com/jquery/jquery/pull/1532
• Just back out the #14394 !important bug fix?
  • YES, but commit the new tests
  • m_gol to do it
• https://github.com/jquery/jquery/pull/1531

• Looks like we do need to fix this

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

• Land now?

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

• Just document cssNumber? YES
• Don't want to embed non-W3C vendor-specific properties

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

• LGTM
• m_gol: I’d hold off, probably reverting the !important patch will fix it by itself. I’d just land the tests

• http://bugs.jquery.com/query?status=assigned&status=new&status=open&status=reopened&group=milestone&report=3&order=priority

• Please land your fixes ASAP

link Old browser job

• Failing oldIE tests -- how to fix?

• Revert fake timers? I hope not.
• Wait until we switch to karma

• Browser support blog post

• Still need UI team input

• $.fn.data

• Land this in 1.12 / 2.2? YES
• Should we fix the clearly broken 2.1 now? NO

Attending: DaveMethvin, rwaldron, m_gol, gibson042

link Wrap up on browser support in 1.12/2.2

• Dave has draft blog post
• Stop accepting new bug reports on these, close wontfix
• Only fix severe regressions but leave patches in for 1.12 & 2.2
• Sync with UI to remove IE 7 etc support there too
• Still needs edits to clarify, want to prevent wails of protest
• Changes won't come until 1.13, months away
• We'll pull IE6/7, Safari 5.1, Opera 12.1x all at once in 1.13
• per markelog, what about IE7 CV mode in IE8?

link $.fn.data API

• Let's make a call on this, need to make 1.x and 2.x compat
• What is the easiest & least disruptive behavior change?
• I'm leaning towards 1.x behavior with minor changes
• Conclusion: "Embrace HTML5" with one exception: Don't camelize objects that are extended into the data object
• TODO: clean up docs for .data() to make things clearer

link Bower

• Did timmywil's latest updates take care of this?
• e.g. http://bugs.jquery.com/ticket/14837 (need more info?)

link support.boxSizing - why is the test so complicated & requires a body?

• check old Androids
• ask mikesherov

link 1.11.1 and 2.1.1

• Land fixes soon so we can move on to 1.12 and 2.2 in master
• Can always branch later if we need 1.11.2 etc

link Current open tickets

• http://bugs.jquery.com/query?status=assigned&status=new&status=open&status=pending&status=reopened&milestone=1.11.1%2F2.1.1&milestone=1.11.1&milestone=2.1.1&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&order=priority
• Pre-release deadline: March 20?

Attending: DaveMethvin, m_gol, gibson042, markelog, rwaldron

(Chat was held on the Google Doc, IRC was flakey)

link Job for underachieving old browsers being put out to pasture

• https://github.com/jquery/infrastructure/issues/242#issuecomment-35852938

• "Weekly Job" is the name

link $.fn.data API

• Let's make a call on this

• https://github.com/jquery/jquery/pull/1515
• https://docs.google.com/spreadsheet/ccc?key=0Aj5JJFjq9rZDdFpCNDZucDgwRVMtaHQyd1RVN0JFamc#gid=0
• http://bugs.jquery.com/ticket/14799
• OUTCOME: Check with rwaldron

• Do we want to make two new entry points for a “pure js” data object with no “black magic” and a “dataset” that only works on elements/with string values
• “the new API is not going to fix any of this, since people will still want .data() to work they way they expect, and populate with JSON data to initialize, etc.” - Dave’s reasoning against
• We need to bring 2.x into compat with 1.x behavior

link Bower

• Did timmywil's latest updates take care of this?
• Do we need to update older tagged versions?

link Wrap up on browser support in 1.12/2.2

• Proposed: Keep IE6/7 in 1.12.x (last one), fork Sizzle to remove non-jQuery-2.x browser support

• Announce the end of the line in a blog post

• Do we really fail a lot of tests on Safari 5.1?
• OUTCOME: Dave to write up a blog post
• We'll pull IE6/7, Safari 5.1, Opera 12.1x all at once in 1.13

link Android 4.0 & $.trim

• this was the only test failing consistently in Android 4.0
• OUTCOME: Just use a regex

link $.xhr

• Need to start work on this
• 1.11.1 and 2.1.1

link Maintenance fixes?

• Let's land these soon and use master for 2.2

Attending: DaveMethvin, m_gol, markelog, rwaldron, timmywil

link 1.11.1/2.1.1

• Problems?
• reliableMarginRight issue
  • do we even need the detect on master? always true it seems
  • http://bugs.jquery.com/ticket/11441
  • only Safari 5.0?
  • no, Android 2.3 as well :(
  • removing it gains 167 bytes on 1.x
• Schedule?
  • After the conf unless something critical comes up

link Blog post on delegated events

• https://github.com/blog/1756-optimizing-large-selector-sets
• timmywil came up with some optimizations
  • good to land in .1 release? no reason not to now
• blog post will wait a bit, also want to put in gibson042 feedback
• Hook could have been done without messing internals

link Test infrastructure

• looking better
• only IE6 is failing, just stops dead, maybe sinon related
• need to guard clearTimeout usage in inject.js - m_gol to do a PR
  • https://github.com/jquery/testswarm/issues/298
  • https://github.com/jquery/qunit/pull/511
• iOS6 needs only one PR to land and it passes tests!
  • https://github.com/jquery/jquery/pull/1496
• iOS7 has moar bugs (still <5 though), but we’ll get there
• Android 4.4 passes, should we add it?
• set up a scheduled job to run mobile Android tests

link api.jquery.com (and every site on WordPress!)

• didn't need Migrate after all, fixed

link 1.12/2.2 planning for San Diego meeting

• sent around a Google Docs link