A Release Candidate for WordPress 4.6.1 is now available. This maintenance release fixes 16 issues reported against 4.6 and is scheduled for final release on Wednesday, September 7.
Thus far WordPress 4.6 has been downloaded almost 7 million times since its release on August 16. Please help us by testing this release candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). to ensure 4.6.1 fixes the reported issues and doesn’t introduce any new ones.
Here’s a list of all closed tickets, sorted by component:
- #37680 – PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher Warning:
ini_get_all() has been disabled for security reasons
- #37696 –
sql_clauses with object cache
- #37683 –
$charset can be undefined in
- #37689 – Issues with utf8mb4 collation and the 4.6 update
- #37690 – Backspace causes jumping
- #37736 – Emails fail on certain server setups
- #37700 – Warning:
curl_exec() has been disabled for security reasons (Requests library)
- #37720 – The minified version of the Masonry shim was not updated in #37666 (Masonry library)
HTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. API 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.
- #37733 –
cURL error 3: malformed for remote requests
- #37768 – HTTP API no longer accepts integer and float values for the cookies argument
- #37697 – Strange behavior with thumbnails on preview in 4.6
- #37800 – Close “link rel” dns-prefetch tag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)
Taxonomy 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.
- #37721 – Improve error handling of
- #37755 – Visual Editor: Weird unicode (Vietnamese) characters display on WordPress 4.6
- #37731 – Infinite loop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. in
_wp_json_sanity_check() during plugin 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 install
This post summarizes the dev chat meeting from August 24th (agenda, Slack archive).
- Bug scrub on August 30 at 15:00 UTC. (all patches should ideally be in trunk 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.)
- Release candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). on September 1 (all patches are in 4.6 branch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".)
- Release on September 7
4.7 Personnel and Schedule
- @jorbin (engineering/development focus) & @jbpaul17 (PM focus) will be release deputies for 4.7
- Full release schedule can be found at https://make.wordpress.org/core/version-4-6-project-schedule/
- The scheduled release date is December 6.
- Due to WCUS & US Thanksgiving holiday, we will have to treat RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). as a true Release Candidate
- There is no “merge window”, testing & feedback should be continuous before merge consideration
Potential Focus Areas
- Many wishlist comments are specific developer-facing features as well as better media findability/organization, easier plugin 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 management, and the initial theme setup experience
- New default theme (aka Twenty Seventeen) likely, but to be confirmed within the next week or two
- REST 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/. content endpoints (posts, terms, comment, users, and their associated meta 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.) to get defined roadmap for 4.7 delivery plus future roadmap to full management and admin (and super admin) API 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. coverage (potential approach)
- the next meeting will be August 29 at 23:00 UTC, where this will be further discussed
- @krogsgard aiming to write spec for each item in the list by next meeting, open to acting as PM for this focus area
- looking for a few committers with knowledge around the API to guide the process with a permanent or lead as their buddy
- looking for review from outside WP community
- will require documentation coverage for builders and consumers
- Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. endpoints will need to be reviewed by their respective component maintainers
Open Forum on Focus Areas
- “find your media more effectively” (#22744)
- taxonomy 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. (aka media tagging) UX User experience+UI User interface work for assignment and filtering mechanisms
- “find an accessible multi-select/autocomplete/tagging helper”
- “smarter defaults”
- Eliminating usability dead-ends in the customizer 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. (#34923, #35395, #37661)
- further refinements to the updates flow continuing from 4.6
- low-fi mockup and testing of metabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. for different publishing possibilities (including existing examples)
- resolve some ancient annoying issues (e.g., #17817)
- Content Authorship in Menus, with Live Preview
- dashicons as svg sprite (Make/Core Post)
- document dynamic hook aliases in core (finally) + adding DevHub support
- initial theme setup experience
Teams and Weekly Updates
- Teams are the contributor groups that form around components and major work items (e.g. features and big API changes)
- Will continue to identify those Teams and a “spokesperson” for each
- Teams should have a weekly scheduled meeting and a weekly update posted to Make/Core
- @helen to continue the tradition of weekly jump start posts, so there will be a reminder of Team meetings each week
- Everyone is empowered to run a bug 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. scrub (can be component based, or based on any other ticket Created for both bug reports and feature development on the bug tracker. report)
- A post with information on how to run a bug scrub and who is empowered to do it (hint: it’s you) will be published on make/core soon
- Bug Scrubs are a great experience in running a meeting, writing good responses, and building confidence in making those do-or-punt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) decisions
- You do not need to be a dev to run a bug scrub, @hugobaeta and the design team has done some great scrubs
- You don’t need to be a committer A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. to run them, @chriscct7 has done some incredible scrubs on ancient tickets
- “If 5 new people that have never run a bug scrub or other core meeting before, run one this release: I will write and record a parody of “No Scrubs” by TLC, but about Bug Scrubs.” — @jorbin Π
The first bug 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. scrub for 4.6.1 will be Tuesday 23 August, 15:00 UTC in #core.
There are currently
9 11 tickets open on the 4.6.1 milestone in various stages of verification, patching, and testing. Working with these over the next several days before the bug scrub will help determine when a 4.6.1 release will be necessary.
Any tickets reported against trunk at this point in the cycle should also be checked for issues that may have been introduced in 4.6.
All testing is helpful, so please take a look if you have time.
See you on Tuesday!