jQuery Mobile Team Meeting – Dec 18 2014

  • Ticket Triage:
    • 262 tickets +0
    • 34 pull requests +0

link 1.5.0

jQuery UI Team Meeting – Dec 17 2014

Chassis Team Meeting – Dec 16 2014

  • Naming convention #4
    • Phone call with Yandex regarding BEM happened this morning
    • BEM seems to be the prefered naming convention
  • Performance Testing #2
    • No news on this at this time
    • Decided to start working on our own solution
  • Domain Names
    • We need to buy domain names
    • kborchers to buy the domain name css-chassis.com
  • Documentation
    • Should we use jquery-wp-content? Don't inherit from base theme to be able to use self-hose?

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 Mobile Team Meeting – Dec 11 2014

  • Ticket Triage:
    • 262 tickets +1
    • 34 pull requests -2

link 1.5.0

  • all updates from ui pulled in
    • tests need fixing started by gabriel, cgack taking over
  • Classes
    • Decided new api and some other changes this morning
  • CSS update (button, checkboxradio, controlgroup)

link Other topics

Project Leads Meeting – Dec 10 2014

Attending: Dave, Scott, Sarah, Alex, Rafael

link Core

  • Patch release of 1.11.2/2.1.2 coming next week with blog post
    • Primary thing is a patch to a Safari selector bug
    • A few very minor bug fixes otherwise
  • Meantime, 3.0 changes being landed in master
    • Another Safari bug bit us there with createHTMLDocument
  • Already updated to QUnit 1.16
  • Targeting release in mid-January with beta beforehand

link UI

  • Dropping support for jQuery 1.6
  • Effects rewrite ready to land

link Mobile

  • Focusing on work not involving ui classes
    • mostly patches and minor stuff

link Globalize

  • Currency formatting implemented \o/.
  • Going to implement currency parser (to allow spinner demos to use new Globalize).
  • Adobe is evaluating Globalize to be used in their client-side applications.
  • Waiting for license approval to use slexaxton/messageformat.js.

link Chassis

  • Name is "Chassis"
  • Using SVG for sure
  • Normalized CSS with some adjustments for box sizing
  • Supporting IE8+
  • Talking with Yandex team

link QUnit

  • QUnit 1.16 came out, YAY

link Testing

  • Recurring problems with Browserstack and outdated Java on IE, m_gol has contacted them several times

link Infrastructure

  • AdamU is working on log rotation as a temporary solution to the full drive issues, root cause is DDoS traffic and long term solution is to get behind firewall
  • All sites updated to Grunt 0.4

Chassis Team Meeting – Dec 09 2014

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