At the beginning of the past few releases or so, we’ve put a call out for community priority tickets. There are over 3000 tickets in Trac. If there’s a ticket you feel is neglected or should have light shined upon it: leave a comment here with a link so we can triage it. Help us help you.
Updates from January, 2015 Toggle Comment Threads | Keyboard Shortcuts
It’s time for another run-down of what’s going on in WordPress core. This edition covers January 17th, 2015  through January 25th, 2015 . If you’re interested in helping out with these updates, comment below, or ping me on Slack as @mike! Without further ado:
- Menus: Improve accessibility of nav menu locations form.  #31090
- TinyMCE: Correct vertical positioning of the image toolbar when there are several instances of the editor.  #31028
get_terms(), check hierarchy for all
$taxonomiesbefore bailing early from
child_of.  #31118
- Introduce ‘childless’ parameter to
get_terms().  #29839
- Add classes for custom taxonomy terms in
get_post_class().  #16223
- Introduce ‘parent’ parameter to
wp_get_object_terms().  #15675
- Better loop detection for
_pad_term_counts().  #20635
wp_get_object_terms(). Adds support for ordering by ‘taxonomy’, ‘term_taxonomy_id’, and ‘parent’.  #28688
- Twenty Eleven and Twelve: Fill in support for
screen-reader-textclass.  #31095
- Twenty Eleven, Twelve, Thirteen, & Fourteen: Escaping and minor code style issues.        #29127
- Hide the reorder-widgets button when a widget area is empty.  #27787
- If there’s only one available sidebar, hide the move-widget button.  #30690
- Replicate behavior from
options-reading.phpand hide front page options if there are no pages.  #27630
- Display correct title in Archives widget if the type of archive was changed using the
widget_archives_dropdown_argsfilter.  #31024
- Options: Allow
add_option()to receive false.  #31119
- Users: In
wp_update_user(), make sure
$userdataIDis set before using it.  #31097
- Comments: When a comment fails to insert, remove any invalid characters and try again.   #21212
WP_Date_Querydate validation should not fail for
hour = 0.  #31067
Thanks to @afercia, @ashfame, @azaozz, @avryl, @boonebgorges, @cais, @celloexpressions, @ChriCo, @Clorith, @dlh, @DrewAPicture, @enej, @floriansimeth, @horike, @joostdekeijzer, @jorbin, @lancewillett, @mikeschinkel, @miqrogroove, @morganestes, @nacin, @nathan_dawson, @obenland, @ocean90, @pento, @SergeyBiryukov, @sillybean, @stevenkword, @theMikeD, and @tyxla for their contributions this week!
- @drewapicture is the 4.2 release lead.
- @wonderboymusic will be feature lead for a lot of media/image stuff.
- 4.1.1 will drop within a week.
- All 4.1 guest committers are renewed for 4.2.
- The tentative target release date for 4.2 is April 8th.
- Wednesday meetings will continue as usual.
- Weekly Friday bug scrubs start next week.
- This Week in Core posts will resume.
- The 4.2 feature plugins are, tentatively: Press This, Customizer Theme Switcher, and Shiny Updates. Customizer Menus is a possible long shot.
- The general focus of 4.2 will be polishing existing UIs in terms of mobile and accessibility.
- @nacin will post about guest commit renewal on make/core.
- @drewapicture will post weekly bug scrub times on make/core.
- @dh-shredder will start This Week in Core posts while permanent contributors are located.
- @johnbillion will add a page to the core handbook on development processes for mobile.
- @pento will post about contributing to Shiny Updates on make/core.
- All feature plugins will post an update to make/core.
- Component maintainers will make a list of the main issues affecting their components.
- @johnbillion will post a call for component maintainers on make/core.
We’re continuing multisite office hours in the new year on Tuesdays at 20:00 UTC in the #core-multisite room. This is a wrap-up of today’s discussion with some goals we have in mind.
Major takeaways today:
- Rapid iteration on new and existing ideas can sometimes be done best as a featured plugin. It would be nice to find some areas of multisite that could be addressed this way and start working for a release in 4.3 or 4.4. It is likely too late to include any new feature plugins in the 4.2 cycle and that’s ok.
- A good sit is needed with @nacin’s multisite roadmap from late 2013. We should revisit this, see what progress has been made, and compare with the world today. As @sam mentioned, it would be nice to see an updated version that references the previous version.
- Some workflow study is in order. We talked a bit about the painful workflows for multisite management in closed and open networks. Taking a good look at the pain points in current flows for new users, sites, plugins, themes, etc… would be good to get a grasp on priority. Looking at how WordPress.org is organized could provide a good model for a closed network.
- With of the above combined (and more!), some actual prioritized goals for multisite would be nice. Bug fixes can continue to be addressed as they come in, but without established long term goals we’re “floating aimlessly” (props @earnjam) each cycle with our wish lists.
So. The next week is for thinking, commenting, and collaborating. If anything above sounds interesting or inspires you a bunch, please leave a comment so we can start organizing around things.
Also – we now have a #core-multisite channel in Slack, so hop in there any time with ideas or questions.
Thanks all for the lively discussion today!
Drop a comment here if there’s anything specific to RC1 that you think needs discussing.
- About page text will land tonight (Wednesday the 10th).
- Moving API docs into the plugin and theme handbooks will be discussed at the next docs meeting.
- A heads up email to plugin devs will go out after RC.
- RC will go out tonight.
- @nacin will alert hosts and one-click installers in advance release.
- 4.1 final targeted for Tuesday.
- Release dry-run on Monday.
- Status check-in meeting on Sunday.
- @stephdau and @nacin will enable localized results for plugins after RC.
- @nacin will work on the plugin developer email.
- @melchoyce @ryelle @helen @jorbin will work on the about page. First draft design due by Friday.
- @nacin @markjaquith will make the final decision on Focus, Distraction Free Writing naming, branding, text.
- @nacin will alert hosts and one-click installers in advance of release.
4.1 was originally due for release today, but a few tickets in the 4.1 milestone have held things up a little. The release candidate will be tagged in time for today’s dev meeting at December 10 2014 21:00 UTC, and the target release date is now
Monday, December 15thTuesday December 16th.
Here’s the agenda for today’s dev meeting:
- Documentation from various make/core posts need to go into the plugin handbook and theme handbook.
- The 4.1 page on the Codex is in progress.
- Eyes on the support forums – the alpha/beta forum has seen almost no activity so we need eyes on the forums as a whole.
- ‘About’ page design – @melchoyce, kelly, @helen #30435
- Plugin developers – update your plugin’s readme files to indicate support for 4.1 once RC1 is released. You’ve tested all your plugins with the beta, yeah?
- Looking for something to do? Tickets reported against trunk needs some continued triaging.
- Status of plugin directory l10n and recommended plugins tab. @stephdau @tellyworth
- Discuss status of l10ns for polyglots.
- Discuss a status update meeting type thing on Sunday.
- Discuss release plan. @nacin
- Any other business.
- Focus rolled out to wordpress.com.
- Beta 3
- Recommended plugins will move to a new tab in the plugin installer. The popular plugins tab will remain.
- Strings will be released to translators on Wed. the 3rd.
- RC1 possibly on the 3rd. Possibly not.
- @tellyworth will move recommended plugins to a new tab.
- @johnbillion will work on about page text, clearing the 4.1 milestone, and triaging tickets reported against trunk.
- @nacin will release strings.
- @johnbillion will tag RC1.
- Beta 3
- Beta 2 (soft-released)
- Term splitting will be pulled from 4.1 and considered for inclusion at the beginning of the 4.2 cycle.
- Focus will default to off.
- The particulars of Focus UX will be documented.
- RC1 will be Monday the 1st.
- The final beta will be on the 27th or 28th.
- Focus will roll out to wordpress.com for testing.
- String freeze on Wednesday December 3rd.
- The about page will get attention this weekend in preparation for string freeze.
- @mboynes and @boone will work on a term splitting migration guide for plugin authors.
- @markjaquith and @janneke will document Focus UX.
- @stephdau and @dd32 will roll Focus out to wordpress.com.
- @markjaquith @nacin @kimparsell @helen and others will work on the about page.