jQuery Core Team Meeting – Nov 12 2012

November 12, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, gnarf, timmywil, mikesherov
Time: Noon ET

Official Agenda:

jQuery 1.8.3 – Today!

  • Last call for patches, but I’d prefer none more patched

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

  • Already sizzle issue, ticket closed

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

  • Should we allow leading whitespace in \$(” \”) detection?
  • I’m leaning NO
  • If it’s not a literal string, user should sanitize–or better, use \$.parseHTML

Create \$.select()? Could we just document the Sizzle entry point?

Mergatron status?

Speed tests

Dave will ping recent new contribs and see if they want to grab unassigned tix

Unassigned tickets

Assigned tickets review for 1.9; need volunteers for open tix

jQuery Core Team Meeting – Nov 05 2012

November 5, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, gibson042, gnarf, mikesherov, timmywil
Time: Noon ET

Official Agenda:

jQuery 1.8.3 – Back on again, animation bug

  • Next week

http://github.com/jquery/jquery-compat

Using github issues to track bugs

still rough and unfinished, patches and updates welcome

TODO

Filter out warnings for .min version

Update QUnit

Add other deprecated items or warnings

  • Note the warning for Quirks for example

Update README, CONTRIBUTING, AUTHORS

Create a tiny-plugin or one-liner repo?

  • put in our own private repos, e.g., dmethvin/jquery-arrayops

Mergatron status? middle of this week sez mikesherov

Speed tests, mikesherov to blow off the old stuff?

  • rwaldron to revive dromeo,dromeaaaaao, dave to bug

Assigned tickets review for 1.9

jQuery Core Team Meeting – Oct 29 2012

October 29, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: mikesherov, gnarf, gibson042, timmywil, petro
Time: Noon ET

Official Agenda:

jQuery 1.8.3 – Cancelled due to complexity and lack of serious bugs

Per discussion last week, jQuery 1.9 in a branch, 2.0 will be master

botio is dead, gnarf is moving to use mergatron

Deprecate \$(html, props)? (leave for now but document that it sucks)

  • whine whine whine but i like it
  • the problem is the creating of attributes mostly
  • plus the other special cases (one element etc)

Create a tiny-plugin or one-liner repo?

1.9 voting – triaged all tickets during the meeting, YAY!!

— post-meeting notes –

jQuery 1.9 tix – need to jump on these and finish

Pull queue – whittling it down, about 14 left now

Speed tests, mikesherov to blow off the old stuff?

Assigned tickets

jQuery Core Team Meeting – Oct 22 2012

October 22, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: mikesherov, gibson042, gnarf, saiwong, timmywil (45 min late!)
Time: Noon ET

Official Agenda:

Commit privs for mikesherov & gibson042!

jQuery 1.8.3 – Wednesday?

  • based off pre-Summit commit
  • last call for must-have patches

Aftermath of Summit

Common standard for landing patches?

  • Check for new author, ask to sign CLA, add to AUTHORS.txt
  • rebase (possibly -i) on branch, then merge to master?
  • Message: “Fix #12345, short description of the ticket. Close gh-123.”

Authors file

Promise/J – diff between our implementation and Promise/A

  • Make .then() Promise/A compliant but leave the rest as-is?
  • Need a thorough article on Promise semantics

New speed tests?

  • Blow away the junk currently in /speed, based on Slickspeed (2008)
  • New tests based on Timmy’s stuff

jQuery 1.9 changes (start of the 1.9 upgrade guide)

1.9 voting – VOTE – next week we will discuss voted tix

Assigned tickets

jQuery Core Team Meeting – Oct 08 2012

October 8, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending:
Time: Noon ET

Official Agenda:

jQuery 1.8.3 this week

essential bug fixes before the 1.9 branching

Candidate tickets, if fixable without high risk of other regressions:

Aiming for Thursday

jQuery Developer Summit

Need to contact attendees at your table this week

  • introduction and assessment (determine skill level)
  • make sure they have prerequisites set up
  • tee up some ideas from below based on their skills

Code ideas

  • move the 1.9 deprecated functions to the compat plugin
  • Ditch the makefile
  • Dave to review open tix for other candidates and add to Summit wiki
  • Team can also handle assigned tickets
  • Add infra todo to fix trac and new-ticket page?

Ticket votes for 1.9 (and 2.0, really)

Assigned tickets

jQuery Core Team Meeting – Sep 24 2012

September 24, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, timmywil, gibson042, rwaldron, jaubourg (10 minutes)
Time: Noon ET

Official Agenda:

jQuery 1.8.2 shipped — bugs?

Landing common fixes before 1.9/2.0 split

  • Should we tag those 1.8.3? (leave it as pre for now)
  • Please ID those by next Monday (Oct 1)
  • Let’s complete bug fixes before summit (Oct 15)

The split(s) schedule

1.9 split to occur post-Summit (Oct 22)

  • master branch will be 1.9

Remove deprecated features and stabilize

Complete the compat plugin

naming? I don’t like jquery-compat-1.9

  • jquery-compat.js

warns about using the features, patches support back in

1.9 alpha/beta first, incorporate feedback

2.0 split early December?

  • master will stay 1.9 … branch will be 2.0

Ticket votes for 1.9 (and 2.0, really)

SVG support

  • Would like a deeper analysis before official support
  • Okay with landing simple SVG fixes
  • yet another one: http://jsfiddle.net/qqvzM/3/ (via peol)

Trac problems

Assigned tickets

jQuery Core Team Meeting – Sep 17 2012

September 17, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, timmywil, rwaldron, gibson042, mikesherov
Time: Noon ET

Official Agenda:

jQuery 1.8.2

Would like this to be the last in the 1.8 line

Let’s stay conservative

  • No regressions
  • Only low-risk, high-impact bugs

Blockers

  • The Big Sizzle
  • Others??

Ship date: Thu Sept 20?

Bug triage meeting last Thursday

  • Triaged all new bugs
  • Triaged 1.8.2 bugs

Assigned tickets

Let’s only grab tix when they can be worked on soon

  • Weekly status on assigned tickets
  • Owned tix discourage others from looking/fixing
  • Can we get some of these done during the hackfest?

Currently assigned

1.9/2.0 split

  • land any post-1.8.2 fixes common to both
  • Do the split after that, post-hackathon

1.9 direction on oldIE

  • Fix anything that’s practical (a dozen or so lines of code max?)
  • Wontfix the rest; explain why (perf, size, side-effects) and give workarounds

1.9 voting

  • Let’s start voting next week (after 1.8.2 ships)
  • Identify tickets that you think should be discussed/voted
  • Don’t tag uncontroversial tickets that should just be done

jQuery Core Team Meeting – Sep 10 2012

September 10, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, mikesherov, gnarf, timmywil, gibson042, rwaldron
Time: Noon ET

Official Agenda:

jQuery 1.8.2

Would like this to be the last in the 1.8 line

Let’s be VERY conservative about fixes

Blockers

https://github.com/jquery/sizzle/pull/151 from gibson

  • needed for regressions

Performance suite for jQuery core

We have a new suite for Sizzle http://cl.ly/image/0C2V351c3y1a

rwaldron will take the lead on Dromaeo adaptation

  • /jquery/dromaeo repo created (thanks scott_gonzalez)

jQuery 1.9/2.0

Fix common 1.9/2.0 problems early

  • Removals from deprecations
  • Bug fixes

Branch 1.9 when common work is complete

2.0 work to be done in master

All open tickets should be in play

Let’s do a ticket triage day before the Summit

  • Thursday 9/10 7:30pm (invites sent)
  • Decide which tix should be addressed before branch

Do we need a public call for features? (no)

  • Last one didn’t come up with useful feedback
  • Not looking to add features this time around

Aim for 1.9 beta in early December

  • Long beta period since we’re removing a lot

Aim for 2.0 beta … when? (1.9 beta +2 wks?)

jQuery Core Team Meeting – Aug 27 2012

August 27, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, timmywil, gibson042,
Time: Noon ET

Official Agenda:

jQuery 1.8.1

Final or RC? Leaning towards final.

Release day? Wednesday, Thursday?

Things to emphasize in the 1.8.1 release blog post

  • Dropped FF 3.6 support, tho Sizzle still has it

No ticket but broken

  • Wilto checked the Android 2.1 issue with .ready(), still there

Tickets with patches

http://bugs.jquery.com/ticket/12403 (UI-related selector fail)

  • landed

http://bugs.jquery.com/ticket/12313 (be kind to SVG on width/height)

Tickets and PRs we need to land (blocker)

http://bugs.jquery.com/ticket/12392 (created elements have a parent)

http://bugs.jquery.com/ticket/12359 (XHTML again)

  • fixed

http://bugs.jquery.com/ticket/12384(regression with .after)

http://bugs.jquery.com/ticket/12369 (.find() and oldIE XML)

http://bugs.jquery.com/ticket/12346 (.append multiple stuff)

http://bugs.jquery.com/ticket/12303 (:first inside attribute values)

http://bugs.jquery.com/ticket/12337 (.nth-child selector fail)

  • marked as dup of 12205, fixed

Full list of blockers

Quick triage on new tickets

jQuery Core Team Meeting – Aug 20 2012

August 20, 2012
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Attending: DaveMethvin, gibson042, jaubourg, rwaldron, timmywil (cameo by phone)
Time: Noon ET

Official Agenda:

jQuery 1.8.1

RC or final? (depends on tix that land by then)

This week: Thursday?

Tickets and PRs we need to land (mark as blocker)

  • sizzle fixes (timmywil and/or gibson042)

jQuery 1.9 & 2.0

Mark your faves as “1.9-discuss” or “2.0-discuss” in the tracker

Intentionally avoiding major rewrites in 1.9 — mostly just deletes

Intend to release 1.9 and 2.0 very close to each other

Aim for alpha after our hackfest in October?

How can we avoid the 1.9.0 bug rush?

How can we involve the community?

  • Running blog posts about changes
  • More alpha/beta releases?