Title: Brian Alexander – Make WordPress Core --- # Author Archives: 󠀁[Brian Alexander](https://profiles.wordpress.org/ironprogrammer/)󠁿 [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 8:54 pm _on_ December 4, 2024 Tags: [consent-api ( 5 )](https://make.wordpress.org/core/tag/consent-api/), [core-privacy ( 53 )](https://make.wordpress.org/core/tag/core-privacy/), [feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/), [privacy ( 39 )](https://make.wordpress.org/core/tag/privacy/), [privacy-roadmap ( 2 )](https://make.wordpress.org/core/tag/privacy-roadmap/) # 󠀁[Let’s reconsider adopting the WP Consent API](https://make.wordpress.org/core/2024/12/04/lets-reconsider-adopting-the-wp-consent-api/)󠁿 This post is a follow up to [Feature Plugin Proposal: WP Consent API](https://make.wordpress.org/core/2020/04/01/feature-plugin-proposal-wp-consent-api/) from 2020, which as part of the [Core Privacy Roadmap](https://make.wordpress.org/core/roadmap/privacy/), proposed a framework to allow extenders to coordinate user consent signals and help websites honor user privacy preferences. ## Objective of this proposal The legal and moral implications around respect for user consent and tracking have evolved steadily since the [original proposal](https://make.wordpress.org/core/2020/04/01/feature-plugin-proposal-wp-consent-api/) was published in 2020. Powering over 40% of the web, WordPress is in a position to lead by example and provide site operators built-in and extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. means to address these concerns. **This proposal seeks to gather consensus around adopting the WP Consent 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. for inclusion in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..** ## A brief history of the API In early 2020, the [WP Consent API](https://wordpress.org/plugins/wp-consent-api/) feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See [Features as Plugins](https://make.wordpress.org/core/handbook/about/release-cycle/features-as-plugins/) was announced. It enables the setting and retrieval of user consent preferences, made accessible to plugins that register with the API. It was designed to be lean and unobtrusive, opt-in only, and with no UIUI User interface. Rather than try to enforce cookie-setting compliance itself, the API lets opted- in plugins verify consent before placing cookies. It also allows consent categories to be defined and user choices set and stored by consent management providers (CMPs) and other extenders, where the technical and legal details around the various flavors of consent can be managed outside of WordPress. In December 2020 the Consent API feature was swept up along with other features during a clean up of the [features list](https://make.wordpress.org/core/features/), and marked as “Closed”. However, subsequent discussions in [#core-privacy](https://wordpress.slack.com/archives/C9695RJBW) in following months were incognizant of the change, and there was [confusion that it had been marked closed](https://wordpress.slack.com/archives/C02QB8GMM/p1616547372027400?thread_ts=1615972427.002600&cid=C02QB8GMM) when attempts were made to move the 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. to the WordPress 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/](https://github.com/) org. Until early this year, adoption of the plugin was minimal, but has been steadily maintained by [@rogierlankhorst](https://profiles.wordpress.org/rogierlankhorst/), [@szepeviktor](https://profiles.wordpress.org/szepeviktor/), [@xkon](https://profiles.wordpress.org/xkon/), [@aurooba](https://profiles.wordpress.org/aurooba/), [@mujuonly](https://profiles.wordpress.org/mujuonly/), [@phpgeekdk](https://profiles.wordpress.org/phpgeekdk/), [@paapst](https://profiles.wordpress.org/paapst/), [@aahulsebos](https://profiles.wordpress.org/aahulsebos/), [@pputzer](https://profiles.wordpress.org/pputzer/), and [@markwolters](https://profiles.wordpress.org/markwolters/). ## Why does this matter now? In March 2024, enforcement of the European Union’s [Digital Markets Act](https://digital-markets-act.ec.europa.eu/index_en)( DMA) began, and adoption of the plugin has since [grown from under 1,000 to over 100,000 active installations](https://wordpress.org/plugins/wp-consent-api/advanced/). Uptake of the plugin can largely be attributed to consent-requiring plugins such as [Google Site Kit](https://wordpress.org/plugins/google-site-kit/), [WooCommerce](https://wordpress.org/plugins/woocommerce/), and [WP Statistics](https://wordpress.org/plugins/wp-statistics/), which use the API to support site analytics, advertising, marketing, and 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.) management. [[ Beyond the DMA, there are [numerous other privacy-focused regulations](https://usercentrics.com/knowledge-hub/data-privacy-in-2024-what-we-are-watching/) around the world that over the past few years have come into effect, or will soon. User consent is a key theme to achieving many of these protections, and WordPress can provide the foundation on which consent plugins interact. ## Considerations for Core adoption The API has remained largely unchanged since its introduction, so would likely require refreshing to meet today’s Core merge expectations. There may also be features that need to be revisited, such as how non-consent-related plugins [appear in Site Health recommendations](https://github.com/Really-Simple-Plugins/wp-consent-level-api/blob/master/site-health.php#L83). Along with the API, Core could implement a default cookie “popup” or 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. that could be activated similar to the built-in [Privacy Policy feature](https://wordpress.org/documentation/article/settings-privacy-screen/). This would give site owners a simple mechanism to request and track consent (cookie- based), and be customizable without requiring an additional plugin. A sample use would be to request “statistics” consent through the popup, styled through a theme, and wrap client-side tracking code inside a `[wp_has_consent()](https://github.com/Really-Simple-Plugins/wp-consent-level-api/blob/adaedac6ed8e1cac3e53bb34e4f06c39772b7a78/assets/js/wp-consent-api.js#L23)` check. Extenders can take things further by expanding the default categories and storage mechanism for more advanced integrations, as current adopters of the API do today. ## Canonical plugin alternative If adding this feature to Core is not viable at this time, then another option would be to [make it canonical](https://make.wordpress.org/core/2022/09/11/canonical-plugins-revisited/). While originally developed under [@rogierlankhorst](https://profiles.wordpress.org/rogierlankhorst/)‘ s personal repo, it has since been migrated to that of a [specific plugin developer and vendor](https://github.com/Really-Simple-Plugins/) in the CMP space. Considering the original intent that this feature be merged to Core, agreement from Rogier that it remain available to the community, and the API’s adoption by [other vendors](https://github.com/Really-Simple-Plugins/wp-consent-level-api/blob/master/readme.txt#L61), officially bringing the plugin into the WordPress org would send a clear signal to site owners and extenders that this is a community-built and supported standard. ## Where to find more info * [#44043: Framework for logging/retrieving a users consent state](https://core.trac.wordpress.org/ticket/44043) * [Core Privacy Roadmap](https://make.wordpress.org/core/roadmap/privacy/) * [Feature Plugin Proposal: WP Consent API](https://make.wordpress.org/core/2020/04/01/feature-plugin-proposal-wp-consent-api/) * [WP Consent API](https://wordpress.org/plugins/wp-consent-api/) plugin page and [demo site](https://wpconsentapi.org/) * [GitHub repo](https://github.com/Really-Simple-Plugins/wp-consent-level-api) * Discussions in [#core-privacy](https://wordpress.slack.com/archives/C9695RJBW) ## Share your thoughts What do you think about WordPress paving the way for easier integration of consent- based privacy controls? Please comment below, especially if you have dealt with implementing consent management in WordPress. _Special thanks to [@rogierlankhorst](https://profiles.wordpress.org/rogierlankhorst/) and [@azaozz](https://profiles.wordpress.org/azaozz/) for review and feedback on this post._ [#consent-api](https://make.wordpress.org/core/tag/consent-api/) [#core-privacy](https://make.wordpress.org/core/tag/core-privacy/) [#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/) [#privacy](https://make.wordpress.org/core/tag/privacy/) [#privacy-roadmap](https://make.wordpress.org/core/tag/privacy-roadmap/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 11:39 pm _on_ January 31, 2024 Tags: [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [core ( 740 )](https://make.wordpress.org/core/tag/core/), [core-editor ( 754 )](https://make.wordpress.org/core/tag/core-editor/), [dev chat ( 917 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 973 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat Summary, January 31, 2024](https://make.wordpress.org/core/2024/01/31/dev-chat-summary-january-31-2024/)󠁿 [Start of meeting on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1706731277511609) This Dev Chat [continues the experiment](https://make.wordpress.org/core/2024/01/16/dev-chat-agenda-january-16-2024/) to focus chat time on discussions related to open CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. proposals and release issues, rather than repeating links already highlighted in the [curated agendas](https://make.wordpress.org/core/tag/dev-chat+agenda/). Please read the [Dev Chat Agenda](https://make.wordpress.org/core/2024/01/31/dev-chat-agenda-january-31-2024/) for a curated list of [announcements](https://make.wordpress.org/core/2024/01/31/dev-chat-agenda-january-31-2024/#announcements), [discussions](https://make.wordpress.org/core/2024/01/31/dev-chat-agenda-january-31-2024/#discussions), [highlighted posts](https://make.wordpress.org/core/2024/01/31/dev-chat-agenda-january-31-2024/#highlighted-posts), [core-editor updates](https://make.wordpress.org/core/2024/01/31/dev-chat-agenda-january-31-2024/#core-editor-updates), [major and minor release updates](https://make.wordpress.org/core/2024/01/31/dev-chat-agenda-january-31-2024/#releases), and more. ## Announcements Following announcement of yesterday’s [6.4.3 release](https://wordpress.org/news/2024/01/wordpress-6-4-3-maintenance-and-security-release/), [@jorbin](https://profiles.wordpress.org/jorbin/) noted that there was [one issue of note](https://core.trac.wordpress.org/ticket/60398), but that there were workarounds available at this time. [@jorbin](https://profiles.wordpress.org/jorbin/) further [gave props](https://wordpress.slack.com/archives/C02RQBWTW/p1706731764936289) to those who helped facilitate the release. [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) shared that [@joemcgill](https://profiles.wordpress.org/joemcgill/) has [accepted his nomination to serve as a 2024 Core team rep](https://make.wordpress.org/core/2023/12/04/nominations-for-core-team-reps-2024-edition/#comment-46130) 🎉. The search continues for a co-rep, where [it’s been noted](https://make.wordpress.org/core/2023/12/04/nominations-for-core-team-reps-2024-edition/#comment-45960) that a contributor from the Core Editor team would be a great compliment, though not required. Nominations remain open until April 1, 00:00 UTC. ## Discussion on open proposals in Core ### 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](https://make.wordpress.org/core/handbook/about/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. Publish Date Link to post: [Proposal: An update to the Field Guide](https://make.wordpress.org/core/2023/08/31/proposal-an-update-to-the-field-guide/) [Conversation start link](https://wordpress.slack.com/archives/C02RQBWTW/p1706731979070329) **Comments:** * [@jorbin](https://profiles.wordpress.org/jorbin/) was under the impression that neither the dev blogblog (versus network, site) team nor 6.4 release leads were interested in moving forward with the proposal. [@webcommsat](https://profiles.wordpress.org/webcommsat/) shared that 6.4 docs release leads didn’t see 6.4 as the deadline, and discussions were continuing. [@joemcgill](https://profiles.wordpress.org/joemcgill/) agreed that the proposal wasn’t release specific, but rather an adjustment to timing of when field guide information is released. [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) also added that the dev blog team has [opened a discussion](https://github.com/WordPress/developer-blog-content/discussions/169) to track the second part of the proposal. * [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) [referred](https://wordpress.slack.com/archives/C02RQBWTW/p1706732238212129) to [@chanthaboune](https://profiles.wordpress.org/chanthaboune/)‘s comment of where best to separate field guide content based on audiences, suggesting the proposal could be adjusted accordingly. [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) added that some folks have difficulty processing field guide information to determine what is relevant and actionable, which [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) agreed should be explored. [@webcommsat](https://profiles.wordpress.org/webcommsat/) agreed with the notion to target field guide content to particular audiences, but also to look at how it relates to other new content produced for the release. * [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) suggested the potential to target content according to the five user groups identified in [Care and influence: a theory about the WordPress community](https://make.wordpress.org/updates/2020/05/01/care-and-influence-a-theory-about-the-wordpress-community/). * [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) asked if the field guide info would be more easily consumable if it was split into a canonical structure, such as `wordpress.org/6-5/field-guide/`, with subpages that match particular areas or audiences. * [@webcommsat](https://profiles.wordpress.org/webcommsat/) noted that segmentation between audiences has grown, and suggested it’s a good time to use teams’ audience- specific insights to improve the field guide format. She added that exploring how best to utilize the limited people and time for the Docs team would be an important factor in implementing improvements. [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) agreed with concerns around challenges in gathering/publishing content, but noted that the issue should be considered as separate from the proposal. * [@jorbin](https://profiles.wordpress.org/jorbin/) [shared](https://wordpress.slack.com/archives/C02RQBWTW/p1706732799696259) that the original published field guide was the result of an overly long email sent 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. developers. * First-time [Docs Co-Lead](https://make.wordpress.org/core/6-5/) [@estelaris](https://profiles.wordpress.org/estelaris/) 🎉 asked about adding additional comments to the proposal. [@jorbin](https://profiles.wordpress.org/jorbin/) noted that Make/Core comments close automatically after 180 days (~6 months). [@costdev](https://profiles.wordpress.org/costdev/) shared that adding the `# keep-comments-open` 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.) would reenable them, but recommended removing the tag once an updated timeframe for feedback has been reached. [@jorbin](https://profiles.wordpress.org/jorbin/) [updated the Core handbook](https://make.wordpress.org/core/handbook/best-practices/post-comment-guidelines/#comments-on-posts) to reflect this info. * [@joemcgill](https://profiles.wordpress.org/joemcgill/) pointed out that the team should review all current channels where field guide-related content is published, to check whether only updating the field guide [in one place] would sufficiently improve the broader sharing of release updates to the community. He suggested engaging with the Docs and Marketing teams to move forward, and [@estelaris](https://profiles.wordpress.org/estelaris/) noted she would begin by sharing with Docs. [@webcommsat](https://profiles.wordpress.org/webcommsat/) suggested looping in Training as well. [@laurlittle](https://profiles.wordpress.org/laurlittle/) noted that the Marketing team could brainstorm on the proposal for future releases, if not 6.5. * In response to [@joemcgill](https://profiles.wordpress.org/joemcgill/), [@webcommsat](https://profiles.wordpress.org/webcommsat/) noted that there have been past lists of channels and audiences, and suspects more current info should be available. She also suggested it might be helpful to have a single post that links out to the various user groups identified earlier, and to link to that post from the About page. * [@jorbin](https://profiles.wordpress.org/jorbin/) referred back to [@jeffpaul](https://profiles.wordpress.org/jeffpaul/)‘ s input and asserted that the dev blog and other team areas might be better places to communicate field guide information, as opposed to Make/Core. [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) asked if, considering this perspective, the proposal was actionable by the Core team, or if the proposal should be re-worked as a cross-team collaboration. [@jorbin](https://profiles.wordpress.org/jorbin/) suggested that the teams publishing the field guide info would take on the proposal. * [@joemcgill](https://profiles.wordpress.org/joemcgill/) noted that it can be difficult to know the status of a proposal, suggesting some way of flagging these posts. [@marybaum](https://profiles.wordpress.org/marybaum/) suggested a visual system to convey “stalled”, “live”, etc, and [@joemcgill](https://profiles.wordpress.org/joemcgill/) raised the idea of a 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. pattern. [@desrosj](https://profiles.wordpress.org/desrosj/) shared that in past proposals ([example](https://make.wordpress.org/core/2022/01/31/ensuring-proper-attribution-for-contributions-to-wordpress-on-github/)) he has added status info to the top of the post, assuming the status was clear. * [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) wrapped up the discussion based on the chat, concluding that the proposal be marked **closed**(“ not accepted”), or must be **picked up by another team(s)**. **Actions:** * Part 1: Move Make/Core field guide publication ahead one week, aligning with last scheduled 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., rather than RC1. **Not accepted ❌** * Part 2: Start publishing a simplified field guide to the [WordPress Developer Blog](https://developer.wordpress.org/news/).** Not accepted ❌** * Other teams to explore revising and adopting this proposal: - [@estelaris](https://profiles.wordpress.org/estelaris/) to share the proposal with Docs. - [@laurlittle](https://profiles.wordpress.org/laurlittle/) to raise the proposal to Marketing for possible brainstorm. - [@webcommsat](https://profiles.wordpress.org/webcommsat/) to loopLoop 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](https://codex.wordpress.org/The_Loop) in Training to gauge their interest in furthering the proposal. - To highlight in dev blog. ## Open Floor * [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) reminded everyone that 6.5 Beta 1 is approaching fast: February 13 (less than two weeks). * [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) asked for more code reviews and testing of a major 6.5 feature, the [Font Library](https://core.trac.wordpress.org/ticket/59166#comment:27), with [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) noting that reviews/issues should be tracked in the [Gutenberg repo](https://github.com/wordpress/gutenberg/issues). She also shared that several contributors are working to smooth the merge process ahead of [expected merge patches](https://core.trac.wordpress.org/ticket/59166#comment:27) to Core. _Props [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) for peer review._ [#6-4](https://make.wordpress.org/core/tag/6-4/), [#6-5](https://make.wordpress.org/core/tag/6-5/), [#core](https://make.wordpress.org/core/tag/core/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 9:46 pm _on_ January 25, 2024 Tags: [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [core ( 740 )](https://make.wordpress.org/core/tag/core/), [core-editor ( 754 )](https://make.wordpress.org/core/tag/core-editor/), [dev chat ( 917 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 973 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat Summary, January 24, 2024](https://make.wordpress.org/core/2024/01/25/dev-chat-summary-january-24-2024/)󠁿 [Start of meeting on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1706126471542129) facilitated by [@webcommsat](https://profiles.wordpress.org/webcommsat/) This DevChat starts with an experiment to shift the chat to synchronize discussions on open coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. proposals and release issues rather than reproducing links highlighted in the curated agendas. Please read the [DevChat Agenda](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/) for a curated list of [discussions](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#discussions), [highlighted posts](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#highlighted-posts), [core-editor updates](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#core-editor-updates), [major and minor release updates](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#releases), and more. ## Discussion on open proposals in Core ### Interactivity 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. Link to post: [](https://make.wordpress.org/core/2023/12/05/proposal-default-theme-task-force-for-2024/) [Proposal: The Interactivity API – A better developer experience in building interactive blocks](https://make.wordpress.org/core/2023/03/30/proposal-the-interactivity-api-a-better-developer-experience-in-building-interactive-blocks/) [Conversation start link](https://wordpress.slack.com/archives/C02RQBWTW/p1706126751171389) **Comments:** * The API is well beyond the proposal stage, with nothing actionable in discussion. **Actions:** * The proposal should be considered “accepted”. ### HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API: Introduce `WP_HTML::tag()` for safely creating HTML Link to PR (draft): [https://github.com/WordPress/wordpress-develop/pull/5884](https://github.com/WordPress/wordpress-develop/pull/5884) [Conversation start link](https://wordpress.slack.com/archives/C02RQBWTW/p1706127033627819) **Comments**: * This PR was raised along with the question of how items should be added to the agenda. It was clarified that topics can be added as comments to the [previous week’s chat summary](https://make.wordpress.org/core/tag/dev-chat+summary/), or to the [current week’s agenda post](https://make.wordpress.org/core/tag/dev-chat+agenda/)( typically published on Tuesdays). And of course, any item can be raised during the open floor section of Dev Chat. * [@dmsnell](https://profiles.wordpress.org/dmsnell/) indicated that the [PR for consideration](https://github.com/WordPress/wordpress-develop/pull/5884) is a scaled back version of a larger [templating system proposal](https://github.com/dmsnell/wordpress-develop/pull/12), which will not be ready for 6.5. The PR adds a helper utility, `WP_HTML::tag()`, to conveniently generate single HTML tags with attributes. The impetus for this feature is to provide Core and extenders a safer way to generate HTML tags, compared with reliance on proper usage of functions such as `esc_attr()`, which might be overlooked and introduce HTML injection vectors. * [@jorbin](https://profiles.wordpress.org/jorbin/) would prefer that any new APIs be used by Core itself, and that there be accessory patches prepared that demonstrate how the function integrates and operates in Core. It was also suggested that a [Make/Core](https://make.wordpress.org/core/) proposal would help with gathering broader input. * [@azaozz](https://profiles.wordpress.org/azaozz/) pointed out that enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. tickets in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are another form of “proposal”, and can also result in healthy discussion. He suggested starting the discussion in Trac, and then utilizing a Make/Core proposal if the ticketticket Created for both bug reports and feature development on the bug tracker. isn’t sufficient to establish consensus. * There continued discussion around [how Core generates HTML](https://wordpress.slack.com/archives/C02RQBWTW/p1706128358864169) currently, which [relies on proper use of `esc_*()` and `echo()`](https://wordpress.slack.com/archives/C02RQBWTW/p1706128553820559), as well as a broader [discussion around safely generating HTML](https://wordpress.slack.com/archives/C02RQBWTW/p1706133508680769?thread_ts=1706128553.820559&cid=C02RQBWTW). Got feedback? Join the conversation in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), or leave a comment below. **Actions**: * [@dmsnell](https://profiles.wordpress.org/dmsnell/) to create a Trac ticket and/ or Make/Core proposal to discuss introduction of `WP_HTML::tag()`. * [@dmsnell](https://profiles.wordpress.org/dmsnell/) to consider a future Make/ Core proposal for the [HTML API templating system](https://github.com/dmsnell/wordpress-develop/pull/12), and continued discussion around generating safe HTML. ## Forthcoming releases ### 6.4.3 [Conversation start link](https://wordpress.slack.com/archives/C02RQBWTW/p1706128902638939) * [@jorbin](https://profiles.wordpress.org/jorbin/) shared the remaining open tickets for this milestone, which are scheduled for review and commit prior to a Thursday( Jan 25) 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)](https://make.wordpress.org/core/author/ironprogrammer/?output_format=md#alpha-beta).: - [#60025](https://core.trac.wordpress.org/ticket/60025) – This needs additional review and testing. Any help is appreciated - [#59866](https://core.trac.wordpress.org/ticket/59866) – [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) and I have been work on the one and I should have an update in the next 12 hours. * [@joemcgill](https://profiles.wordpress.org/joemcgill/) requested help reviewing the approach proposed in [#5926 Cache locate template paths](https://github.com/WordPress/wordpress-develop/pull/5926), which would address both [#60025](https://core.trac.wordpress.org/ticket/60025) and [#60290](https://core.trac.wordpress.org/ticket/60290). ### 6.5 [Conversation start link](https://wordpress.slack.com/archives/C02RQBWTW/p1706129069306749) [See this section in the agenda](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#next-major-release-6-5) for updates, helpful links, and information for the 6.5 release. **Comments:** * [@oglekler](https://profiles.wordpress.org/oglekler/) pointed out that there are [several `early` 6.5 tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~early&milestone=6.5&col=id&col=summary&col=status&col=milestone&col=owner&col=type&col=priority&col=changetime&desc=1&order=changetime) that need attention, asking for review as some might have the potential to be completed in time 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.. * [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) indicated that the 6.5 cycle is past the “early part of alpha”, suggesting these may need to be punted if they truly require a long runway for soak time and discussion. * [@azaozz](https://profiles.wordpress.org/azaozz/) agreed that the `early` keyword indicates a need for comprehensive testing, and possible reconsideration of the milestone if the testing hasn’t occurred. He also suggested that while not required, it might be preferable to fix old/known bugs during alpha, and allow beta testers to focus on “new” bugs introduced from Beta 1 and onward. * [@jorbin](https://profiles.wordpress.org/jorbin/) suggested two interpretations of `early`; i.e. actually early in the alpha cycle, or just before Beta 1. * [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) noted that since Beta 1 is the 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.) milestone for enhancements/features, that in her perspective, `early` should apply to early in the alpha cycle. She cited changes to `WP_Query` as an example where `early` would apply. * [@afragen](https://profiles.wordpress.org/afragen/) observed that it doesn’t seem that many `early` tickets are committed early in the cycle. ## Open Floor * [@afragen](https://profiles.wordpress.org/afragen/) highlighted [#59448: is_wp_version_compatible works unreliably](https://core.trac.wordpress.org/ticket/59448) for additional review/attention. * [@swissspidy](https://profiles.wordpress.org/swissspidy/) shared that [#59656: Merge Performant Translations (Ginger MO)](https://core.trac.wordpress.org/ticket/59656)( [changeset 57337](https://core.trac.wordpress.org/changeset/57337)) has just been committed to `trunk`. [@azaozz](https://profiles.wordpress.org/azaozz/) asked if it could be highlighted in non-English sites/forums, and [@swissspidy](https://profiles.wordpress.org/swissspidy/) noted that it should be a pinned post topic during beta, and would raise it in the [#polyglots](https://wordpress.slack.com/archives/C02RP50LK) channel. [@webcommsat](https://profiles.wordpress.org/webcommsat/) also suggested referencing this update in the next polyglot newsletter. * In order to expand topics in the Contributor Mentorship Program, [@oglekler](https://profiles.wordpress.org/oglekler/) invited Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. [https://core.trac.wordpress.org](https://core.trac.wordpress.org) to share interesting and important ideas, tickets, and issues related to Core over in the [#contributor-mentorship](https://wordpress.slack.com/archives/C05FUD148LD) channel or via DM. _Props [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/) for peer review._ [#6-4](https://make.wordpress.org/core/tag/6-4/), [#6-5](https://make.wordpress.org/core/tag/6-5/), [#core](https://make.wordpress.org/core/tag/core/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 10:17 pm _on_ December 13, 2023 Tags: [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [dev chat ( 917 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 973 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat Summary, December 6, 2023](https://make.wordpress.org/core/2023/12/13/dev-chat-summary-december-6-2023/)󠁿 The WordPress Developers Chat meeting took place on [ 6 December 2023 at 20:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231206T2000) in [core](https://wordpress.slack.com/messages/core/) on [Make WordPress Slack](https://make.wordpress.org/chat/)( or [#core](https://matrix.to/#/#core:community.wordpress.org) in Matrix). ## Key info * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1701892836903139) of the Dev Chat on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), hosted by [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/). * Today’s [Dev Chat Agenda](https://make.wordpress.org/core/2023/12/05/dev-chat-agenda-december-6-2023/) was prepared by [@webcommsat](https://profiles.wordpress.org/webcommsat/). ## Announcements * [WordPress 6.4.2 Maintenance & Security Release](https://wordpress.org/news/2023/12/wordpress-6-4-2-maintenance-security-release/): 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. addresses a handful of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. bugs, as well as a preventive security update. Props to the minor release squad for getting this shipped! ## Highlighted Posts * [Recap: WordPress 6.4 “Shirley” Retrospective](https://make.wordpress.org/core/2023/12/05/recap-wordpress-6-4-shirley-retrospective/): Check out this summary of feedback received from the 6.4 retro post. * [Proposal: Default Theme Task Force for 2024](https://make.wordpress.org/core/2023/12/05/proposal-default-theme-task-force-for-2024/): Share your thoughts or step forward to join this effort in supporting default themes. * [Redesigning Developer Resources and a call for testing](https://make.wordpress.org/meta/2023/11/22/redesigning-developer-resources-and-a-call-for-testing/): Your feedback is requested to help move forward on improving the design and information flow for WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)’ s Dev Resources content. * Summary posts covering content from November 2023: [What’s new for Developers, November 2023](https://developer.wordpress.org/news/2023/11/whats-new-for-developers-november-2023/) and What’s New on [Learn WordPress, November 2023 edition](https://make.wordpress.org/updates/2023/12/01/whats-new-on-learn-wordpress-in-november-2023/). More developer-focused posts are available on the [Developer Blog](https://developer.wordpress.org/news/). The next editorial meeting has been moved to December 14, 2023, 13:00 UTC in the [#core-dev-blog](https://wordpress.slack.com/archives/C03RL47B3S8) channel on Slack. * [Hallway Hangout: Performance End of Year Review 2023](https://make.wordpress.org/core/2023/11/30/hallway-hangout-performance-end-of-year-review-2023/): Hop into this hallway hangout _tomorrow, December 7_ to celebrate accomplishments this year, and for a peek at what’s coming in 2024. * [Create Tours for Make P2s](https://make.wordpress.org/meta/2023/11/29/create-tours-for-make-p2s/): All team blogs have this 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. activated…how can your team use it? * [Nominations for 2024 edition, core team reps](https://make.wordpress.org/core/2023/12/04/nominations-for-core-team-reps-2024-edition/)– nominations open until December 14! * [Core Team update, December 4, 2023](https://make.wordpress.org/updates/2023/12/05/core-team-update-december-4-2023/): See this post for a team status update. ## Editor Updates [@annezazu](https://profiles.wordpress.org/annezazu/) has graciously shared this week’s [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7) update, found here: [https://make.wordpress.org/core/2023/12/05/dev-chat-agenda-december-6-2023/#comment-45924](https://make.wordpress.org/core/2023/12/05/dev-chat-agenda-december-6-2023/#comment-45924) * Coming to 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/](https://wordpress.org/gutenberg/) 17.3, [you can explore partially synced patterns behind an experimental flag](https://github.com/WordPress/gutenberg/pull/56235) by enabling the “Connections” experiment when the time comes. * Efforts continue to [align post and site editor features](https://github.com/WordPress/gutenberg/issues/52632#issuecomment-1836150176) with some [behind the scenes work](https://github.com/WordPress/gutenberg/pull/56671) done to have the canvas of the site editor and post editor under a unique component. * New tracking issue for a [public 1.0 version of the interactivity API](https://github.com/WordPress/gutenberg/issues/56803). * [Progress update](https://github.com/WordPress/gutenberg/pull/55657#issuecomment-1840710183) on having the navigation overlay as a separate template part that can be individually customized. * PR to [Add layout classes to legacy Group inner container](https://github.com/WordPress/gutenberg/pull/56130) merged (requires a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 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.) as part of an overall effort to bring appearance tools to classic themes. * Various improvements to the data views work including support for [NOT IN operator as a way to filter](https://github.com/WordPress/gutenberg/pull/56479), [a way to filter by template author](https://github.com/WordPress/gutenberg/pull/56338) allowing you to see templates provided by plugins more readily, and a [grid view for templates with a preview of the templates listed](https://github.com/WordPress/gutenberg/pull/56382). This is all behind an experimental flag in Gutenberg > Experiments > “New adminadmin( and super admin) views”. * The 6.5 roadmap is slated to ship this week barring any last minute feedback. ## Release Updates ### Next minor release: 6.4.3 [@jorbin](https://profiles.wordpress.org/jorbin/) indicated that work is underway to put a squad together for this release. 👉🏻 Volunteers interested in helping on the 6.4.3 minor release should drop a note in [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N). ### Next 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 Some helpful links: * [Development cycle page](https://make.wordpress.org/core/6-5/). * [WordPress 6.5 Editor Tasks board is out](https://github.com/orgs/WordPress/projects/148). * [A 6.5 roadmap draft has been shared](https://wordpress.slack.com/archives/C065MBW03EH/p1701192564792069) in [#6-5-release-leads](https://wordpress.slack.com/archives/C065MBW03EH) and work is underway to gather remaining information. * ⏰ Reminder [Hallway Hangout](https://make.wordpress.org/core/2023/11/23/hallway-hangout-lets-explore-wordpress-6-5/) on exploring 6.5 will take place on [Tuesday, January 16, 2024 at 01:00 PM PST](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240116T2100). Are you able to help with future 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? [Bug scrubs](https://make.wordpress.org/core/2023/11/14/bug-scrub-schedule-for-wordpress-6-5/) post. Next scrub: [ December 19, 2023 at 19:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231219T1900) in the [#core](https://wordpress.slack.com/messages/core/) Slack channel. ## Component Maintainer Updates ### Disable autoload for large options [@flixos90](https://profiles.wordpress.org/flixos90/) requested a second opinion and general feedback on the approach envisioned in [https://core.trac.wordpress.org/ticket/42441](https://core.trac.wordpress.org/ticket/42441). In order to differentiate between whether an `autoload` value for an option was set as a default or explicitly chosen, it is proposed to add new possible values for that database column. For additional context, [comment:20](https://core.trac.wordpress.org/ticket/42441#comment:20) may be helpful, and [a PR implementation](https://github.com/WordPress/wordpress-develop/pull/5671) already exists. While personally supportive of the effort, Felix added that such a change will require 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 plugins specifically focused on autoloading may need to cater for the change. It was clarified that only plugins that _enhance_ autoloading specifically should be affected. [@azaozz](https://profiles.wordpress.org/azaozz/) agreed that this approach was sound, and should be fully backwards compatible. Additional discussion moved to [the Trac ticket](https://core.trac.wordpress.org/ticket/42441). ## Open Floor ### Core version displayed on Updates page From the [agenda comments](https://make.wordpress.org/core/2023/12/05/dev-chat-agenda-december-6-2023/), [@shenyanzhi](https://profiles.wordpress.org/shenyanzhi/) wished to draw attention to [https://core.trac.wordpress.org/ticket/40241](https://core.trac.wordpress.org/ticket/40241). It was suggested to raise the ticketticket Created for both bug reports and feature development on the bug tracker. over in [#core-upgrade-install](https://wordpress.slack.com/archives/CULBN711P) for additional feedback, and for contributors to leave a comment on the ticket or dev chat post comments. ### Disable the `WordPress-Docs` ruleset in Gutenberg Also from the agenda comments, [@antonvlasenko](https://profiles.wordpress.org/antonvlasenko/) asked for feedback on a [proposal (GB 56487)](https://github.com/WordPress/gutenberg/issues/56487) to [temporarily] disable the `WordPress-Docs` ruleset from Gutenberg. Core doesn’t use these rules, so this change would simplify the backporting process from Core, improving parity between the repos. Feedback on the issue or accompanying PR is greatly appreciated. ## Next Meeting The next meeting will be on [ 13 December 2023 at 20:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231213T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the next meeting! _Props [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) for peer review, and [@webcommsat](https://profiles.wordpress.org/webcommsat/) for essential meeting preparation work._ [#6-4](https://make.wordpress.org/core/tag/6-4/), [#6-5](https://make.wordpress.org/core/tag/6-5/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 10:18 am _on_ November 17, 2023 Tags: [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [dev chat ( 917 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 973 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat Summary, November 15, 2023](https://make.wordpress.org/core/2023/11/17/dev-chat-summary-november-15-2023/)󠁿 The WordPress Developers Chat meeting took place on [Wednesday, November 15, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231115T2000) in [core](https://wordpress.slack.com/messages/core/) on [Make WordPress Slack](https://make.wordpress.org/chat/)( or [#core](https://matrix.to/#/#core:community.wordpress.org) in Matrix). ## Key info * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1700078412796729) of the Dev Chat on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), hosted by [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/). * Today’s [Dev Chat Agenda](https://make.wordpress.org/core/2023/11/14/dev-chat-agenda-november-15-2023/) was prepared by [@webcommsat](https://profiles.wordpress.org/webcommsat/). ## Announcements 🎉 [WordPress 6.4.1 is out!](https://wordpress.org/news/2023/11/wordpress-6-4-1-maintenance-release/): Thank you to every single person who has been involved and continues to contribute to 6.4! (Also see the [original release post](https://wordpress.org/news/2023/11/shirley/).) _Additional background information on the release:_ * [Overview of technical details and timeline for the rapid maintenance release 6.4.1](https://make.wordpress.org/core/2023/11/10/wordpress-6-4-1-rapid-maintenance-release-technical-details-and-timeline/)( props [@desrosj](https://profiles.wordpress.org/desrosj/)). Update comment on [number of installs of 6.4 now running 6.4.1](https://make.wordpress.org/core/2023/11/10/wordpress-6-4-1-rapid-maintenance-release-technical-details-and-timeline/#comment-45843). * To safeguard against future related issues, contributors are [exploring ways to better test against different versions of curl](https://core.trac.wordpress.org/ticket/59844). It is always strongly recommended to run current and supported versions of all software. * Hosting companies and interested contributors are encouraged to join the [distributed testing program](https://make.wordpress.org/hosting/test-results-getting-started/) where anyone can get involved with and report the results of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. automated test suite back to WordPress. ## Highlighted Posts * [What’s new in Gutenberg 17.0?](https://make.wordpress.org/core/2023/11/10/whats-new-in-gutenberg-17-0-9-november/): Get the scoop on what’s new, and try it out for yourself. * [WordPress 6.4 performance improvements](https://make.wordpress.org/core/2023/11/13/wordpress-6-4-performance-improvements/)( to be added 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](https://make.wordpress.org/core/handbook/about/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.). * Also check out [@swissspidy](https://profiles.wordpress.org/swissspidy/)‘s personal blogblog (versus network, site) post on [getting started with performance testing](https://pascalbirchler.com/wordpress-performance-testing/). * 👀 See this update to the Field Guide: [Main query loop handling for block themes in 6.4](https://make.wordpress.org/core/2023/11/13/main-query-loop-handling-for-block-themes-in-6-4/). * [Update to the core commit message format](https://make.wordpress.org/core/2023/11/10/an-update-to-the-core-commit-message-format/): It has been updated to take into account 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. and follow up commits. There is also a change on where “props” is used in the commit message. * 📣 Call for help on outstanding [6.4 End User documentation](https://make.wordpress.org/docs/2023/10/25/call-for-volunteers-to-help-with-6-4-end-user-documentation/#comment-40466)( HelpHub). Please see the [documentation tracker on GitHub for 6.4 end users](https://github.com/orgs/WordPress/projects/141/views/2). 🙏 > @webcommsat emphasized that developers with 6.4 knowledge can really help with > reviews and contributions toward End User docs. The sooner the documentation is > published, the sooner it can benefit the community. _And some items from last week’s cancelled chat to touch on:_ * [A proposed schedule for 2024 major releases](https://make.wordpress.org/core/2023/11/06/proposal-2024-major-release-timing/) has been shared by [@chanthaboune](https://profiles.wordpress.org/chanthaboune/), proposing dates for 6.5, 6.6, and 6.7. Please share your thoughts on timing, focus, or anything else relates to these releases in the post comments. > @jeffpaul called on potential 6.5/6.6/6.7 leads to share their thoughts on this > post. * [Accessibility improvements in the 6.4 release](https://make.wordpress.org/core/2023/11/03/wordpress-6-4-accessibility-improvements/): Check out this rundown of 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) items addressed in 6.4. * [Proposal to discontinue the weekly #core-editor meetings](https://make.wordpress.org/core/2023/11/07/proposal-cancel-core-editor-chat/): Add your thoughts about this change, and opportunities to incorporate editor discussions in Dev Chat. * [Shareable performance testing utils](https://github.com/WordPress/gutenberg/issues/55852): Join the discussion to explore ways that projects can incorporate performance testing as part of their development workflow. And finally, some reminders ⏲️: * [Call for 6.4.x Release Managers](https://make.wordpress.org/core/2023/10/30/call-for-6-4-x-release-managers/): Work on improving 6.4 continues after the main release, so please consider joining the 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. squad to help keep 6.4 healthy. * [Call for volunteers to help with 6.4 end-user documentation](https://make.wordpress.org/docs/2023/10/25/call-for-volunteers-to-help-with-6-4-end-user-documentation/): The Docs team is looking for volunteers to revise end-user docs (HelpHub) for 6.4. Check out the post and learn how to pitch in! Wait…did I mention this already? Yep — but it’s so important for our user community ❤️. ## Release Updates ### Next minor release: 6.4.2 [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) noted that if minor release squad volunteers can be found soon, that there’s a possibility of shipping a 6.4.2 minor release before year’s end. He requested feedback on whether there are any urgent/important items that need to be addressed soon. [@jorbin](https://profiles.wordpress.org/jorbin/) has been watching the [(6.4) minor release issues report](https://core.trac.wordpress.org/tickets/minor), and noted that [#59847](https://core.trac.wordpress.org/ticket/59847) seems the most urgent. He also pointed out nice-to-have editor package backports in [#59828](https://core.trac.wordpress.org/ticket/59828). If volunteers can be found to support the release, then he suggested a target of the week of November 27, 2023. [@joemcgill](https://profiles.wordpress.org/joemcgill/) noted that [#59847](https://core.trac.wordpress.org/ticket/59847) is nearly ready, and requested feedback on the related PR. 👉🏻 Volunteers who can help with the 6.4.2 minor release (and determine timing) should drop a note in [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N). ### Next 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 * The [development cycle page](https://make.wordpress.org/core/6-5/) has been created. It will be populated after discussing release timings and the finalization of the squad. * Are you able to help with future 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? [Check out the 6.5 scrub schedule.](https://make.wordpress.org/core/2023/11/14/bug-scrub-schedule-for-wordpress-6-5/) * And keep tabs on the [#6-5-release-leads](https://wordpress.slack.com/archives/C065MBW03EH) channel for additional updates. [@jorbin](https://profiles.wordpress.org/jorbin/) asked that 6.5 ticketticket Created for both bug reports and feature development on the bug tracker. scrub participants keep an eye out for regressions that should be moved to the 6.4.2 milestone, to get fixes delivered to users more quickly. [@webcommsat](https://profiles.wordpress.org/webcommsat/) shared a link to [the November 14 scrub](https://wordpress.slack.com/archives/C02RQBWTW/p1699987986081639) for anyone looking at tickets async, and called on contributors to help with patches and writing of tests. 🙏🏻 ## Open Floor ### Proposal to Cancel `#core-editor` Meetings _(This discussion [started during highlights](https://wordpress.slack.com/archives/C02RQBWTW/p1700079699829069) with regards to [this proposal](https://make.wordpress.org/core/2023/11/07/proposal-cancel-core-editor-chat/), and is shared here for readability.)_ [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) expressed worry about losing touch with 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/](https://wordpress.org/gutenberg/) development without regular meetings and sought alternative ways to stay updated. [@jorbin](https://profiles.wordpress.org/jorbin/) suggested incorporating editor updates into existing meetings, particularly emphasizing involvement from major release editor leads. [@webcommsat](https://profiles.wordpress.org/webcommsat/) highlighted the usefulness of core-editor summaries and proposed integrating regular updates into the dev chat agenda. [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) raised the question of where the editor summary would originate if the meetings themselves were cancelled. [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) suggested obtaining editor updates during dev chat to ensure communication of updates and blockers across the project. The idea of carving out an official “editor updates” section in dev chat was considered, and [@jorbin](https://profiles.wordpress.org/jorbin/) suggested seeking volunteers from the [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7) channel to participate in the chat. [@annezazu](https://profiles.wordpress.org/annezazu/) volunteered to take on the responsibility and discussed potential ways to share editor updates, including during the meeting or through agenda posts. The need for asynchronous options, given different time zones, was acknowledged. [@webcommsat](https://profiles.wordpress.org/webcommsat/) suggested having a dedicated section for editor updates on the dev chat agenda post, and plan for asynchronous sharing. [@annezazu](https://profiles.wordpress.org/annezazu/) volunteered to make the meetings and incorporate asynchronous sharing, considering her near term availability across time zones. The importance of avoiding disruptions during meetings was discussed, as was the possibility of maintaining `#core-editor` office hours for specific questions related to the editor. ### 2024 Core Team Reps Nominations [@webcommsat](https://profiles.wordpress.org/webcommsat/) gave a reminder for `# core` contributors to have a look at the draft post: [Nominations for Core Team Reps: 2024 Edition](https://make.wordpress.org/core/?p=107497&preview=1&_ppp=b254869bc1). The dates/timing may need revising, and team reps are looking into the possibility of having the voting poll embedded into the post to make it easier to vote. Please share your feedback in [#core](https://wordpress.slack.com/archives/C02RQBWTW) and CC [@webcommsat](https://profiles.wordpress.org/webcommsat/) and [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/). ### WordPress 6.4 Retrospective [@cbringmann](https://profiles.wordpress.org/cbringmann/) shared [WordPress 6.4 Retrospective](https://wp.me/p2AvED-sxC), and asked that anyone who has contributed to the release to reflect and share their thoughts on the release process (instructions in the post). A follow-up post will be published in December. ## Next Meeting The next meeting will be on [ 22 November 2023 at 20:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231122T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the next meeting! _Props [@webcommsat](https://profiles.wordpress.org/webcommsat/) for collaboration on this post and meeting preparation._ [#6-4](https://make.wordpress.org/core/tag/6-4/), [#6-5](https://make.wordpress.org/core/tag/6-5/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 11:44 pm _on_ October 18, 2023 Tags: [6-3 ( 70 )](https://make.wordpress.org/core/tag/6-3/), [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [dev chat ( 917 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 973 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat Summary, October 18, 2023](https://make.wordpress.org/core/2023/10/18/dev-chat-summary-october-18-2023/)󠁿 The WordPress Developers Chat meeting took place on [October 18, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231018T2000) in the [core](https://wordpress.slack.com/messages/core/) channel of [Make WordPress Slack](https://make.wordpress.org/chat/). ## Key Links * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1692216005854449) of the Dev Chat on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), hosted by [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/). ## Announcements * [WordPress 6.4 Release Candidate 1](https://wordpress.org/news/2023/10/wordpress-6-4-release-candidate-1/): Download the latest 6.4 build and don’t forget [this handy reference guide](https://make.wordpress.org/test/2023/09/26/help-test-wordpress-6-4/) for testing the latest features. ## Highlighted Posts * [WordPress 6.4 Release Candidate Phase](https://make.wordpress.org/core/2023/10/17/wordpress-6-4-release-candidate-phase/): Learn or refresh your knowledge of what happens during 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)](https://make.wordpress.org/core/author/ironprogrammer/?output_format=md#alpha-beta).. Questions? Please post them in [the comments](https://make.wordpress.org/core/2023/10/17/wordpress-6-4-release-candidate-phase/). * [6.4 Dev Notes](https://make.wordpress.org/core/tag/dev-notes-6-4/): It’s been a busy time in the Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site)! Stay updated on the latest technical updates by checking out posts conveniently tagged with [#dev-notes-6-4](https://make.wordpress.org/core/tag/dev-notes-6-4/). _Major props_ to 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. authors and wranglers who have worked tirelessly to make this happen! 🎉 * [WordPress core is now using Playwright for all browser-based tests](https://make.wordpress.org/core/2023/10/16/wordpress-core-is-now-using-playwright-for-all-browser-based-tests/): e2e fans rejoice! This milestone promises improved test stability and better options for authoring tests. If you’ve been holding back while the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. from Puppeteer to Playwright has been underway, now is a great time to jump back in to improve Core e2e coverage. * [What’s new in Gutenberg 16.8 (11 October)](https://make.wordpress.org/core/2023/10/11/whats-new-in-gutenberg-16-8-11-october/): Check out updates to the Cover 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., Font Library, and more in this roundup of the latest release. ## Release Updates ### WordPress 6.4 **RC 2 is scheduled for next Tuesday, October 24, 2023.** Stay in the loopLoop 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](https://codex.wordpress.org/The_Loop) with 6.4 by following: * [WordPress 6.4 Development Cycle](https://make.wordpress.org/core/6-4/) * [Roadmap to 6.4](https://make.wordpress.org/core/2023/08/22/roadmap-to-6-4/) — this next 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. is scheduled for November 7, 2023 * [Testing WordPress 6.4](https://make.wordpress.org/test/2023/09/26/help-test-wordpress-6-4/)— a detailed guide for testing new and refined features * [6.4 Editor tasks board](https://github.com/orgs/WordPress/projects/127) * [Release parties schedule for 6.4](https://make.wordpress.org/core/2023/08/29/6-4-release-parties-schedule-and-hosts/) * [Bug Scrub Schedule 6.4](https://make.wordpress.org/core/2023/08/17/bug-scrub-schedule-for-wordpress-6-4/) ✅ (current schedule is complete) * and following along in the [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N) channel Additional release updates from the floor included: * [A question was raised](https://wordpress.slack.com/archives/C055Y7FKS7N/p1697651668430749) in [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N) about removing some 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/](https://wordpress.org/gutenberg/)- only packages from the next npm package update to Core. * Some 6.4 dev notesdev 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. drafts are still needed for a couple of areas, so [a gentle reminder was raised](https://wordpress.slack.com/archives/C02RQBWTW/p1697660898273199) to keep the official [6.4 Documentation Tracker](https://github.com/orgs/WordPress/projects/141) updated with latest progress. Reach out on the Tracker for help or to the Documentation release group in the [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N) channel. ## WordPress 6.3.2 * [WordPress 6.3.2 – Maintenance and Security release](https://wordpress.org/news/2023/10/wordpress-6-3-2-maintenance-and-security-release/): This follow-up to 6.3.1 introduces several 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 security updates. Make sure to update! * Keep tabs on the [#6-3-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ) channel for future updates. ## Open Floor ### Automated Welcome/Signposting for 󠀁[#core](https://wordpress.slack.com/archives/C02RQBWTW)󠁿 [@webcommsat](https://profiles.wordpress.org/webcommsat/) [asked](https://wordpress.slack.com/archives/C02RQBWTW/p1697661423730869) if Core would consider utilizing an automated messaging/workflow tool similar to that used by Training. When users joined the channel, they would receive a private message from Slackbot that includes channel-specific info and links, such as the Dev Chat schedule, or orientation for new contributors and contributor days. Abha agreed to draft a proposal to seek broader input from Core and new contributors. ### Use of `noopener noreferrer` in New Window/Tab Links [@presskopp](https://profiles.wordpress.org/presskopp/) [had a question](https://wordpress.slack.com/archives/C02RQBWTW/p1697661466210439) regarding use of `rel="noopener noreferrer"` in links with `target="_blank"`, which were [supposed to have been removed](https://core.trac.wordpress.org/ticket/49558). To help resolve instances where this unneeded behavior remains (in Core and Gutenberg), contribute to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. [#53843: Remove adding of rel=”noopener” to links with target=”_blank”](https://core.trac.wordpress.org/ticket/53843). ## Next Meeting The next meeting will be on [October 25, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231025T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the [`#core` Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). _Props _[@webcommsat](https://profiles.wordpress.org/webcommsat/)_ for peer review of this post._ [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-4](https://make.wordpress.org/core/tag/6-4/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 6:27 pm _on_ August 17, 2023 Tags: [6-3 ( 70 )](https://make.wordpress.org/core/tag/6-3/), [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [dev chat ( 917 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 973 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat Summary, August 16, 2023](https://make.wordpress.org/core/2023/08/17/dev-chat-summary-august-16-2023/)󠁿 The WordPress Developers Chat meeting took place on [August 2, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230802T2000) in the [core](https://wordpress.slack.com/messages/core/) channel of [Make WordPress Slack](https://make.wordpress.org/chat/). ## Key Links * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1692216005854449) of the Dev Chat on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), hosted by [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/). * Today’s agenda: [Dev Chat agenda, August 16, 2023](https://make.wordpress.org/core/2023/08/15/dev-chat-agenda-august-16-2023/), courtesy [@webcommsat](https://profiles.wordpress.org/webcommsat/). ## Highlighted Posts * [Two Weeks in Core – August 14, 2023](https://make.wordpress.org/core/2023/08/16/a-week-in-core-august-14-2023/)— Thank you, [@audrasjb](https://profiles.wordpress.org/audrasjb/), for these updates! > Here’s an overview of what’s happened in TracTrac An open source project by Edgewall > Software that serves as a bug tracker and project management tool for WordPress. > between July 31 and August 14, 2023: > * 40 commits > * 50 contributors > * 164 tickets created > * 15 tickets reopened > * 138 tickets closed > * _and 5 new contributors in this period_ ❤️ * [Status update on the Interactivity API](https://make.wordpress.org/core/2023/08/15/status-update-on-the-interactivity-api/): Get the latest updates on this proposal and where to track its progress. This post also includes info on valuable learning resources so you can dive in and explore the 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.’s possibilities. * [What’s new for developers? (August 2023)](https://developer.wordpress.org/news/2023/08/whats-new-for-developers-august-2023/): Do “new shiny objects”, “bag of goodies”, and “kid in a toy shop” spark your interest? Thought so! Check out the newest stuff in 6.3 and 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/](https://wordpress.org/gutenberg/) in this latest post on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)’ s own Developer Blogblog (versus network, site). * [What’s new in Gutenberg 16.4](https://make.wordpress.org/core/2023/08/10/whats-new-in-gutenberg-16-4-9-august/): _Inside:_ A new progress bar component, updates to the Command Palette and Footnotes 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., and auto-inserting blocks are highlighted in the latest 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. release. * ⏰ Reminder: Share your comments on the [ticket ownership discussion](https://make.wordpress.org/core/2023/08/01/whose-ticket-is-it-anyway/) by **September 1, 2023**. ## Release Updates ### WordPress 6.3 * See the [WordPress 6.3 developer notes](https://make.wordpress.org/core/tag/dev-notes+6-3/). 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](https://make.wordpress.org/core/handbook/about/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. has had 6,500 views since it was published on July 18! ### WordPress 6.3.1 * There are some [urgent fixes](https://github.com/WordPress/gutenberg/commits/wp/6.3) that have been identified for a quick turnaround 6.3.1 release, but as of this writing, timing is still being decided. For the latest updates, follow discussions in the [#6-3-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ) channel. ### WordPress 6.4 Stay in the loopLoop 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](https://codex.wordpress.org/The_Loop) with 6.4 by checking out: * [WordPress 6.4 Development Cycle](https://make.wordpress.org/core/6-4/) hub * [6.4 Editor tasks board](https://github.com/orgs/WordPress/projects/127) * and following along in the [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N) channel ## Maintainers: Component Help Requests ### Rollback Auto Updates – Part 3 The [Rollback Update Failure](https://wordpress.org/plugins/rollback-update-failure/) plugin has received several recent updates, and is awaiting security audit and additional feedback. ### Plugin Dependencies [Plugin dependencies (Trac #22316)](https://core.trac.wordpress.org/ticket/22316) has been updated with the latest round of feedback, and is ready for commit consideration. [Trac #59112](https://core.trac.wordpress.org/ticket/59112) has been created to encompass remaining design input for this feature, which could be incorporated during the feature’s merge to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. ## Open Floor ### WCUS 2023 Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of 󠀁[https://make.wordpress.org/](https://make.wordpress.org/)󠁿 There are many teams that people can participate in, each with a different focus. 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)󠁿 #### Make/Core Post 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](https://central.wordcamp.org/about/). US [Contributor Day](https://us.wordcamp.org/2023/contributor-day/) is next week! There is a Core blog [draft](https://make.wordpress.org/core/?p=107443&preview=1&_ppp=53874734a0) underway that aims to promote and provide info to new contributors ahead of the event. The post is to be finalized after Dev Chat, and it is requested that Core community members provide feedback in the [#core channel](https://wordpress.slack.com/archives/C02RQBWTW). Core Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. [@webcommsat](https://profiles.wordpress.org/webcommsat/) is collating details for the event. #### Volunteers Needed Volunteers are needed to help facilitate _**in person at tables** and **remotely on Slack**_ during Contributor[ Day](https://us.wordcamp.org/2023/contributor-day/). Contributors are asked to raise their hand in Slack, or add their name and level of participation in the post comments. A handful of chat attendees raised their hands to help attend to Core tables throughout the day, as well as help remote attendees in Slack, but there are still no clear Core table leads. #### Ticketticket Created for both bug reports and feature development on the bug tracker. Focus There was a question about whether “ancient” Trac tickets should be a point of focus during Contributor Day, and there was general agreement that `good-first-bug` tickets were likely better candidates to focus on, given the limited time and resources available at the event. New contributors to Core are encouraged to set up their local environments in advance of WCUS, and to join the next New Core Contributor meeting on **[2023-08-23 at 19:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230823T1900)** in the [#core](https://wordpress.slack.com/archives/C02RQBWTW) channel. ### Fields API A status update was provided for the [WordPress Fields API](https://github.com/sc0ttkclark/wordpress-fields-api), with a Make/Core post to come later this week. Those interested in this project are invited to help with [project research](https://github.com/sc0ttkclark/wordpress-fields-api/blob/develop/docs/research.md), stop on by and chat with [@sc0ttkclark](https://profiles.wordpress.org/sc0ttkclark/) at WCUS, and to join the conversation over in the [#core-fields channel](https://wordpress.slack.com/archives/C04MWK7PZ). ### 6.4 Scrub Schedule The 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 schedule is still being finalized, but the first session is to take place on [2023-08-17 at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230817T1700) in [#core](https://wordpress.slack.com/archives/C02RQBWTW). All are welcome to join the scrub! ## Next Meeting The next meeting will be on [August 23, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230823T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the [`#core` Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). _Props [@afragen](https://profiles.wordpress.org/afragen/) for peer review of this post._ [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-4](https://make.wordpress.org/core/tag/6-4/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 7:44 pm _on_ August 5, 2023 Tags: [6-3 ( 70 )](https://make.wordpress.org/core/tag/6-3/), [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [dev chat ( 917 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 973 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat Summary, August 2, 2023](https://make.wordpress.org/core/2023/08/05/dev-chat-summary-august-2-2023/)󠁿 The WordPress Developers Chat meeting took place on [August 2, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230802T2000) in the [core](https://wordpress.slack.com/messages/core/) channel of [Make WordPress Slack](https://make.wordpress.org/chat/). ## Key Links * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1691006403956369) of the Dev Chat on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), hosted by [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/). * Today’s agenda: [Dev Chat agenda, August 2, 2023](https://make.wordpress.org/core/2023/08/01/dev-chat-agenda-august-1-2023/), courtesy [@webcommsat](https://profiles.wordpress.org/webcommsat/). ## Announcements * [6.3 RC3 was released](https://wordpress.org/news/2023/08/wordpress-6-3-rc3/) yesterday and is available for testing. * [WordPress 6.3 Release Day Process](https://make.wordpress.org/core/2023/08/01/wordpress-6-3-release-day-process/): Shares the current plan and what will happen during each phase, as well as tips and guidance on where contributors can help. * The [WordPress 6.3](https://make.wordpress.org/core/6-3/) General Release is planned for next week, **Tuesday, 8 August 2023**. ## Highlighted Posts * [A Week in Core – July 31, 2023](https://make.wordpress.org/core/2023/08/01/a-week-in-core-july-31-2023/)— Thank you, [@audrasjb](https://profiles.wordpress.org/audrasjb/)! > Here’s an overview of updates in TracTrac An open source project by Edgewall Software > that serves as a bug tracker and project management tool for WordPress. between > July 24 and July 31, 2023: > * 21 commits > * 40 contributors > * 64 tickets created > * 12 tickets reopened > * 39 tickets closed * [Synced Patterns: The Evolution of Reusable Blocks](https://wordpress.org/news/2023/07/synced-patterns-the-evolution-of-reusable-blocks/): New pattern functionality with WordPress 6.3. * [Whose ticket is it, anyway?](https://make.wordpress.org/core/2023/08/01/whose-ticket-is-it-anyway/): Follow-up post to last week’s DevChat discussion about ticketticket Created for both bug reports and feature development on the bug tracker. ownership. Share your thoughts and opinions by **September 1, 2023**. * [Proposal: improve the editor tech workflow for major releases](https://make.wordpress.org/core/2023/08/01/proposal-improve-the-editor-tech-workflow-for-major-releases/): Ideas for improvements to ease the pain points of merging code from 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/](https://wordpress.org/gutenberg/) into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., particularly before 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. This proposal has already generated a lot of favorable consensus to experiment with this approach in the 6.4 cycle. * This proposal has been adopted: [Proposal: Criteria for Removing “Beta Support” from Each PHP 8+ Version](https://make.wordpress.org/core/2023/06/20/proposal-criteria-for-removing-beta-support-from-each-php-8-version/). Involved contributors are currently in the process of: - working through the action items list. - evaluating the list of incompatibilities for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.0 and 8.1 for WordPress 6.3. ## Release Updates ### WordPress 6.3 [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) asked if [Trac #58940 – site-health.php page Fatal error on version: 6.3-RC2](https://core.trac.wordpress.org/ticket/58940) would require 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)](https://make.wordpress.org/core/author/ironprogrammer/?output_format=md#alpha-beta). release. It was confirmed that the ticket was opened before RC 3, but not fixed in that release. [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) and [@audrasjb](https://profiles.wordpress.org/audrasjb/) agreed that another RC may be warranted, and would check other tickets that remain in the 6.3 [milestone](https://core.trac.wordpress.org/tickets/major) (or same query [grouped by workflow](https://core.trac.wordpress.org/tickets/major/workflow)). ### WordPress 6.4 [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) indicated that work was underway on [6.4 `early` tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~early&milestone=6.4&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority). [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) noted that wishlist items were being gathered, and that 6.4 release coordinators would be able to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. these earlier than is typical, since the 6.4 release cycle is shorter than normal. Of particular note was consideration of items requiring additional dev, design, or 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) attention before committing them to the release. ## Maintainers: Component Help Requests [@craigfrancis](https://profiles.wordpress.org/craigfrancis/) asked for attention on [Trac #54042 – Extending wpdb::prepare() to support IN() operator](https://core.trac.wordpress.org/ticket/54042), and consideration for 6.4 `early` designation. He asked for review and thoughts/ suggestions on improving the existing patches. ## Open Floor ### Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of 󠀁[https://make.wordpress.org/](https://make.wordpress.org/)󠁿 There are many teams that people can participate in, each with a different focus. 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)󠁿 Core/Core-* Tables [@desrosj](https://profiles.wordpress.org/desrosj/) related questions he’d received regarding how Core tables are often spread out at Contributor Day, which can be confusing for both new and experienced Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. [https://core.trac.wordpress.org](https://core.trac.wordpress.org) who wish to move between tables, especially for collaboration with other focus teams. [@webcommsat](https://profiles.wordpress.org/webcommsat/) agreed that it would be beneficial to locate them closely together, to avoid the issue of contributors getting confused and dropping out of the event. [@desrosj](https://profiles.wordpress.org/desrosj/) also asked if there were any volunteers from the [#core-performance](https://wordpress.slack.com/archives/C02KGN5K076) and [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7) channels who would be willing to lead their respective tables at WCUS. [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) suggested posing the question to each team’s Slack channel. [@joemcgill](https://profiles.wordpress.org/joemcgill/) raised his hand for helping at the Core Performance table. ### PHP 8.3 [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) shared that initial impressions concerning PHP 8.3 are that it would have a low impact to Core. PHP 8.3’s release date is scheduled for November 23, 2023. ## Next Meeting The next meeting will be on [August 9, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230809T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the [`#core` Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-4](https://make.wordpress.org/core/tag/6-4/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 10:23 pm _on_ May 24, 2023 Tags: [6-3 ( 70 )](https://make.wordpress.org/core/tag/6-3/), [6.2.2 ( 2 )](https://make.wordpress.org/core/tag/6-2-2/), [dev chat ( 917 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 973 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat Summary, May 24, 2023](https://make.wordpress.org/core/2023/05/24/dev-chat-summary-may-24-2023/)󠁿 The WordPress Developers Chat meeting took place on [May 24, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230524T2000) in the [core](https://wordpress.slack.com/messages/core/) channel of [Make WordPress Slack](https://make.wordpress.org/chat/). ## Key Links * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1684958417000799) of the Dev Chat on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). * Today’s agenda: [Dev Chat Agenda, May 24, 2023](https://make.wordpress.org/core/2023/05/23/dev-chat-agenda-may-24-2023/), courtesy [@webcommsat](https://profiles.wordpress.org/webcommsat/). * Last meeting summary: [Dev Chat Summary, May 17, 2023](https://make.wordpress.org/core/2023/05/19/dev-chat-summary-may-17-2023/). ## Announcements * [WordPress 6.2.2 Security Release](https://wordpress.org/news/2023/05/wordpress-6-2-2-security-release/): This rapid-response security release addresses a shortcodes regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/author/ironprogrammer/?output_format=md#blocker). 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. from 6.2.1, and further improves security around this feature. * [What’s new in Gutenberg 15.8](https://make.wordpress.org/core/2023/05/20/whats-new-in-gutenberg-15-8-may-17/): Get the latest scoop on what’s recently shipped in 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/](https://wordpress.org/gutenberg/). Posted by [@fabiankaegy](https://profiles.wordpress.org/fabiankaegy/) 🎉 * …which means that [Gutenberg 15.8 is available for download.](https://wordpress.org/plugins/gutenberg/) ## Highlighted Posts * [A Week in Core – May 22, 2023](https://make.wordpress.org/core/2023/05/24/a-week-in-core-may-22-2023/)— Thank you, [@audrasjb](https://profiles.wordpress.org/audrasjb/)! > Here’s an overview of updates in TracTrac An open source project by Edgewall Software > that serves as a bug tracker and project management tool for WordPress. between > May 8 and May 22, 2023 — yep, that’s “Two Weeks in CoreCore Core is the set of > software required to run WordPress. The Core Development Team builds WordPress.”: > * 48 commits > * 87 contributors > * 108 tickets created > * 10 tickets reopened > * 79 tickets closed > * 🥁 and **5 new contributors** in this period 🎉 * [WP Briefing: Episode 56: What to Know About WordPress Playground](https://wordpress.org/news/2023/05/episode-56-what-to-know-about-wordpress-playground/): Learn more about experiments surrounding the ever-growing WordPress Playground, and what coding and testing 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) opportunities this exciting project is making possible. * [Core Editor Improvement: Smoother Site Editing](https://make.wordpress.org/core/2023/05/22/core-editor-improvement-smoother-site-editing/): See some of the latest updates to the editor, including 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. history for styles, templates, and template parts. ## Release Updates * [WordPress 6.3 Planning Roundup](https://make.wordpress.org/core/2023/05/18/wordpress-6-3-planning-roundup/): Please take a moment to review the latest plans for the next 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.. And give a round of applause to the new release squad! (You can find them and follow along over in [#6-3-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ), too!) * [@audrasjb](https://profiles.wordpress.org/audrasjb/) indicated that the full 6.3 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 schedule was almost ready to publish. The schedule includes at least 2 scrubs per week, on Tuesdays and Thursdays, and alternatively at 05:00, 06:00, 14:00, and 17:00 UTC. Everyone is welcome to join the first scrub on 25 May at 14:00 UTC. * [@karmatosed](https://profiles.wordpress.org/karmatosed/) wished to bring awareness to a proposal to include [#design](https://wordpress.slack.com/archives/C02S78ZAL) triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. as part of 6.3 [#core](https://wordpress.slack.com/archives/C02RQBWTW) and [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7) triages, rather than as separate design-only meetings. The objective is to draw greater designer focus to these release-specific meetings, and encourage better collaboration and alignment between teams. It is planned to record some of these sessions as learning resources. Tammie asked for feedback on this idea and how the Design team can be helpful in the release, with the first meeting plan soon to be posted on [make/design](https://make.wordpress.org/design/). She also called on other contributors to highlight tickets that needed Design team input, so that they could be amplified in [#design](https://wordpress.slack.com/archives/C02S78ZAL). * [@francina](https://profiles.wordpress.org/francina/) also gave a reminder that the [#6-3-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ) channel was a good place to follow along with release coordination efforts, in particular encouraging contributors with interest in helping on the 6.4 release to join the channel and ask questions. ## Maintainers: Component Help Requests [@afragen](https://profiles.wordpress.org/afragen/) called for additional help in testing the 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Dependencies feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See [Features as Plugins](https://make.wordpress.org/core/handbook/about/release-cycle/features-as-plugins/), and requested Design team feedback. [@karmatosed](https://profiles.wordpress.org/karmatosed/) proposed some options for helping move designer involvement forward. [@oglekler](https://profiles.wordpress.org/oglekler/) highlighted [#11856: URL for 1st comments page is not canonical](https://core.trac.wordpress.org/ticket/11856), indicating it would need a careful approach to resolution. ## Open Floor ### WP Adminadmin (and super admin) Help Panel [@studionashvegas](https://profiles.wordpress.org/studionashvegas/) shared [#55342: If the contextual help panel is open and then I scroll, I have to click on help twice to close the panel](https://core.trac.wordpress.org/ticket/55342), asking for review of the 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., which addresses a visual bug in WP admin. [@audrasjb](https://profiles.wordpress.org/audrasjb/) assigned the ticketticket Created for both bug reports and feature development on the bug tracker. to the 6.3 milestone, and marked for `needs-testing`. ### Special Focus Triage Sessions [@oglekler](https://profiles.wordpress.org/oglekler/) asked if there were plans for additional “old ticket” triage sessions, and [@karmatosed](https://profiles.wordpress.org/karmatosed/) suggested that holding even one session per release would be a good beginning. [@oglekler](https://profiles.wordpress.org/oglekler/) also wondered if all tickets marked as `critical` could be triaged, with the belief that many may be mis-classified. She suggested that the `critical` severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while **priority** is its relationship to other bugs. is most useful when applied correctly. [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) asked if reviewing these tickets was part of release scrubs, and [@audrasjb](https://profiles.wordpress.org/audrasjb/) indicated that scheduling dedicated scrubs for these tickets would be best, but that it was ultimately up to release Triage co-leads to decide. [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) then asked for volunteers to help facilitate these scrubs, suggesting there could be other interested contributors, and included a link to the Core Handbook’s [bug scrub tutorial](https://make.wordpress.org/core/handbook/tutorials/leading-bug-scrubs/). [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) added a reminder that scrubs could happen any time by anyone. He also indicated agreement that [existing `critical` tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&severity=critical&order=id) were mostly `normal` severity, and could be cleaned up quickly without requiring a meeting. Contributors can request “Bug GardenerBug Gardener A contributor who has been given advanced privileges in Trac.” Trac access in the [#core](https://wordpress.slack.com/archives/C02RQBWTW) channel if they wish to conduct triage. ## Next Meeting The next meeting will be on [May 31, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230531T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the [`#core` Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). _Props [@audrasjb](https://profiles.wordpress.org/audrasjb/) and [@pbiron](https://profiles.wordpress.org/pbiron/) for peer review of this summary._ [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-2-2](https://make.wordpress.org/core/tag/6-2-2/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 11:13 pm _on_ May 11, 2023 Tags: [6-3 ( 70 )](https://make.wordpress.org/core/tag/6-3/), [6.2 ( 90 )](https://make.wordpress.org/core/tag/6-2/), [dev chat ( 917 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [PHP 8.0 ( 6 )](https://make.wordpress.org/core/tag/php-8-0/), [summary ( 973 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev Chat Summary, May 10, 2023](https://make.wordpress.org/core/2023/05/11/dev-chat-summary-may-10-2023/)󠁿 The WordPress Developers Chat meeting took place on [May 10, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230510T2000) in the [core](https://wordpress.slack.com/messages/core/) channel of [Make WordPress Slack](https://make.wordpress.org/chat/). ## Key Links * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1683748821238729) of the Dev Chat on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). * Today’s agenda: [Dev Chat agenda, May 10, 2023](https://make.wordpress.org/core/2023/05/09/dev-chat-agenda-may-10-2023/), courtesy [@webcommsat](https://profiles.wordpress.org/webcommsat/). * Last meeting summary: [Dev Chat Summary, May 3, 2023](https://make.wordpress.org/core/2023/05/03/dev-chat-summary-may-3-2023/). ## Highlighted Posts * [A Week in Core, May 8, 2023](https://make.wordpress.org/core/2023/05/09/a-week-in-core-may-8-2023/): Thank you, [@audrasjb](https://profiles.wordpress.org/audrasjb/)! > Here’s an overview of updates in TracTrac An open source project by Edgewall Software > that serves as a bug tracker and project management tool for WordPress. between > May 1 and May 8, 2023: > * 24 commits > * 56 contributors > * 46 tickets created > * 9 tickets reopened > * 49 tickets closed > * and **5 new contributors** in this period 🎉 Welcome! * [What’s new for developers? (May 2023)](https://developer.wordpress.org/news/2023/05/whats-new-for-developers-may-2023/): Check out this nifty guide to some of the latest WordPress updates, especially suited for extenders or contributors who would like to learn more about developing with WordPress. * [WP Briefing: Episode 55: Happy Anniversary, WordPress!](https://wordpress.org/news/2023/05/episode-55-happy-anniversary-wordpress/): Take a look back on the past **20 years** and how the 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. community has grown WordPress into what it is today. * [What’s new in Gutenberg 15.7? (03 May)](https://make.wordpress.org/core/2023/05/04/whats-new-in-gutenberg-15-7-03-may/): This is of the best places to see what’s new in the 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/](https://wordpress.org/plugins/) or can be cost- based plugin from a third-party., as well as what’s in store for the future of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. * [@webcommsat](https://profiles.wordpress.org/webcommsat/) shared: It is day two of the “#WP20 From Blogs to Blocks” campaign. We have had a request from [#marketing](https://wordpress.slack.com/archives/C0GKJ7TFA) to highlight this in [#core](https://wordpress.slack.com/archives/C02RQBWTW) and encourage more devs to take part too: [https://github.com/WordPress/Marketing-Team/issues/220](https://github.com/WordPress/Marketing-Team/issues/220). ## Release Updates * [WordPress 6.2.1 RC1 is now available](https://make.wordpress.org/core/2023/05/09/wordpress-6-2-1-rc1-is-now-available/): Help test this first 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. candidate (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)](https://make.wordpress.org/core/author/ironprogrammer/?output_format=md#alpha-beta).) for 6.2 before next week’s final release. See the post for details on what’s been fixed, and watch the [#6-2-release-leads](https://wordpress.slack.com/archives/C04JZ199XPG) channel for additional updates. * And a reminder, for those who haven’t [submitted feedback](https://docs.google.com/forms/d/e/1FAIpQLSetmM1TctizUuo77LjcUeeqWR0mBGg_FIsiWiXXYYICvxU1Ag/viewform?usp=sharing) for the [WP 6.2 release retrospective](https://make.wordpress.org/core/2023/04/14/wordpress-6-2-dolphy-retrospective/)— [@priethor](https://profiles.wordpress.org/priethor/) has noted that the original survey deadline has been extended, so please make sure to take this opportunity to help improve future releases! ## Maintainers: Component Help Requests [@oglekler](https://profiles.wordpress.org/oglekler/) indicated a draft 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. was ready, and requested contributor involvement with [#23348: Add a “Contribute” tab to the about page](https://core.trac.wordpress.org/ticket/23348). [@audrasjb](https://profiles.wordpress.org/audrasjb/) agreed with the proposed update, but had a question about some of the languages included in the language options. Olga clarified that those were included in mobile apps, but that clarity was needed to avoid this appearing as a mistake. ## Open Floor ### PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.x Compatibility [@xavivars](https://profiles.wordpress.org/xavivars/) asked about PHP supported versions, and documentation surrounding it. He pointed out misconceptions that WordPress wouldn’t work under PHP 8.x [due to its “beta support” label](https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/), and has only upgraded his sites from PHP 7.4 recently due to this misunderstanding. He then posed these questions (paraphrased): 1. How can the PHP versions documentation page better convey that WordPress does work under PHP 8.x without major issues? 2. What are the tickets that can help move PHP 8.x support forward, and allow removal of the “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. support” 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.)? 3. Do others think this is a problem? [@oglekler](https://profiles.wordpress.org/oglekler/) related the numerous PHP notices encountered when trying out WooCommerce and PHP 8.2, noting that even if WordPress was almost ready, plugins and themes still posed a challenge. [@azaozz](https://profiles.wordpress.org/azaozz/) agreed that Core functions pretty well up to 8.2, and that plugins were the main reason behind the lack of full support. [@clorith](https://profiles.wordpress.org/clorith/) added that while Core should not have fatal errors, that the deprecation notices it might throw would be indiscernible from plugin errors to most users. [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) shared two relevant discussions from last month: * [https://wordpress.slack.com/archives/C02RQBWTW/p1680727533581459](https://wordpress.slack.com/archives/C02RQBWTW/p1680727533581459) * [https://wordpress.slack.com/archives/C02RQBWTW/p168072768559110](https://wordpress.slack.com/archives/C02RQBWTW/p1680727685591109) [@joemcgill](https://profiles.wordpress.org/joemcgill/) asked if the proposal mentioned in the second link was ever published, and if there was enough support to help make it happen. While not published yet, [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) confirmed the post is still planned, and that support for the compatibility strategy has been positive. She also noted that lifting PHP 8.0’s “beta support” label was a target for WordPress 6.3. [@clorith](https://profiles.wordpress.org/clorith/) suggested that the best place to continue discussion would be the [#core-php](https://wordpress.slack.com/archives/C60K3MP2Q) channel. [@azaozz](https://profiles.wordpress.org/azaozz/) noted that the [PHP Compatibility Checker](https://wordpress.org/plugins/php-compatibility-checker/) plugin only supports up to PHP 7.4, and questioned if it could be upgraded to support newer PHP versions. [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) mentioned the relevance of the [Tide project](https://wptide.org/), and [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) confirmed that Tide powers the recently updated PHP Compatibility Checker plugin. He added, however, that Tide in turn relies on [PHPCompatibilityWP](https://github.com/PHPCompatibility/PHPCompatibilityWP), which does not yet support PHP 8.x, and shared [a discussion link](https://wordpress.slack.com/archives/C7TK8FBUJ/p1680631652793589) toward adding PHP 8.x support. To help address [@xavivars](https://profiles.wordpress.org/xavivars/)‘s second question, [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) shared links to PHP 8 items in the 6.3 milestone: * [#57837 – PHP 8.x: various compatibility fixes for WordPress 6.3](https://core.trac.wordpress.org/ticket/57837)( epic tracking ticketticket Created for both bug reports and feature development on the bug tracker.) * [WordPress 6.3 PHP 8.0 Open Tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~php8+-php81+-php82&milestone=6.3&order=priority) * [WordPress 6.3 PHP 8.1 Open Tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~php81&milestone=6.3&order=priority) * [WordPress 6.3 PHP 8.2 Open Tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~php82&milestone=6.3&order=priority) [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) also pointed at a related topic that might help move PHP support-related discussions forward: [#57345: Bump the minimum required PHP version to 7.2](https://core.trac.wordpress.org/ticket/57345). [@webcommsat](https://profiles.wordpress.org/webcommsat/) indicated a possible need for [#marketing](https://wordpress.slack.com/archives/C0GKJ7TFA) team support to facilitate this work, which was confirmed by [@sereedmedia](https://profiles.wordpress.org/sereedmedia/). ### Update Error Messages [@pbiron](https://profiles.wordpress.org/pbiron/) raised the following ticket, [#57999: Don’t show error message when there is nothing to update](https://core.trac.wordpress.org/ticket/57999), requesting patch testing and design feedback. He asked if the idea of the ticket was sound, and which of the proposed patches would be preferred. [@oglekler](https://profiles.wordpress.org/oglekler/) suggested adding screenshots for the proposed patches. [@presskopp](https://profiles.wordpress.org/presskopp/) added screenshots of existing Core behavior, and [@pbiron](https://profiles.wordpress.org/pbiron/) additionally requested before/after shots for each of the patches. [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) also suggested pinging the [#design](https://wordpress.slack.com/archives/C02S78ZAL) channel for awareness. ### Screen Options and Help Panel Modernization [@oglekler](https://profiles.wordpress.org/oglekler/) asked for attention to be drawn to [#21583: Improve discoverability and visual design of Screen Options and Help Panels](https://core.trac.wordpress.org/ticket/21583), and remarked that modernizing these panels would also benefit 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). [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) referred to [@joedolson](https://profiles.wordpress.org/joedolson/) previously [suggesting some shared UI relevance](https://core.trac.wordpress.org/ticket/21583#comment:62) between this ticket and [WP Features Notifications](https://github.com/WordPress/wp-feature-notifications), and asked if there had been any discussion about this. [@oglekler](https://profiles.wordpress.org/oglekler/) asked how these were related. Brian provided the link to a recent [Notifications feature post](https://make.wordpress.org/core/2023/04/25/wp-feature-notifications-2023-status-update/), noting that the maintainers should be able to help answer questions. Joe further clarified that the Notifications feature is looking to add another panel in the same vicinity as Screen Options/Help, and called for holistic consideration of how each of these are implemented. Before moving to the next item, [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) pointed out that because Design Team time is often limited, addressing these related WP adminadmin (and super admin) UIUI User interface concerns at the same time could be a worthwhile collaboration. ### “Roll Back” UI String [@kebbet](https://profiles.wordpress.org/kebbet/) requested feedback and 6.3 milestone consideration for ticket [#58282: Change wording where `roll back` is used](https://core.trac.wordpress.org/ticket/58282), asking if more user-friendly terms should be considered. There were several positive emoji reactions to the ticket, and [@audrasjb](https://profiles.wordpress.org/audrasjb/) swiftly added it to the 6.3 milestone. ## Next Meeting The next meeting will be on [May 17, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230517T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the [`#core` Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). _Props [@audrasjb](https://profiles.wordpress.org/audrasjb/) and [@xavivars](https://profiles.wordpress.org/xavivars/) for peer review of this summary, and to everyone who participated in the Dev Chat._ [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-2](https://make.wordpress.org/core/tag/6-2/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#php-8-0](https://make.wordpress.org/core/tag/php-8-0/), [#summary](https://make.wordpress.org/core/tag/summary/) # Post navigation [← Older posts](https://make.wordpress.org/core/author/ironprogrammer/page/2/?output_format=md)