jQuery Core Team Meeting – Dec 15 2014

Attending: DaveMethvin, m_gol, gibson042, markelog, timmywil

link 1.11.2/2.1.2 release

  • All patches landed? They should all be here:
  • Trac tickets listed under a single GH issue
  • Sizzle has been updated in master, compat, 2.1-stable, and 1.11-stable
  • Add Ajax URL sanitization?
  • 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

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
  • Support for jquery-release to build changelog

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

jQuery Core Team Meeting – Dec 08 2014

Attending: DaveMethvin, m_gol, gibson042, markelog

link Do we need a 1.12/2.2 release?

  • Yes
  • Release 12/15?
  • Safari selector bug, maybe one or two other low-risk patches
  • m_gol suggests starting at https://github.com/jquery/jquery/commit/e488d985cfb10ab8c684bbc6a9b8ff3eae23bf83
  • Dave to do blog post on Safari's lack of response and info on this
  • m_gol to find jQuery patches and make a branch
  • gibson042 to make a Sizzle branch
    • start at 78a8c3a7a83ebd8356ae3e23c7c1970ef6d948d2 or later
    • back out ea1c40428c85de1b08087e9c76c5518ba8d15d4f
    • add PR 297
    • maybe add PR 300

link Schedule for 3.0

  • Release target date mid-January
  • Firmer dates once we get closer

link Style guide

link Issues vs Pull Requests

  • Any bug/feature/deprecation should have an issue
  • Issues track the functional changes in the release
  • Dave to go back and check tags/milestones for pre-3.0 commits
  • Think I need to create issues for pre-closed tix in Trac

link Issues

  • Remove .context and .selector
  • Is the guard around currentStyle.left needed? Probably not

link PRs

  • to discuss next week

jQuery Core Team Meeting – Dec 01 2014

Attending: DaveMethvin, gibson042, timmywil, m_gol

link Issues and PRs

  • Just land a fix, no unit test since it's a resource leak
  • Landed in Sizzle
  • .detail used in all mouse events, now inclined to just add it
  • Just always use gBCR?
  • Maybe a bit slower but would provide fractional dimensions for width/height
  • Does gBCR also fix offset/position/width/height when elements are transformed? Need to check

link Promises/A+ compat

  • make .then() as Promise/A+ compat as it can be
  • may be a few minor behavioral things not std
  • what about extensions to the Promise/A+ spec? (context, multiple values, progress)
  • seems like we need multi values for the most common use case of $.ajax
  • keep other Deferred behavior basically unchanged
  • no need to introduce breaking changes
  • current Deferred functionality won't be enhanced e.g., https://github.com/jquery/jquery/issues/1839

jQuery Core Team Meeting – Nov 24 2014

Attending: DaveMethvin, gibson0421, markelog, m_gol

link Issues and PRs

jQuery Core Team Meeting – Nov 17 2014

Attending: gibson0421, m_gol, timmywil

link Sizzle issues:

link Issues and PRs

link Shadow DOM support

jQuery Core Team Meeting – Nov 03 2014

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

link Issues and PRs in the 3.0 milestone

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

jQuery Core Team Meeting – Oct 27 2014

Attending: timmywil, DaveMethvin, gibson042, m_gol

link Trac issues migrated

link Branch naming

  • "compat-only" and "master-only" for issues applying to just one -- done
  • rename "1.x-master" to "compat"
  • also change name in package.json - “jquery-compat”
  • Both versions need package.json rename to 3.0.0-pre
  • land PRs before renaming

link Promises/A+ compat

link $.xhr -- replaced by $.fetch

  • Should this start as a plugin? Yes

link Publish 3.0 blogpost

  • Dave to do this week

link Browser support for 3.0.0

  • Drop official support for Opera 12 and Safari 5.1
  • Keep IE9 in the master branch
  • Support Android 2.x on both (dammit)

link Additional things to reconsider as of 3.0?

  • remove deprecated stuff like andSelf
  • fractional width/height?

link Testing

  • Continue to test Opera (latest, latest-1), but on the weekly job
  • We could test Yandex browser there if it's on browserstack
  • Let's switch to private browser sets (m_gol)
    • jquery and jquery-periodic
    • jquery-compat and jquery-compat-periodic

link Issues and Pull Requests

  • Assign milestones to all issues
  • https://github.com/jquery/jquery/issues/1784
  • Shadow DOM is a pain
    • Is this something jQuery should try to fix?
    • code size and performance implications could be big
    • dave to get some input from Polymer or web standards groups on whether this is reasonable to do, and if so what devs (and jQuery) should be doing to make this work without horrible perf

link Roadmap wiki page?

  • Collect all features/enhancements for feedback

jQuery Core Team Meeting – Oct 13 2014

Attending: DaveMethvin, jaubourg, markelog, gibson042, m_gol

link Trac

link Branch naming

  • Have a "compat-only" and "master-only" for issues applying to just one
  • rename "1.x-master" to "compat"
  • land PRs before renaming

link Promises/A+ compat

link $.xhr

link version 3.0

  • dmethvin making blog post, to be done this week for review

link Testing

  • Continue to test Opera, but on the weekly job
  • We could test Yandex browser there if it's on browserstack
  • Let's switch to private browser sets (m_gol)
    • jquery and jquery-weekly
    • jquery-compat and jquery-compat-weekly

jQuery Core Team Meeting – Oct 06 2014

Attending: DaveMethvin, markelog, m_gol

link Trac

link Promise Error telemetry

  • mikesherov will talk to Domenic

link Promises/A+ compat

link $.xhr

link versioning proposals (see last week for deeper discussion)

  • version- and API-synchronized
  • jquery 1.11.1 → jquery-compat 3.0.0
  • jquery 2.1.1 → jquery 3.0.0
  • methods & properties existing in both packages have identical signatures & structure for a given version
  • public API MUST NOT exist only in jquery-compat distribution
  • public API MAY exist only in jquery distribution
  • files on cdn are jquery-3.0.0.js and jquery-compat-3.0.0.js etc.
  • RESOLVED: we use the same version number for both branches
  • dmethvin to make a blog post

jQuery Core Team Meeting – Sep 29 2014

Attending: DaveMethvin, timmywil, jaubourg, gibson042

link Update on web site attacks

link Trac

  • Let's switch to Github issues
  • Infra team swamped with DDoS and hack attacks
  • Keeping Trac for old issues reference
    • turn off new account creation and anonymous add/comment (dave)
  • Trac 1.0 upgrade will happen when it happens
  • Migrate open issues to GH issues?
    • no, just close them via the current GH hook
  • Create new issues with GH issues
    • turn on gh issues (dave)
    • create tags/milestones

link Promise Error telemetry

  • mikesherov will talk to Domenic

link Promises/A+ compat

  • needs review
  • should this deliver to the .then? It doesn't currently because the .done throws
    • Deferred().done(f1).then(f2)
  • gibson042 proposing a change for that

link $.xhr