jQuery Core Team Meeting – Apr 03 2012

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

Official Agenda:

1.7.2

New issues?

Bad TinyMCE .attr() duck punch seems to be resolved by their beta

Bug tracker misbehavin’ again last week

  • Who knows why, but a reboot fixed it…

Style guide: Did we remove the ambiguous “space around quotes” rule?

  • Dave to create epic email thread regarding this

http://bugs.jquery.com/ticket/11539 Do we want to change our support for text nodes?

  • gibson042: traversing is safe for text nodes, manipulation is not?

Triage

1.8 (April 9 Beta)

Dev on master or branch? Consensus: 1.8 on Development Branch

1.8 Feature branch — we’ll land PRs there?

Specific process?

  • Make standard PRs but against 1.8 branch (after I create it)
  • https://github.com/jquery/jquery/branches
  • Um, create 1.8 branch (BRANCH is 1.8pre b/c there was 1.8 subs?)
  • WHY CAN’T I label PRs? (gnarf: maybe bc issues are off?)

Several PRs ready to land

jaubourg has been a good boy

Pinged Chad Killingsworth re Closure Compiler, he made a Sizzle PR for some issues to simplify CC work (haven’t reviewed it yet)

jQuery Core Team Meeting – Dec 13 2011

December 12, 2011
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Time: Noon ET

Official Agenda:

  • Open bugs — jQuery 1.7.2? http://goo.gl/jYbsc
  • 1.8 voting in tracker — http://goo.gl/sy3Ax

    • Suggestions boiled from list (see link from last week)
    • Team voting on 1.8 suggestions this week; Team vote here: http://goo.gl/lhKlz
    • Don’t add bugs to here unless you need to discuss them by vote
    • Landing contingent on final code review (size especially)
  • Public link to suggestions spreadsheet (sans emails): http://goo.gl/9Ss0K

  • Closure Compiler status — Chad working on string-defined methods

jQuery Core Team Meeting – Nov 14 2011

November 14, 2011
Minutes (Notes) of the meeting of jQuery
Location: #jquery-meeting on Freenode
Time: Noon ET

Official Agenda:

  • jQuery 1.7.1 Issues

  • Pull request process

    • Help is welcome but some PRs are more work than their value
    • How should we approach those? Leaving in the queue means they go stale
    • Ask ppl to engage us before making a PR?
    • Review current open PRs: https://github.com/jquery/jquery/pulls
  • Deprecation blog post feedback (Dave)

    • Followup blog post to address suggestions in blog comments

      • “Remove all IE support!”
      • “Break it into tiny little parts and have a download builder!”
      • “Wait until 2.0 to remove stuff”
      • “Make effects and/or ajax optional”
    • Need a a review to ensure we have marked deprecated in API docs (Dave)

jQuery Core Team Meeting – Nov 01 2011

October 31, Noon ET

jQuery Core Team Meeting – Jun 28 2011

Minutes (Notes) of the meeting of jQuery

Location: #jquery-meeting on Freenode

Time: Noon ET

Official Agenda:

jQuery 1.6.2 status

  • Get the release out today or tomorrow.

Bug Triage Day: July 11th and 12th

  • Holding vote now for travel budget approval.

jQuery Core Team Meeting – Jun 21 2011

Minutes (Notes) of the meeting of jQuery

Location: #jquery-meeting on Freenode

Time: Noon ET

Official Agenda:

jQuery 1.6.2 status

  • RC1 has had some bug closed and \$.browser.chrome ready to pull, should we do an RC2?
  • DaveMethvin: it seems like 1.6.2 may be in good shape then? other than a peaceful queasy feeling?
  • Seems to be a no on RC2, pending John and Timmy’s input

Bug Triage Day: July 11th and 12th – Same day as ARIA Hackathon ( http://wiki.jqueryui.com/ARIA-Hackathon ), but no real overlap of people. Could be useful to know UI team is at least available for questions.

  • July 11th – all day
  • July 12th – till 2:30pm
  • Project to vote on airfare for Timmy -> BOS

jQuery Core Team Meeting – Jun 13 2011

Minutes (Notes) of the meeting of jQuery

Location: #jquery-meeting on Freenode

Time: Noon ET

Official Agenda:

jQuery 1.6.2 Status

  • We're getting the RC out today.

Talked with Closure Compiler team, they’re fixing bugs, should be good for the team

We’re working on dates for an upcoming bug triage day, possibly late June

Firefox version support moving forward

  • Mozilla has dropped support for 3.0 and 3.5, makes sense for us to do the same

jQuery Core Team Meeting – Jun 06 2011

Minutes (Notes) of the meeting of jQuery

Location: #jquery-meeting on Freenode

Time: Noon ET

Official Agenda:

Collaboration with Google Closure Compiler

  • Chad Killinsworth (non-Google contributor) and Alan Leung (at Google) to join today’s meeting
  • goal:
    demonstrate mutual interest, thereby making better support of jQuery in
    advanced mode a priority for the Closure Compiler team

jQuery 1.6.2 Status

  • Keep on keepin’ on.

jQuery 1.7 Roadmap

http://bugs.jquery.com/report/501

Voting Results:

jQuery Core Team Meeting – Jun 03 2011

No updates from the core team this week – meeting wasn't held due to conflict with Memorial Day in the US. Work is continuing on 1.6.2 and votes are still being tallied for the 1.7 roadmap meeting.

jQuery Core Team Meeting – May 23 2011

Minutes (Notes) of the meeting of jQuery

Location: #jquery-meeting on Freenode

Time: Noon ET

Official Agenda:

jQuery 1.6.2 Status

http://bugs.jquery.com/query?status=!closed&milestone=\^1.6.2&order=priority

Blockers

No major rush, just keep fixing bugs. We’ll set a date soon (likely in a month or so)

jQuery 1.7 Roadmap

http://bugs.jquery.com/report/501

Voting on Bugs:

  • The
    point of voting on the blockers is that they're, previously nominated
    by just one person as being a blocker – we use this opportunity to
    determine if it should remain a blocker (and be fixed) or if not, get
    bumped down to a lower priority.

Voting on Features:

  • In the case of feature/enhancement requests – either land it or close the bug as wontfix

Form is now closed

Team members should have permission to vote, please let John know if you don’t have access, for some reason.

Voting should be done by June 6th

  • Roadmap Meeting on June 6th

Final Release: September 30th

Beta 1: September 1st

Alpha 1: August 1st

September will be dedicated towards Q&A

August will be dedicated towards docs writing