The dev chat is normally two hours later, at 2100 UTC. I won’t be available, and will leave that to @markjaquith and co. I expect it will be a light meeting again. 3.5.1 timing should be discussed, which should be easier with the triage session happening earlier.

• Congratulations on WordPress 3.5, everyone.
• Fallout of 3.5. How’s the support forums? Any common issues? What can we learn from plugins that broke?
• Can we help with any common issues? Can documentation (like field guide posts) help?
• Triage 3.5.1 tickets. What does our timeline currently look like?
• Discuss plans for the month of December, and 3.6.
• Stare at the download counter.

Thank you so much for a great release. Really proud of what we accomplished. — @nacin, @koop

Final decisions need to be reached on:

• The functionality of the browser uploader and media-new.php — #22604
• IE7 and media — #22609

Status reports needed on:

• Early returns for RC2 and the merge to WP.com (both which should be out before tomorrow)
• Status of remaining tickets
• How are the support forums doing? We need to continue to closely monitor http://wordpress.org/support/forum/alphabeta.

Things to do:

• Get people to write posts for a field guide

• Triage http://core.trac.wordpress.org/report/5. No ticket should be without an owner, a path forward, and a timeline.
• Discuss timeline for RC1 and how we are all feeling.
• Things we need to do (or start thinking about) to prepare for a final release:
  • We need an About page of features. So, what are our wins?
  • Full sweeps for RTL, help text, IE, no JS, the blue color scheme, performance regressions, and 100% passing unit tests.
  • Continue to scan the support forums and awaiting review tickets reported against trunk to ensure we don’t miss anything.
  • Brainstorm what features and API changes need written tutorials (the “field guide”), and get people on board to research and write them.
  • Figure out what changes might need “3.5 compat” posts. The wpdb::prepare() argument change comes to mind, and obviously parts of media.

All tickets should have people responsible for them, but also, so should all of these release preparation tasks. There’s something in there for everyone — bug gardeners, documentation, research, testing, etc.

Agenda for today is to shore up http://core.trac.wordpress.org/report/6 and ready another beta to be kicked out the door.

Let’s aim to resolve/triage/punt a significant amount of report/6 in preparation for a beta.

chat.freenode.net, #wordpress-dev, 20:00 UTC

This will likely be a working meeting. Let’s push through and line things up for beta 3.

I think the goal for today is:

• Determine how 3.5 Beta 1 was received. Any major bugs? Any lingering issues we need decision points on? How do the support forums and Trac queues look?

• Determine the goals for Beta 2, dropping next week. (After that, one beta per week until we transition to RCs.) Media needs a final push, and a few things still need to land. We need to start looking at closing out tasks/projects that are in trunk but need tweaks, testing, or changes to consider them done.

Suggested reading: Countdown to 3.5 Beta 1 and Timeline for Twenty Twelve 1.0.

Updated. Agenda topics based on the comment thread:

• #21951 – Twenty Twelve – Conditionals in one template versus more templates but less logic
• #21101 – get_comments() – comment_approved versus status
• #18302 – theme_uri() with child theme inheritance
• #22002 – Plugin favorites via the plugin installer screen

An incomplete list of things that need to land before beta 1:

• Welcome screen v2
• Color picker (even if it is the initial pass; we can follow up after with @mattwiebe’s changes)
• Retina spinners (more likely people can find bugs)
• Page on front UI
• Multisite in a subdirectory