Post-3.5 IRC meeting
Here’s the agenda for the December 12 developer chat in IRC. That’d be #wordpress-dev on freenode at 21:00 UTC. Should be a fairly low-key meeting:
- 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
Paddleman, 
George Stephanis 7:09 am on December 12, 2012 Permalink
Considering the abundance of script-loader.php reports we’re getting in on the forums, we may want to reevaluate how we’re chopping and array-izing things from http://core.trac.wordpress.org/ticket/22757 — for example, http://wordpress.org/support/topic/quick-edit-not-working-after-35-update
Andrew Nacin 7:23 am on December 12, 2012 Permalink
I don’t know if this is specific to our chopping in #22757, or something else. Anecdotally, I too have seen a number of bug reports, but We need to isolate the individual issues and figure out what things exactly are causing things to break for these users.
George Stephanis 7:24 am on December 12, 2012 Permalink
Agreed. I’m hoping to accumulate some example URLs to a variety of problematic load-scripts.php instances before the meeting tomorrow, so we can sort out what varieties are cropping up.
Clifford Paulick 7:45 am on December 12, 2012 Permalink
Faster Insert broke: http://wordpress.org/support/topic/doesnt-workdisplay-on-wp-35
I setup a custom write panel that has meta boxes but no ‘editor’ so Faster Insert was a good way to still allow WP native uploads and [ gallery ], so I’m missing it. Maybe that’ll help you out.
Thanks for 3.5!
sourceforge 10:13 am on December 12, 2012 Permalink
thank you @nacin, @koop do they pay you extra for all the front end work and contributions?
Maor Chasen 10:36 am on December 12, 2012 Permalink
Well done guys! This version is definitely a solid one. Hope to see you all then and there.
nofearinc 11:34 am on December 12, 2012 Permalink
Any plans on setting some order in Trac? There are probably hundreds of tickets with patches with no end resolution, as well as other corner cases.
Some of them require simple gardening which is not a core dev job, but setting priorities to open tickets or closing open discussions that just won’t ever get to Core is a lead decision.
Amy Hendrix (sabreuse) 5:41 pm on December 12, 2012 Permalink
There’s been some talk about doing some Trac cleanup post-3.5 — bringing in new bug gardeners, cleaning up old tickets/reports/workflows, and so on. It’s definitely true that we have way too many open tickets for too long. If you’re interested in helping out with that, I’m sure it would be very welcome!
Ipstenu (Mika Epstein) 2:32 pm on December 12, 2012 Permalink
If you guys are seeing more crazy on the forums, don’t assume I saw everything! Please email the WP-forums list
Lance Willett 7:40 pm on December 12, 2012 Permalink
Would like to briefly discuss the Twenty Twelve hotfix and #22856
John Blackbourn (johnbillion) 9:08 pm on December 12, 2012 Permalink
It was briefly mentioned in #wordpress-dev a few days ago that 3.6 could be a one-feature release, concentrating on media again, possibly with a short release cycle. Discuss?
John Blackbourn (johnbillion) 9:09 pm on December 12, 2012 Permalink
Actually, it’s probably too early for 3.6 chat. Feel free to punt for now.
Paddleman 12:36 am on December 13, 2012 Permalink
OMG @ Download counter
Thanks (esp Nacin and Lance) for taking note of my bug reports from RC3 and fixing it in 3.5.
This is my first experience with WordPress upgrade and cant believe how smooth it went. Well done to everyone.
I got a wish list for 3.6. What is the procedure for communicating it?
Tom Lynch 1:43 am on December 13, 2012 Permalink
I have been doing a bit of digging and I think the Settings API and use of it in Dashboard might be worth a look, I have pulled out a number of tickets to look at:
https://core.trac.wordpress.org/query?keywords=~settings-3.6&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=milestone&order=id
Looks like the key issues are implementing Settings API in Dashboard, tweaking Settings API and allowing for priority, and removal of Settings.
From a UI perspective implementing a table less css design and reviewing the settings layout for consistency.