Garth Mortensen 10:51 pm on April 27, 2016
Tags: , 4.5.2, , ,   

Dev Chat Summary – April 27, 2016

This post summarizes the dev chat meeting from April 27.

4.5.1 / 4.5.2

  • Released April 26, 2016.
  • Exact time of release wasn’t announced, which left places like #forums on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. 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 releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. 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 pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins./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 pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party are ready for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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 APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. team would like to propose their changes to register_meta() and a datalayer for metadata REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/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 CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.) and #30937 (Add Customizer transactions). Anyone who has questions or is looking to contribute should join #core-customize on Slack.

Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. 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 bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. 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, TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies., Themes, and Widgets.

Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site

  • 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.

Editor

  • @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. 🙂

i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

  • 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.

Customizer

  • The Customizer Transactions patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. got a refresh for trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision..

Comments

  • Bug scrub time will be announced next week.

a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)

  • 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/

RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.

  • @adamsilverstein is working dilligently on resolving tickets including #20564 (Framework for storing revisions of Post MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.), #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/

Open Discussion

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

#4-5-1, #4-5-2, #4-6, #dev-chat, #summary