4.5.1 / 4.5.2
- Released April 26, 2016.
- Exact time of release wasn’t announced, which left places like #forums on Slack and hosts in the dark. Going forward an exact timeframe should be announced, the handbook will be updated to be more clear on this requirement.
- Two proposals about minor release leads came forth. One being that a set of “maintainers” be established to be on top of minor releases, the other being @ocean90 and @voldemortensen do 4.5.2 as a dry-run for 4.6.0. No decision has been made at this time.
Status of the wish-list post
There are currently 124 tickets, 4 of which are complete with about 15 in progress.
Feature plugin/project proposals for 4.6
- Contributors to the proposed projects should attend the feature plugins/projects meetings. The next one will be held on May 3, 2016 15:00 UTC.
- Parts of the Shiny Updates v2 plugin are ready for core and have been proposed for merge. This fits in with the goals of the 4.6 release cycle.
- Any one who would like to try the Shiny Updates plugin can find it here: https://wordpress.org/plugins/shiny-updates/
- The Fields API team would like to propose their changes to register_meta() and a datalayer for metadata REST API endpoints.
- @helen is looking at #32678 (Audit toolbar links and content) for items that can be brought into 4.6.0. No meetings are currently being held, but times are being considered.
- @westonruter proposed #34923 (Introduce basic content authorship in the Customizer) and #30937 (Add Customizer transactions). Anyone who has questions or is looking to contribute should join #core-customize on Slack.
Triage of tickets with the “early” keyword
- There are currently 12 tickets which are marked as early. Let’s try to get this report empty by next week. : https://core.trac.wordpress.org/query?status=!closed&keywords=~early&milestone=4.6
Component Maintainer Updates/Reminders
- Please post notes from weekly meetings and bug scrubs on make/core. Release leads will try get weekly posts on upcoming meetings.
- Weekly meeting times can be found here: https://make.wordpress.org/meetings/
- Components which should definitely have a bug scrub soon: Posts, Post Types; Comments, Taxonomy, Themes, and Widgets.
- Had a kick-off meeting last Thursday and published notes: https://make.wordpress.org/core/2016/04/25/multisite-kickoff-for-4-6-chat-summary/
- Had the first weekly chat of the cycle yesterday…and published notes: https://make.wordpress.org/core/2016/04/27/multisite-office-hours-recap-april-26-2016/
- Great progress has been made on `WP_Site_Query`, check it out. #35791
- If you use multisite for anything, also checkout (and test) #34941.
- A casual bug scrub will happen on April 28, 2016 at 20:00 UTC in #core-multisite.
- Weekly office hours are Tuesdays at 16:00 UTC.
- @iseulde has started working on using the TinyMCE APIs for wpView and inline toolbars
- @azaozz is still chasing after couple of rare editor bugs and will start on the wishlist (https://make.wordpress.org/core/2016/04/12/editor-wish-list-4-6/) probably by the end of the week.
- If somebody have questions or like to get involved/help, please join us at the regular editor chats on Wednesday two hours before this chat in #core-editor
Pings and Trackbacks
- @dshanske is a new maintainer. He closed/consolidated several tickets however reading the code caused him to open some more. 🙂
- First bug scrub was this Tuesday, next scrub is May 3, 2016 at 18:00 UTC.
- The roadmap for 4.6: https://make.wordpress.org/core/2016/04/22/i18n-kickoff-for-4-6-chat-summary/
- Meetings happen in #core-i18n.
- The Customizer Transactions patch got a refresh for trunk.
- Bug scrub time will be announced next week.
- Just a reminder that any new feature landing in core (see feature projects/plugins) should be in line with the accessibility coding standards found here: https://make.wordpress.org/core/handbook/best-practices/coding-standards/accessibility-coding-standards/
- @adamsilverstein is working dilligently on resolving tickets including #20564 (Framework for storing revisions of Post Meta), #27244 (Restore This Autosave’ immediately updates a published post), #30679 (Clicking “Restore this Revision” publishes immediately) and #20299 (Preview changes on a published post makes all post meta “live”).
- Work on #20564 is mainly happening on https://github.com/adamsilverstein/wp-post-meta-revisions and can be tested here https://wordpress.org/plugins/wp-post-meta-revisions/
The REST API team is seeking direction and clarity on the path forward. A more in depth summary will be posted separately. Read the conversation here: https://wordpress.slack.com/archives/core/p1461791901002328
@tfrommen would really love to see (more) feedback on #36335, especially by (but of course not restricted to) Core Committers. Both targeted at the ticket’s core (i.e., a central autoloader) and the parts directly related to WordPress (e.g., split up files with multiple classes, or classes and functions, etc.). Things that might be tackled in the scope of WordPress 4.6, or in general, some day/release. https://wordpress.slack.com/archives/core/p1461795636002501
The full dev chat logs can be found here: https://wordpress.slack.com/archives/core/p1461787203002129