4.9.6 Schedule Changes

Last Thursday, 4.9.6 beta was released. In order to properly address all feedback received from betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. testers, more time is needed.

After careful discussion, @desrosj, @allendav, @azaozz, and @sergeybiryukov have decided that to prevent any further set backs, both the 4.9.6 release candidaterelease 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). and 4.9.6 release by two days each.

The new schedule moving forward is as follows:

  • Release Candidate: Thursday, May 10th
  • Release: Thursday, May 17th

As previously detailed, 4.9.6 is not a typical 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. because of the inclusion of time sensitive features. In order to give site owners the personal data and information tools needed to be prepared for GDPR (General Data Protection Regulations) before the May 25th, 2018 effective date, these features cannot be removed to ship the minor version on time.

This decision was not made lightly. Deadlines are not arbitrary. However, it is important that the tools are ready and that translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. contributors have enough time to localize the large number of new strings in the release.

Please continue to test the 4.9.6 beta package and provide feedback.

#4-9-6

WordPress 4.9.6 Beta

The beta package for 4.9.6 has been released and is now available for testing. Please help test the beta version to ensure the version works without error.

This betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. release contains 10 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. fixes and 34 enhancements/feature requests. Since the primary focus of this release was adding privacy and personal data tools in support of the European Union’s General Data Protection Regulation (GDPR), the number of enhancements and features added in this 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. is much higher than usual.

Even more than usual, we need testers to help polish this release: Shortly, version 4.9.6 will introduce the first round of tools that help WordPress site owners and admins meet the new requirements of user privacy regulations.

The release candidaterelease 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). is scheduled for Tuesday, May 8th, and the official release is scheduled for Tuesday, May 15th.

Bug Fixes

A full list of bugs fixed in 4.9.6 Beta can be found on Trac.

Login and Registration

  • #43917 – Set nocache_headers in wp-activate.php
  • #43843 – Set nocache_headers in wp-signup.php

Media

  • #42919 – Unable to upload files with the AAC extension

Query

  • #43375 – Incorrect old_slug_redirect_post_id filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. docs

Themes

  • #43374PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 7.2 Warning: count(): Parameter must be an array or an object that implements Countable in /wp-includes/theme.php on line 356

Features and Enhancements

A full list of features and enhancements in 4.9.6 beta can be found on Trac.

Administration

  • #43820 – Add “Mine” filter for attachments similarly to posts and comments

General

  • #43583 – Introduce new PHP cross-version compat function is_countable()
  • #43619 – Introduce new PHP cross-version compat function is_iterable()

Plugins

  • #43650 – Add Requires PHP Version to 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 – View Details

Posts, Post Types

  • #43739 – Include ‘viewable’ attribute on Post Type resource for ‘edit’ context

Privacy

  • #43435 – Add settings screen for creating a privacy policy
  • #43473 – Add default text for a privacy policy
  • #43620 – Privacy Policy page design
  • #43926 – Improve flow for privacy.php
  • #43935 – Limit Privacy Policy screen to Super Admins in 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
  • #43850 – Add privacy policy URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org template tags
  • #43715 – Add Privacy Policy link to bundled theme footers
  • #43721 – Adding links to imprint and privacy policy pages on WP login screens
  • #43545 – Helper functions: Anonymizing data in a standardized way
  • #43481 – Add tabs and placeholders to privacy tools page in wp-adminadmin (and super admin)
  • #43547 – Add personal data from usermeta/ userdata to personal data export
  • #43440 – Add personal data from comments to personal data export
  • #43883 – Add a user’s attachments to the personal data export file
  • #43551 – Add a means to package personal data into a file
  • #43443 – Add a method for confirmation of requests for deleting or anonymizing of personal data
  • #43637 – Add filters and ajax support for personal data erasure
  • #43911 – Add mailto into Export/Erasure tables
  • #43442 – Add tools for anonymizing of commenters
  • #43931 – Use associative array instead of numeric for exporters and erasers
  • #43436 – Add opt-in for commenter cookies
  • #43873 – Relocate ‘Privacy / Export / Erasure’ pages into more appropriate menus
  • #43894 – Rename page / menu ‘Privacy Tools’ to ‘Privacy Policy Page’
  • #43942 – Add pointers informing users of the new privacy pages

Themes

  • #43872 – Add page template filter for all post types

Users

  • #42202 – 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/.: no equivalent for `who=authors` to display potential authors

#4-9-6

Dev Chat Summary: May 2nd (4.9.6 week 5)

This post summarizes the dev chat meeting from May 2nd (agenda, Slack archive).

4.9.6 planning

  • Decision to push betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. back two days gave us enough time to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. all the things (thanks to @sergey for all the work there)
  • 25 tickets left in the milestone, aiming to get to 10 for beta, will likely puntpunt 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.) non-GDPR tickets
  • Bug scrub tomorrow will be at 15:00 UTC instead of 17:00 UTC
  • @azaozz lined up to help package up the beta in Mission Control, process to begin at 20:00 UTC
  • Heavy discussion on where to introduce new menu items as part of #43873, four options outlined:
    • 1) All three under the Tools menu (currently how it is in 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.).
    • 2) The settings page under the Settings menu labeled Privacy, and the tools under Tools
    • 3) A new top level menu item for Privacy.
    • 4) Listing the erasure and export tools under Users, and the settings page under Settings.
  • Summary of decision:
    • Export and erase tools remain under tools
    • A settings page for Privacy Notice is added to the bottom of the Settings menu.
    • @melchoyce to follow up with feedback on that settings page.
    • @desrosj to create a ticketticket Created for both bug reports and feature development on the bug tracker. for the pointers needed for this work
  • Reminder that after beta ships tomorrow, RC will be up next on Tuesday, May 8th (see: 4.9.6 schedule)
  • Please feel free to drop into #gdpr-compliance to continue discussions or if you have some time available to help out before beta.

Updates from focus leads and component maintainers

  • The 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/. team has a callout for help on register_meta, a reminder on the Gutenberg-related issues that need some help, a summary from their meeting last week about those GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/-related priorities, and a reminder on their next meeting tomorrow Thursday, May 3rd at 17:00 UTC focused on the `register_meta()` improvements.
  • @danielbachhuber has created a crowdsourced Gutenberg MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. Guide to document WordPress Classic Editor customization points and their Gutenberg equivalents, so please help contribute there if you’re able
  • The Internationalization team are resuming work on JS I18N, have posted on the background and some options, and plan to meet on Tuesday, May 8th at 15:00 UTC in #core-i18n to continue the discussion and planning

Next meeting

The next meeting will take place on May 9, 2018 at 20:00 UTC / May 9, 2018 at 20:00 UTC in the #core 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/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#4-9-6, #core, #dev-chat, #summary

Dev Chat Agenda: May 2nd (4.9.6 week 5)

This is the agenda for the weekly dev meeting on May 2, 2018 at 20:00 UTC / May 2, 2018 at 20:00 UTC:

  • 4.9.6 planning
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-9-6, #agenda, #core, #dev-chat

4.9.6 Beta Delayed: Two Days

The release of 4.9.6 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. is being delayed by two days. The new 4.9.6 beta release day is Thursday, May 3, 2018. The rest of the schedule will remain unchanged.

In a typical release cycle, when the beta date approaches, tickets deemed not ready are punted (or moved) to the next milestone so they can be given more attention. 4.9.6 is a unique release, in that some of the features slated for this release are time sensitive and cannot be punted.

The primary focus of 4.9.6 is delivering a set of tools for controlling and managing private information in a GDPR compliant manner. With GDPR going into effect on May 25th, 2018, this will be the last 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. before the new laws go into effect.

With this in mind, @allendav and myself have made the decision to delay the beta release by two days to allow for enough time to properly commit and backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. all features required for these tools.

#4-9-6

Dev Chat Summary: April 25th (4.9.6 week 4)

This post summarizes the dev chat meeting from April 25th (agenda, Slack archive).

4.9.6 planning

  • Would appreciate testing help so people working in #gdpr-compliance can land as many of the GDPR tickets as possible in 4.9.6
  • Beta planned for Tuesday, May 1st
  • Expecting to freeze most strings for betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process., Polyglots will also need lots of help translating strings coming in 4.9.6
  • #43862 will need some good old-fashioned hand testing when it lands

Updates from focus leads and component maintainers

  • @danielbachhuber posted GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/, 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/., and you to highlight several REST API-related tickets that are needed to support Gutenberg. Please take a look at those and consider attending the REST API office hours on Thursdays at 17:00 UTC.
  • The PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 Team posted minutes from their past two meetings, so scan through these and consider joining their next meeting on Monday, April 30th at 15:00 UTC to discuss the latest iteration of the php widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. and decide on whether the widget will default to collapsed.
  • @audrasjb and @danieltj posted their feedback on leading 4.9.5, its worth a read to see if there are areas each of us feel we can help improve the release process.

Bug scrub communication

  • @mindmantra and @desrosj noted that there’s no space on the Meetings page or otherwise to note scheduled Bug Scrubs besides the post that goes out on the topic
  • Would it help to communicate scheduled 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 other than the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. posts? If so, where/how?
  • Decision to add bug scrubs to the Meetings page for 4.9.6 and reasses after release if that worked well, if so we’ll make that standard for future releases and add to the core handbook

General announcements

Next meeting

The next meeting will take place on May 2, 2018 at 20:00 UTC / May 2, 2018 at 20:00 UTC in the #core 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/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#4-9-6, #core, #dev-chat, #summary

Dev Chat Agenda: April 25th (4.9.6 week 4)

This is the agenda for the weekly dev meeting on April 25, 2018 at 20:00 UTC / April 25, 2018 at 20:00 UTC:

  • 4.9.6 planning
  • Updates from focus leads and component maintainers
  • Bub scrub communication
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-9-6, #agenda, #core, #dev-chat

Dev Chat Summary: April 18th (4.9.6 week 3)

This post summarizes the dev chat meeting from April 18th (agenda, Slack archive).

4.9.6 planning

  • Focus on tickets from GDPR chat:
    • 43546 (@allendav), 43551 (@allendav), 43602 (@allendav), 43637 (@allendav), 43442 (@allendav), 43440 (@azaozz), 43473 (@idea15), 43435 (@idea15), 43492 (needs owner), 43715 (@xkon), 43436 (@xkon), 43547 (@tz-media?), 43620 (@xkon)
    • These tickets are in 4.9.6 milestone and would be good place to focus for folks looking to contribute to this 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.
  • Proposed timeline: BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. on Tuesday, May 1st, RC on Tuesday, May 8th, and Release on Tuesday, May 15th
  • @desrosj and @jbpaul17 working to confirm 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. scrub dates/times, will publish to Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

Updates from focus leads and component maintainers

  • The Editor / GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ Team released v2.7 and published information on how they’re organizing component-specific issues in their GitHub repo. Component Maintainers will benefit from utilizing the specific milestone setup for their component when trying to identify areas that would best benefit Gutenberg. There are also additional milestones for 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) and docs.
  • The GDPR Compliance Team published notes from their recent meeting covering recent deployments, available resources, 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 dev guidelines, and the addition of a privacy section to the readme.txt file
  • The PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 Team published notes from their recent meeting
  • The Media Team published notes from their recent meeting covering a time change for their meeting (to Thursday’s at 20:00 UTC) and their main focus on a Gutenberg Media triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.
  • @jorbin looking for a proposal on Make/Core post from team working on the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. reorg / no longer using srcwith a summary and proposed timeline; majority of current info is in #43055

Next meeting

The next meeting will take place on April 25, 2018 at 20:00 UTC / April 25, 2018 at 20:00 UTC in the #core 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/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#4-9-6, #core, #dev-chat, #summary

4.9.6 Schedule

This schedule has changed. Please refer to the 4.9.6 Schedule Changes for the new 4.9.6 release schedule.

The following is the current 4.9.6 release schedule:

Important Dates

  • BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.: Tuesday, May 1st.
  • RC: Tuesday, May 8th.
  • Release: Tuesday, May 15th.

Bug Scrubs

  • Tuesday, April 24th at 1600 UTC
  • Thursday, April 26th at 1600 UTC
  • Tuesday, May 1st at 1600 UTC
  • Thursday, May 3rd at 1700 UTC
  • Tuesday, May 8th at 1600 UTC
  • Tuesday, May 15th at 1600 UTC

GDPR Meetings

The GDPR compliance group meets in the #gdpr-compliance channel in 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/. every Wednesday at 1500 UTC.

#4-9-6

Dev Chat Agenda: April 18th (4.9.6 week 3)

This is the agenda for the weekly dev meeting on April 18, 2018 at 20:00 UTC / April 18, 2018 at 20:00 UTC:

  • 4.9.6 planning
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-9-6, #agenda, #core, #dev-chat