jQuery Core Team Meeting – Apr 08 2013

Attending: DaveMethvin, gibson042, orkel, timmywil, gnarf, rwaldron

link jQuery 2.0

link jQuery 1.10

  • Mentioned quickly in 2.0 beta 3 blog post
    • Dave working on blog post; shared here
    • Ship a month or two after 2.0, near Portland conf

link Document differences 1.x to 2.x

  • 2.x data can be attached anywhere
  • ???

link Open tickets triage

jQuery Core Team Meeting – Apr 01 2013

  • Attending: DaveMethvin, gibson042, orkel, timmywil, rwaldron, scott_gonzalez, jrburke, tbranyen

link jQuery 2.0

link Removing named global jQuery for AMD (tbranyen suggestion, jrburke joins)

  • tbranyen to create a ticket

link Migrate

  • Ship 1.2 with 2.0 beta, reflecting 1.10 changes
  • All bugs closed last week
  • Still need a good approach to detect/warn on scripts
    • Approach?
  • Ship 1.3 with jQuery 2.0
  • List of changes below

link jQuery 1.10

link Document differences 1.x to 2.x

  • 2.x data can be attached anywhere
  • ???

link (Add these to Migrate Plugin and document NOW for 2.0/1.10 release)

  • No script execute by default, must use $.parseHTML
    • Groundwork for XSS reduction, but not a complete fix atm
    • This would make the no-leading-space restriction unnecessary?
  • http://bugs.jquery.com/ticket/13417 domManip and empty text nodes
  • http://bugs.jquery.com/ticket/12838 $.ajax hook point for domManip
  • change Event.isTrigger from boolean to bitmask
  • allow multiple args for .replaceWith (ref)

link Open tickets triage

jQuery Core Team Meeting – Mar 25 2013

  • Attending: DaveMethvin, gibson042, orkel, timmywil, jaubourg, gf3

link jQuery 2.0

link Migrate

  • Ship 1.2 with 2.0 beta, reflecting 1.10 changes
  • Fix sourcemap support (Scott says it's always been broken)
  • Ship 1.3 with jQuery 2.0
  • List of changes below

link jQuery 1.10

link Document differences 1.x to 2.x

  • 2.x data can be attached anywhere
  • ???

link (Add these to Migrate Plugin and document NOW for 2.0/1.10 release)

  • No script execute by default, must use $.parseHTML
    • Groundwork for XSS reduction, but not a complete fix atm
    • This would make the no-leading-space restriction unnecessary?
  • http://bugs.jquery.com/ticket/13417 domManip and empty text nodes
  • http://bugs.jquery.com/ticket/12838 $.ajax hook point for domManip
  • change Event.isTrigger from boolean to bitmask
  • allow multiple args for .replaceWith (ref)

link jQuery 1.9.2

  • None planned

link Open tickets triage

jQuery Core Team Meeting – Mar 18 2013

  • Attending: DaveMethvin, timmywil, mikesherov, rwaldron, orkel, gibson042

link jQuery 2.0 Final

  • Ship for jQuery Uk (April 19)
  • Stuff to be ironed out
    • Use in node.js

link Migrate 1.2

  • Ship with jQuery 2.0, reflecting 1.10 changes as well
  • List of changes below

link jQuery 1.10

link Document differences 1.x to 2.x

  • 2.x data can be attached anywhere

link (Add these to Migrate Plugin and document NOW for 2.0/1.10 release)

  • No script execute by default, must use $.parseHTML
    • Groundwork for XSS reduction, but not a complete fix atm
    • This would make the no-leading-space restriction unnecessary?
  • http://bugs.jquery.com/ticket/13417 domManip and empty text nodes
  • http://bugs.jquery.com/ticket/12838 $.ajax hook point for domManip
  • change Event.isTrigger from boolean to bitmask
  • allow multiple args for .replaceWith (ref)

link jQuery 1.9.2

  • None planned

link Documentation Day

link Open tickets triage

jQuery Core Team Meeting – Mar 12 2013

March 11, 2013
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, timmywil, mikesherov, rwaldron, orkel
Time: Noon ET

Official Agenda:

jQuery 2.0 Final

Ship for jQuery Uk (April 19)?

Stuff to be ironed out

.data() implementation

Use in node.js

other?

Sizzle ticket https://github.com/jquery/sizzle/pull/193

  • Timmy will land

jQuery 1.10

Hard to move quickly on this, we’ve given zero notice

Need to publicize changes (next bullet) and do a blog post

  • Dave to do blog post ASAP

Ship a month or two after 2.0? — mid-June would be Portland

(Add these to Migrate Plugin and document NOW for 2.0/1.10 release)

No script execute by default, must use $.parseHTML

  • Groundwork for XSS reduction, but not a complete fix atm
  • This would make the no-leading-space restriction unnecessary?

http://bugs.jquery.com/ticket/13417 domManip and empty text nodes

http://bugs.jquery.com/ticket/12838  $.ajax hook point for domManip

change Event.isTrigger from boolean to bitmask

allow multiple args for .replaceWith (ref)

jQuery 1.9.2 — Do we need one? (Doesn’t seem so, none scheduled)

Documentation Day

Tuesday March 12 8pm Eastern time #jquery-dev

Can we get the team together virtually to knock down the docs issues?

Document treatment of various node types ‘n stuff wrapped by jQuery

  • What can be put in a set?
  • What methods work with it?

bugs.jquery.com

  • New home page to improve people’s reporting — on Dave’s plate
  • e.g., docs issues go to api.jquery.com

Open tickets triage

jQuery Core Team Meeting – Mar 11 2013

  • Attending: DaveMethvin, timmywil, mikesherov, rwaldron, orkel

link jQuery 2.0 Final

link jQuery 1.10

  • Hard to move quickly on this, we’ve given zero notice
  • Need to publicize changes (next bullet) and do a blog post
    • Dave to do blog post ASAP
  • Ship a month or two after 2.0? — mid-June would be Portland

link (Add these to Migrate Plugin and document NOW for 2.0/1.10 release)

  • No script execute by default, must use $.parseHTML
    • Groundwork for XSS reduction, but not a complete fix atm
    • This would make the no-leading-space restriction unnecessary?
  • http://bugs.jquery.com/ticket/13417 domManip and empty text nodes
  • http://bugs.jquery.com/ticket/12838 $.ajax hook point for domManip
  • change Event.isTrigger from boolean to bitmask
  • allow multiple args for .replaceWith (ref)

link jQuery 1.9.2

  • Do we need one? (Doesn’t seem so, none scheduled)

link Documentation Day

  • Tuesday March 12 8pm Eastern time #jquery-dev
  • Can we get the team together virtually to knock down the docs issues?
  • Document treatment of various node types ‘n stuff wrapped by jQuery
    • What can be put in a set?
    • What methods work with it?

link bugs.jquery.com

  • New home page to improve people’s reporting — on Dave’s plate
  • e.g., docs issues go to api.jquery.com

link Open tickets triage

jQuery Core Team Meeting – Feb 25 2013

Attending: DaveMethvin, mikesherov, gibson042, rwaldron, timmywil

link jQuery 2.0b2

link jQuery 1.9.2

  • Still can wait a couple of weeks

link Documentation needs work

  • Dave to work on some of this in Toronto Monday
  • Move upgrade-guide stuff into api.jquery.com
  • Document treatment of various node types 'n stuff wrapped by jQuery
    • What can be put in a set?
    • What methods work with it?

link jQuery 1.10 correspondence with 2.0

link jQuery 1.10 and 2.0 final ship date

  • 2.0 to stay in beta until 1.10?
  • Encourage people to use the beta

link bugs.jquery.com

  • New home page to improve people's reporting -- on Dave's plate
    • e.g., docs issues go to api.jquery.com

link Open tickets triage

jQuery Core Team Meeting – Feb 15 2013

February 12, 2013
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, rwaldron, orkel, gibson042, siovene, timmywil
Time: Noon ET

Official Agenda:

Siovene update/discussion on perf

  • Still looking for ideas on organization, tests, etc

jQuery 2.0b2

  • This week – Day?
  • Stuff to be done before it ships? No

Things still needed for 2.0 final

Optional qSA/mS Sizzle stub

jQuery Migrate 1.1.1 late this week — Dave

Todos marked in Github issue tracker:

jQuery 1.9.2 — I think we can wait a couple of weeks

Version/feature correspondence (from last week)

  • Make 1.10 track 2.0? (So 1.11->2.1, 1.12->2.2, etc)
  • in next major point release, don’t execute scripts by default
  • Let’s leave this an open issue until we know what might need to be in each version

bugs.jquery.com

  • New home page to improve people’s reporting
  • e.g., docs issues go to api.jquery.com

Open tickets triage

http://bugs.jquery.com/ticket/13428

  • Lets hold off on action for now, potentially document that native events should not depend on using trigger data and use .triggerHandler if you need to pass data

http://bugs.jquery.com/ticket/13393

http://bugs.jquery.com/query?status=new&report=505&order=priority

jQuery Core Team Meeting – Feb 11 2013

Attending: DaveMethvin, rwaldron, orkel, gibson042, siovene, timmywil

link Siovene update/discussion on perf

  • Still looking for ideas on organization, tests, etc

link jQuery 2.0b2

link jQuery Migrate 1.1.1 late this week -- Dave

link jQuery 1.9.2

  • I think we can wait a couple of weeks

link Version/feature correspondence (from last week)

  • Make 1.10 track 2.0? (So 1.11->2.1, 1.12->2.2, etc)
    • in next major point release, don't execute scripts by default
    • Let's leave this an open issue until we know what might need to be in each version

link Open tickets triage

  • Lets hold off on action for now, potentially document that native events should not depend on using trigger data and use .triggerHandler if you need to pass data

jQuery Core Team Meeting – Feb 06 2013

February 4, 2013
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, rwaldron, timmywil, gibson042, mikesherov, jaubourg, orkel
Time: Noon ET

Official Agenda:

jQuery 1.9.1

TODAY

TestSwarm isn’t working AT ALL right now (natch)

Any other changes to be landed?

jQuery Migrate 1.1.0

  • May need a 1.1.1 to remove “use strict” there too

Build issues

grunt working well enough to wait for 0.4.0 final

still need to restore compare-size

stupid sourceMappingURL location issue

Need to check our build code when we upgrade Uglify:

Swarm failures

  • Seeing focus issues on Firefox, need to double-check

jQuery 2.0 beta2

Thursday?

should have a beta to let people exercise changes to .data()

  • Rick is working on performance optimizations for .data()

Benchmarks

Version/feature correspondence

  • Make 1.10 track 2.0? (So 1.11->2.1, 1.12->2.2, etc)
  • in next major point release, don’t execute scripts by default

Open tickets triage