WordPress 6.4 Release Day Process

Preparation for the WordPress 6.4 release is completed. This post shares the release process, including the timeline and how you can help.

Release Timeline Overview

  • The Dry Run completed on Monday, November 6, 2023. โœ…
  • The 24-hour code freeze started on Monday, November 6, 2023, at 18:00 UTCย  โœ…
  • The release party is planned for . ๐Ÿ“…

Dry Run โœ…

The Dry Run is a key event as a final walk-through for the final release. As noted above, this was hosted on November 6 in the #core Slack channel.

What happens usually during the dry run?

  • Bug reports are reviewed to determine if any are critical to warrant another RCrelease 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). (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).).
  • Checks and any necessary updates are made in the src/wp-adminadmin (and super admin)/includes/update-core.php file.
  • Pre-release scripts are run to ensure test suites, coding standards, and other automated checks pass.

Since the results were acceptable, the release went into a 24-hour code freeze period.

24-Hour Code Freeze โœ…

After the dry run and before the release party starts, a mandatory 24-hour code freeze goes into effect.

What does this mean? No source code for 6.4.0 (i.e., in the 6.4 branchbranch 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".) can be changed during these 24 hours.

What happens if a critical 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. is reported during this period? The release squad will meet with committers and maintainers to determine if the issue is a blockerblocker A bug which is so severe that it blocks a release..

  • If yes, another RC release happens, and the release process restarts (meaning the dry run is repeated, and then the 24-hour code freeze clock restarts).
  • If not, then the bug is targeted for 6.4.1.

The Release Party ๐Ÿ“…

The WordPress 6.4 Release Party will start on Tuesday, November 7 at 18:00 UTC in the #core Slack channel.

The release party walks through the steps in the Major Version Release process for anyone who wants to follow along.

Please note releasing a major version requires more time than releasing a 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. or release candidate. There are more steps in the process. If any last-minute issues need addressing, more time will be needed.

How You Can Help

A key part of the release process is checking that the ZIP packages work on all the available server configurations. If you have some of the less commonly used servers available for testing (IIS, in particular), that would be super helpful. Servers running older versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher and MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com will also need testing.

You can start this early by running the WordPress 6.4 RC4 packages, which are built using the same method as the final packages.

During the release party, options will be provided on how to help test the release package.

Tips on What to Test

In particular, testing the following types of installs and updates would be much appreciated:

  • Does a new WordPress install work correctly? This includes running through the manual install process, as well as WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ or one-click installers.
  • Test upgrading from 4.0.38, 4.9.22, 5.8.6, 5.9.5, 6.0.3, 6.1.3, 6.2.2, 6.3.0, 6.3.1, 6.3.2 and 6.4 RC3, as well as any other versions possible.
  • Remove the wp-config.php file and test a fresh install.
  • Test single site and 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/networknetwork (versus site, blog) (both subdirectory and subdomain) installations.
  • Does it upgrade correctly? Are the files listed in $_old_files removed when you upgrade?
  • Does multisite upgrade properly?

Testing the following user flows on both desktop and mobile would be great to validate each function as expected:

  • Publish a post, including a variety of different blocks.
  • Comment on the post.
  • Install a new 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./theme, or upgrade an existing one.
  • Change the site language.
  • If youโ€™re a plugin developer, or if there are complex plugins you depend upon, test that theyโ€™re working correctly.

For a more in-depth list of what features to test, make sure to check the Help Test WordPress 6.4 post.


Thanks to @meher, @rmartinezduque, @hellofromtonya and @akshayar for the peer review

#6-4, #core, #release-process

Proposal: 2024 Major Release Timing

Following the conversation in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. chat a few weeks back (Oct. 25,ย Nov. 1), here are some proposed dates for releases in 2024. These are open to adjustment, but the current dates attempt to account for major holidays and WordPress events.

  • 6.5 โ€“ 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. 1 on Feb. 13, final release on Mar. 26 (WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what theyโ€™ve learned throughout the year and share the joy. Learn more. Asia Mar. 7-9)
  • 6.6 โ€“ Beta 1 on Jun. 4, final release on Jul. 16 (WordCamp Europe Jun. 13-15)
  • 6.7 โ€“ Beta 1 on Sep. 24, final release on Nov. 5 (WordCamp US still TBD)

Given that 2024 will hold a bulk of the work for Phase 3, I expect that 6.5 and 6.7 will be focused on those Collaborative features. I would like to propose that 6.6 be held specifically for maintenance and general polish of the software (as was wished for earlier this year).

Leave your thoughts in the comments on timing, focus, or anything that you think is key to discuss! And as always If youโ€™re interested in participating in a squad and want to know more, you canย pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test itโ€™s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of โ€œPing me when the meeting starts.โ€ย @davidbaumwald, @hellofromtonya, @jeffpaul, @priethorย or any former release squad member you know!

#planning

#6-5, #6-6, #6-7

WordPress 6.4 Release Candidate 4

The fourth 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). (RC4) for WordPress 6.4 is now available!

This unplanned RC4 release does not impact the general WordPress 6.4 release date, which is scheduled for November 7, 2023.

This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, itโ€™s recommended that you evaluate RC4 on a test server and site.

You can test WordPress 6.4 RC4 in three ways:

  1. 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.: Install and activate the WordPress Beta Tester plugin on a WordPress install (select the โ€œBleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.โ€ channel and โ€œ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./RCrelease 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). Onlyโ€ stream).
  2. Direct download: Download the RC4 version (zip) and install it on a WordPress site.
  3. Command line: Use the following WP-CLI command:
    wp core update --version=6.4-RC4

Read the RC1 announcement for featured highlights, and check the Make WordPress Core blog for 6.4-related posts. If you are looking for detailed technical notes on new features and improvements, the WordPress 6.4 Field Guide is for you.

The WordPress 6.4 release is brought to you by an underrepresented gender release squad to welcome the participation and partnership of those who identify as gender-underrepresented in the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project.

Whatโ€™s new in RC4

Thanks to all contributors who tested the Beta/RC releases and provided feedback. The following updates have been addressed since RC3:

  • #55858 โ€“ Fixed patterns not working anymore as a post template for custom type posts
  • #55859 โ€“ Fixed positioning and styles for the new lightboxโ€™s trigger.
  • #59812 โ€“ Fixed the following in Twenty Twenty-Four:
    • Removed the custom CSSCSS Cascading Style Sheets. for links.
    • Moved the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. stylesheet enqueuing to a new function.
    • Fixed height of newsletter landing pattern.
    • Resolved border colors in variations.

Get involved in testing

Your help in testing remains vital to developing the WordPress software and ensuring its quality.ย Check out this guideย for instructions on testing WordPress 6.4 features.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible 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. report. You can also check your issue against a list of known bugs.

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Update your theme or plugin

Hopefully, you have already tested your themes and plugins with WordPress 6.4 betas. With RC4, you will want to continue your testing and update the โ€œTested up toโ€ version in your pluginโ€™s readme file to 6.4.

Please post detailed information to the support forums if you find compatibility issues.

Documentation

Help the Docs team put the finishing touches on end-user documentation in time for the 6.4 release. Find out whatโ€™s needed and how you can help in this post.

Help translate WordPress

Do you speak a language other than English? ยฟEspaรฑol? Franรงais? Portuguรชs? ะ ัƒััะบะธะน? ๆ—ฅๆœฌ? Help translate WordPress into more than 100 languages.


Thank you @meher, @rmartinezduque and @hellofromtonya for collaborating on this post.

#6-4

WordPress 6.4 Accessibility Improvements

Thank you to @sereedmedia and @joedolson for writing this post.

This post seeks to provide an overview of the many accessibilityAccessibility 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) improvements and fixes coming to WordPress 6.4. This release addresses numerous issues that affect accessibility and general UIUI User interface consistency, including many long-standing wp-adminadmin (and super admin) bugs, such as a six-year-old issue adjusting the relative proximity of interface buttons โ€œDelete Menuโ€ and โ€œSave Menu.โ€

If youโ€™re interested in improving WordPress accessibility, please join the #accessibility channel in MakeWP 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 check out how to get involved. There are numerous contributing opportunities, such as testing, giving feedback, and working on accessibility issues.

Site Editor

The Site Editor includes improvements for consistent labeling and semantics in pattern and template management and the Navigation blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience..

  • #53755 โ€“ Comments form: Accessibility fixes for back-end
  • #53755 โ€“ Add missing aria roles to the โ€˜Replace template partโ€™ menu item
  • #53754 โ€“ Add missing aria roles to the โ€˜Create template partโ€™ menu item
  • #53739 โ€“ Add missing aria roles to the โ€˜Create patternโ€™ menu item
  • #52597 โ€“ Site Editor: Unify the delete button style in the dropdown menu with red
  • #53469 โ€“ Add accessible description of current Navigation block state
  • #53462 โ€“ Implement accessible version of Navigation overlay preview toggle control
  • #54418 โ€“ Navigation: Add ariaLabel block support
  • #52177 โ€“ Navigation block: Donโ€™t close submenu when it has focus
  • #52170 โ€“ Navigation block: Do not toggle aria-expanded on hover when the overlay menu is opened
  • #53373 โ€“ Search Block: Fix unintended wrapping of button text in โ€œButton onlyโ€ style
  • #52710 โ€“ Return focus more from focus return hook
  • #52678 โ€“ My patterns page: Increase color contrast for the toggle group
  • #52641 โ€“ Change Delete page menu item to Move to trashTrash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days..
  • #52634 โ€“ Password protected field: Remove autofocus and improve placeholder text consistency.
  • #52622 โ€“ Change password input to type text so contents are visible.
  • #52603 โ€“ Do not autofocus page title field in the โ€˜Draft a new pageโ€™ modal dialog
  • #52592 โ€“ Site Editor: Fix navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. actions order and label
  • #52251 โ€“ Navigation block: Add notice on reduced accessibility
  • #52271 โ€“ Site Editor: update headings hierarchy in the โ€˜Manage allโ€™ screens
  • #52263 โ€“ Fix incorrect aria-describedby attributes for theme patterns
  • #52930 โ€“ [Commands]: Add aria-activedescendant attribute to suggestions

Block Editor

The general block editor experience focuses on making labeling clearer and more consistent and improving the semantics of block and editor HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers..

  • #52885 โ€“ Edit site: Add missing label to post status password protected input field
  • #53691 โ€“ [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)] Fix: aria-haspop, aria-expanded attributes on the link format button.
  • #53692 โ€“ [a11y] Fix: aria-haspop and aria-expanded attributes on the inserter button.
  • #54324 โ€“ Table block: Fix semantic structure for screen readers on back-end
  • #54498 โ€“ Improve Notice component accessibility.
  • #54687 โ€“ Paragraph: Make โ€˜aria-labelโ€™ consistent with other blocks
  • #54590 โ€“ Allow Modal to place focus on first element within contents via new 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.
  • #54206 โ€“ Allow using a button element for button blocks
  • #54184 โ€“ Update nofollow control label
  • #52255 โ€“ Making Circular Option Picker a listbox
  • #45801 โ€“ Improve the placeholder instructions accessibility.
  • #52932 โ€“ ColorPalette, BorderControl: Donโ€™t hyphenate HEX value in aria-label
  • #52653 โ€“ Modal: Fix loss of focus when clicking outside
  • #52246 โ€“ Improve consistency of the Post editor and Site editor Document actions
  • #52495 โ€“ Item: Unify focus style and add default font styles
  • #53693 โ€“ [a11y] Fix: aria-haspop and aria-expanded attributes on list view button.
  • #54843 โ€“ Footnotes: Add aria-label to return links

User Interface

WordPress 6.4 fixes many long-term spatial layout and usability issues in the WordPress UI. Key changes include adjusting spacing between elements, repositioning certain actions for better flow, and using more intuitive icons, like replacing the โ€˜xโ€™ character with a clearer icon.

  • #40822 โ€“ Addressing proximity in the admin area.
  • #56594 โ€“ Change position of โ€œDelete menuโ€ action.
  • #58493 โ€“ User Profile Page: Vertical spacing inconsistency between label and field on smaller screens.
  • #59371 โ€“ Adjust theme details buttons to improve proximity of controls.
  • #59372 โ€“ Adjust theme details buttons in 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. to improve proximity of controls.
  • #58785 โ€“ Show dashicons-dismiss instead of the character โ€˜xโ€™ when we talk about the dashicon-dismiss.

Admin UI and Messages

With an emphasis on accessible messaging within the admin area, 6.4 addresses issues like making โ€œAdd Newโ€ links more descriptive, improving spoken messages for voice output, and adjusting the order and presentation of form elements and notifications.

  • #47125 โ€“ Admin: clarify the โ€œAdd Newโ€ links for better accessibility.
  • #58573 โ€“ Site Health: Improve the speak() messages.
  • #30685 โ€“ Better Login Error&Message Displaying.
  • #59229 โ€“ Add new post/page: admin notice when JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. is off canโ€™t install 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. by single click.
  • #58738 โ€“ Widgets page: Add missing H1 and admin notice when JS is off.
  • #58703 โ€“ wp-list-table: <label> is preceding <input> in the checkbox column.

Media-Related Fixes

As part of the lead-in to the planned Media Library updates, 6.4 enhances accessibility in a variety of media elements. Adjustments include adding alternative text support, improving select state issues in the Media Library, adhering to device settings, and ensuring focus states are maintained when editing images.

  • #58582 โ€“ XML-RPC API: Add alt field support.
  • #58756 โ€“ Media Library Improvements: UI, Non-Closing Options, and Button Select State Issues in Image Editing.
  • #55723 โ€“ Thumbnails Gifs for Plugins do not respect โ€œno motionโ€ device settings.
  • #59353 โ€“ Loss of focus when closing Image Rotation menu.

All 6.4 accessibility tickets are viewable in the WordPress Trac.

#6-4

Dev Chat Summary, November 1, 2023

The notes from the weekly WordPress developers chat which took place onย November 1, 2023 at 20:00 UTCin theย coreย channel ofย Make WordPress Slack.

Key Links

Announcements

WordPress 6.4 Release Candidate 3ย was released just before Dev Chat โ€“ please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed towards this.

Reminder: Dev Chat continues at 20:00 UTC throughout the year and does not change with daylight saving changes.

Highlighted Posts

A recording of theย Hallway hangout on performance improvements in WordPress 6.4ย is now available. The main points are also summarized on the post for anyone not able to access the recording.

Call for 6.4x release managersย โ€“ this followed a discussion in Dev Chat last week. Please add a comment to the post if you are interested in supporting the maintenance and minor releases. Thanksย to @jorbinย for putting this together.

Reminder:ย Call for contributors to assist with 6.4 End User documentation. Extra assistance will be appreciated to help with this as we move towards the release day.

Whatโ€™s new in Gutenberg 16.9.

Release Updates

Next major WordPress release: 6.4

Release candidates and rest of the cycle

RC3 was the lastย scheduledย 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)..

@hellofromtonya explained that another RCrelease 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). could possibly happen in the following circumstances. If a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.(s) gets reported and resolved, then yes, another might happen. But currently all regressions are resolved and shipped in RC3!

Next weekโ€™s schedule:

  • Dry Run โ€“ on Nov 6, 2023.
  • 24 hour code freeze starts after the Dry Run.
  • 6.4.0 release party starts on Nov 7, 2023 after the 24 hour code freeze expires.

Any issues relating to 6.4?

No other issues were raised during the meeting.

Relevant 6.4 links

No new links were published at the time of the meeting.

Field Guide for 6.4

@webcommsat: In addition to the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page., you can also find all Developer Notes relating to 6.4 using thisย tag. If you think aย change would benefit from an additionalย dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase., please add it to theย Documentation Tracker for 6.4. You can also tagtag 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.) one of the docs release co-leads in a message in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. if you want to discuss the possibility of an additional dev note and do not have access to the tracker.

Release parties schedule for 6.4

6.4 Release Candidates phase

This detailed guideย will walk you through testing features in WordPress 6.4.

Roadmap to 6.4ย โ€“ this release is scheduled for November 7, 2023.

6.4 Development Cycle

Future releases: 6.5

Timings and squad

  • @joemcgill followed up the question at last weekโ€™s dev chat on the formation of a release squad for 6.5.
  • @chanthaboune is thinking through the timing of releases across the year, and therefore there is no clear date for the first release of 2024 as yet. She hopes to bring a draft of suggested dates/ times by Monday November 6, 2023. This is the โ€˜only blockerblocker A bug which is so severe that it blocks a release.โ€™ for a call for volunteers. One person has contacted Josepha so far to participate in 6.5.
  • General agreement in the meeting for early planning for the next release.
  • the discussion on Slack.

Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets for 6.5

  • @oglekler requested triages to start as soon as possible, as 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. is already open and 6.5 Alpha has begun. She raised a call for volunteers.
  • discussion followed on updating the core handbook to reflect that triages 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 can be held at any time, and to clarify that any contributors wanting to run a scrub did not need to wait for a completed release cycle or for a squad to be formed. The possibility of a post highlighting and calling for volunteers was suggested for the future.
  • a number of experienced core developers are able to buddy or give advice to help anyone less familiar with running scrubs.
  • if you can volunteer to run a scrub, you can share details in a future dev chat or comment on the summary post, and also post the information 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 ahead of time to best ensure that others are aware and can gather to help at the scrub. The core triage lead or the Core Team Reps can also update the bug scrub post in Make/Core.
  • if you are wanting to run a scrub related to particular component(s), please contact the component maintainers who can help and share information on priority tickets or planned scrubs.

The full discussion on triaging and bug scrubs.

Tickets or components help requests

No tickets were mentioned in the meeting.

Open floor

Reminders for the following were brought up right before the meeting ended:

Call for contributors to assist with 6.4 End User documentation. Volunteers can also post in this thread from the meeting.

Call for 6.4x release managers

Next meeting

The next meeting will be onย Wednesday November 8, 2023, at 20:00 UTC.

After Dev Chat posts for attention:

Hallway Hangout: Issues Triage Extending Gutenberg โ€“ note this will take place on November 10, 2023 at 16:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on theย #coreย Slack channel or contact one of the Core Team reps.

Props toย @zunaid321 for contribution to the notes, and to @marybaum for review.

#6-4, #6-5, #dev-chat, #meeting, #summary

Dev Chat Summary, October 25, 2023

The notes from the weekly WordPress developers chat which took place onย October 25, 2023 at 20:00 UTC in theย coreย channel ofย Make WordPress Slack.

Key Links

Announcements

WordPress 6.4 Release Candidate 2ย is available โ€“ please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed towards this.

Summary and Insights of Phase 3 related conversations

WordPress 6.4 Release Candidate Phase

WordPress 6.4 Field Guide

Highlighted Posts

Summary and Insights of Phase 3 related conversations

WordPress 6.4 Release Candidate Phase

WordPress 6.4 Field Guide

Release Updates

Next major WordPress release: 6.4

New 6.4 related posts

6.4 Release Candidates phase

Update from contributors on docs for this release:

  • Field Guide for 6.4
  • You can also find all Developer Notes relating to 6.4 using thisย tag
  • If you think aย ticketticket Created for both bug reports and feature development on the bug tracker.ย needs aย dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.ย and it has not been highlighted previously, send a message to Nalini 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/ for those working on the docs release or add it to theย Documentation Tracker for 6.4
  • Call for contributors to assist with 6.4 End User documentation

Any issues relating to 6.4 tickets?

Existing 6.4 useful links

Release parties schedule for 6.4

This detailed guideย will walk you through testing features in WordPress 6.4.

Roadmap to 6.4ย โ€“ this release is scheduled for November 7, 2023.

Bug Scrub Schedule 6.4

6.4 Development Cycle

Project Board for Editor Tasks for WordPress 6.4ย onย GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the โ€˜pull requestโ€™ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/

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/

Whatโ€™s new in Gutenberg 16.9? (25 October) โ€“ Other than the new release update, nothing related to Gutenberg was brought up in the meeting.

Components & Tickets

The following tickets were raised in the meeting for feedback:

TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket #59718: Short-term (WP 6.4) hotfix to prevent fatal error in standalone Gutenberg (<16.5)

Trac ticket #59289: About Page for 6.4 Release

Trac ticket #59722: Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.: class-wp-rest-server.php

For the above tickets check out theย Slack discussionย for more information.

Trac ticket #59723: Pattern file containing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher constant from theme causes fatal error on update to WordPress 6.4 โ€“ was brought up by @hellofromtonya since this issue is in 6.3 and 6.4 and causes a fatal error during the upgrade process. Check out theย Slack discussionย for more info.

More tickets were brought up by @hellofromtonya as they need attention:

Trac ticket #59736: Regression: Singular blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. template โ€“ regression introduced in 6.4 by r56507. Has a 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. on it and explanation.

Trac ticket #59723: Pattern file containing PHP constant from theme causes fatal error on update to WordPress 6.4 โ€“ fatal error during WP upgrade

Trac ticket #55493: [Block] File: Embedded PDF fails to render in Safariย โ€“ regression in File block introduced in 6.4

Trac ticket #59732: Theme live preview is broken โ€“ 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. theme live previewers are broken, which 6.4 didnโ€™t cause but help to emphasis it. Thereโ€™s a patch thatโ€™s ready to test. Need to better understand its impact in 6.4.

Trac ticket #58281: Rollback Auto-Update (Rollback part 3) โ€“ check out theย Slack discussionย for more info as it was raised byย @afragen

Open floor

@jeffpaul highlighted for post 6.4, theย Community Summit Discussion Notes: Aligning processes and contributions between WordPress Core and Gutenberg. He especially drew attention to this topic to those who are active during the 6.4 release and particularly with the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./Gutenberg interactions. He asked for them to share their insights and thoughts on the post to help improve planning, shared processes and to make things easier for the future.

@joemcgill raised a query on the planning and squads formation for the future major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope., 6.5, and the 6.4.1, 6.4.2 etc minor releases. Theย Slack discussion.

Next Meeting

The next meeting will be onย Wednesday November 1, 2023, at 20:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on theย #coreย Slack channel.

Props toย @webcomms and @marybaum for input into the summary and for review.

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

Hallway Hangout: Issues Triage Extending Gutenberg

In many conversations, the question comes up about what the stage is on getting more extensibility features, hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., and filters into the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor. In the 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/ GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the โ€˜pull requestโ€™ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ Repository, there are approximately 110 issues labeled with โ€œExtensibilityโ€ and 20 with โ€œBlocks Adoptionโ€.ย 

If you are interested in discussing those issue and how they can be solved, you are invited to join Tammie Lister, Fabian Kรคgy, myself and others to have an informal conversation on what the next steps are for each issue to move it forward.ย 

Join us for Hallway Hangout: Issues Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Extending Gutenberg on November 10th at 16:00 UTC
The Zoom link will be shared in time in the #core-editor channel.ย 

Props for review @fabiankaegy @karmatosed and @mamaduka

Dev Chat agenda, November 1, 2023

The next weekly WordPress developers chat will take place onย Wednesday, November 1, 2023 at 20:00 UTCย in theย coreย channel ofย Make WordPress Slack. Note, the 6.4 RC3 is scheduled for November 1, so there may be a change in Dev Chat timings if needed. Please check the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel for updates.

Further items will continue to be added as they come up in core and release leads channels 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/.

Welcome and housekeeping

All are welcome to join Dev Chat.

If you can help with dev chat summaries, please raise your hand in the meeting. It is a busy time and additional people are appreciated.

Announcements

WordPress 6.4 Release Candidate 3 โ€“ was released today.

Highlighted posts

Due to time constraints during a release and to prioritize 6.4 items, some of the highlighted posts may not be raised during the live Dev Chat meeting.

Recording of the Hallway hangout on performance improvements in WordPress 6.4 is now available. The main points are also summarized on the post for anyone not able to access the recording.

Call for 6.4x release managers โ€“ this followed a discussion in Dev Chat last week. Please add a comment to the post if you are interested in supporting the maintenance and minor releases. Thanks @jorbin for putting this together.

Reminder: Call for contributors to assist with 6.4 End User documentation. Extra assistance will be appreciated to help with this as we move towards the release day.

Whatโ€™s new in Gutenberg 16.9

Forthcoming release updates

Next major WordPress release: 6.4

Updates or important discussions relating to the final week of the release.

Any issues relating to 6.4?

Existing 6.4 useful links

Field Guide for 6.4

You can also find all Developer Notes relating to 6.4 using thisย tag. If you think anotherย change would benefit from aย dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.ย and it has not been highlighted previously, add it to theย Documentation Tracker for 6.4.

Release parties schedule for 6.4

6.4 Release Candidates phase

This detailed guideย will walk you through testing features in WordPress 6.4.

Roadmap to 6.4 โ€“ this release is scheduled for November 7, 2023.

Bug Scrub Schedule 6.4

6.4 Development Cycle

Project Board for Editor Tasks for WordPress 6.4 on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the โ€˜pull requestโ€™ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/

Tickets or Components help requests

This section is subject to change depending on the needs of the release.

Please add any items for this part of the agenda to the comments โ€“ tickets for 6.4 will be prioritized. If you can not attend dev chat live, donโ€™t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

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

Editor Chat Agenda: Wednesday, November 1st, 2023

Facilitator and notetaker:ย @andraganescu.

This is the agenda for the weeklyย editor chatย scheduled forย Wednesday, 1 November 2023, 03:00 PM GMT+1

This meeting is held in theย #core-editorย channel in Making WordPressย 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/.

  • Announcements
  • Project updates
  • Open Floor

If you are not able toย attendย the meeting, you are encouraged to share anything relevant to the discussion:

  • If you have an update for the main site editing projects, please feel free to share it as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.
#agenda, #core-editor, #core-editor-agenda, #meeting

Performance Chat Summary: 31 October 2023

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members ofย #core-performance
  • WordPress 6.4ย 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). 3 is tomorrow
  • Theย Performance Hallway Hangoutย blogblog (versus network, site) post has been updated with a recording of the session

Priority Projects

Server Response Time

Link to roadmap projects and link to the GitHub project board

Contributors: @joemcgill @swissspidy @thekt12 @mukesh27 @pereirinha

  • @joemcgill One of the focuses for 6.5 will looking at several tickets related to improving template loading:ย https://github.com/WordPress/performance/issues/746
  • @thekt12 As a part of 746, โ€“ Created a PoC to test out if persistent cache better than default function for checkingย files_existsย #59314 (ย PR#5597ย ).
    Need to get some numbers for that
  • @joemcgill As weโ€™ve talked about this exploration, one of the things that came up was the need to come up with a solid approach for cache invalidation, if we do find that the effort is worth pushing forward. Somewhat related, we have #59719 that would be great to get feedback on from anyone interested
  • @pereirinha as for #59595 thereโ€™s already a PR and some feedback to look into. The proposed solution is to use object caching. The CPU impact and the wall time are greatly improved, but thereโ€™s the memory cost. Iโ€™ll be circling back on the feedback shortly

Database Optimization

Link to roadmap projects and link to the GitHub project board

Contributors: @mukesh27 @thekt12

  • @mukesh27 Iโ€™ve been working on #56912, but it appears that this ticketticket Created for both bug reports and feature development on the bug tracker. is no longer valid. Some options have been autoloaded in WordPress 6.3, while the remaining options are not loaded in WordPress. Therefore, we should proceed to close this ticket. We are awaiting feedback from Jonny before finalizing the decision.
    • @joemcgill We can give it a couple days to see ifย @spacedmonkey has anything to add, but think itโ€™s ok to close if you andย @flixos90 agree, since Jonnyโ€™s been away
  • @brianhenryie On the templates caching, I see itโ€™s usingย file_exists()ย but elsewhere in WP I seeย is_readable()ย which is more correct, and presumably slightly slower.
    • @joemcgill I think the current implementation is simply for testing purposes, but would you mind adding a comment to the ticket so we remember to review that?

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a userโ€™s browser. https://www.javascript.com & CSSCSS Cascading Style Sheets.

Link to roadmap project and link to the GitHub project board

Contributors: @mukesh27 @10upsimon @westonruter

  • No updates this week

Images

Link to roadmap projects and link to the GitHub project board

Contributors: @flixos90 @thekt12 @adamsilverstein @joemcgill @pereirinha @westonruter

  • @westonruter Iโ€™ve got anย initial PRย open to introduce an โ€œImage Loading Optimizationโ€ module for the Performance Lab 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.. In addition to having scaffolding for the module, this PR also introdues output buffering for template renders as well as a 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. manipulating the output buffer prior to flushing. Reviews for this PR would be appreciated so it can be merged. This will then be used in subsequent PRs for the module to optimize the loading of images (and other things). For example, I have anย early draft PRย for the detection logic to determine which image is LCP and which images should not be lazy-loaded. Seeย overview issue.

Measurement

Link to roadmap projects and link to the GitHub project board

Contributors: @adamsilverstein @joemcgill @mukesh27 @swissspidy @flixos90

  • @swissspidy For theย metrics stabilization explorationย I did share someย preliminary findingsย the other day based on my testing. Iโ€™m a bit out of options right now as I donโ€™t think Iโ€™ve found a magic bullet that just eliminates any variance, so Iโ€™d appreciate some eyes there.
  • @joemcgill Related to measurement, Iย reported hereย yesterday some observations I made about the automated benchmarking workflow weโ€™ve been experimenting with during this release. Discovering that running benchmarks on the two themes sequentially, was causing the classic theme results to be skewed. Iโ€™ve openedย a PRย onย @swissspidyโ€˜s repo that allows you to choose which theme you want to test, as one approach to avoiding that issue.

Ecosystem Tools

Link to roadmap projects and link to the GitHub repo

Contributors: @mukesh27 @swissspidy @westonruter

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27 @10upsimon

Open Floor

  • n/a

Our next chat will be held on Tuesday, November 7, 2023 at 16:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary