Title: 6-4 – Make WordPress Core --- # Tag Archives: 6-4 [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 11:39 pm _on_ January 31, 2024 Tags: 6-4, [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [core ( 723 )](https://make.wordpress.org/core/tag/core/), [core-editor ( 746 )](https://make.wordpress.org/core/tag/core-editor/), [dev chat ( 901 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 967 )](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, [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [core ( 723 )](https://make.wordpress.org/core/tag/core/), [core-editor ( 746 )](https://make.wordpress.org/core/tag/core-editor/), [dev chat ( 901 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 967 )](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/tag/6-4/?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/jorbin/) [Aaron Jorbin](https://profiles.wordpress.org/jorbin/) 8:26 pm _on_ January 25, 2024 Tags: 6-4, [6-4-x ( 2 )](https://make.wordpress.org/core/tag/6-4-x/), [minor releases ( 38 )](https://make.wordpress.org/core/tag/minor-releases/), [releases ( 56 )](https://make.wordpress.org/core/tag/releases/) # 󠀁[WordPress 6.4.3 RC1 is now available](https://make.wordpress.org/core/2024/01/25/wordpress-6-4-3-rc1-is-now-available/)󠁿 WordPress 6.4.3 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release: * Use the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) 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 this is a minor 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/tag/6-4/?output_format=md#alpha-beta). release, select the _Point Release_ channel and the _Nightlies_ stream. This is the latest build including the RC and potentially any subsequent commits in [trunk](https://make.wordpress.org/core/handbook/contribute/codebase/). * Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) to test: `wp core update `[https://wordpress.org/wordpress-6.4.3-RC1.zip](https://wordpress.org/wordpress-6.4.3-RC1.zip) * [Directly download the Beta/RC version](https://wordpress.org/wordpress-6.4.3-RC1.zip). ## What’s in this release candidate? 6.4.3 RC1 features [5 fixes in Core](https://core.trac.wordpress.org/query?status=closed&component=!Bundled+Theme&id=!59828&milestone=6.4.3&group=status&col=id&col=summary&col=component&col=owner&col=type&col=priority&col=version&col=keywords&order=priority) as well as [16 fixes](https://core.trac.wordpress.org/ticket/59828) for the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor. The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed: * [Text isnt highlighted when editing a page in latest Chrome Dev and Canary](https://core.trac.wordpress.org/ticket/59943) * [Update default PHP version used in local Docker Environment for older branches](https://core.trac.wordpress.org/ticket/60095) * [wp-login.php: login messages/errors](https://core.trac.wordpress.org/ticket/59983) * [Deprecated print_emoji_styles produced during embed](https://core.trac.wordpress.org/ticket/59892) * [Attachment pages are only disabled for users that are logged in](https://core.trac.wordpress.org/ticket/59866) The following block editor issues from 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/) are fixed: * [Fix block rename control shown in “Advanced” for unsupported blocks](https://github.com/WordPress/gutenberg/pull/55995) * [Query block: remove unnecessary class](https://github.com/WordPress/gutenberg/pull/55438) * [Fix duotone not showing in site editor style block level styles](https://github.com/WordPress/gutenberg/pull/55361) * [Query Loop – Add accessibility markup at the end of the loop in all cases.](https://github.com/WordPress/gutenberg/pull/55890) * [Background Image Support: Hide the background image reset button when there’s no image](https://github.com/WordPress/gutenberg/pull/55973) * [Background image support: Fix focus loss when resetting background image](https://github.com/WordPress/gutenberg/pull/55984) * [Autocomplete: Fix Voiceover not announcing suggestions](https://github.com/WordPress/gutenberg/pull/54902) * [Fix pattern category renaming causing potential duplicate categories](https://github.com/WordPress/gutenberg/pull/55607) * [Patterns: use existing download function for JSON downloads to fix non-ASCII encoding](https://github.com/WordPress/gutenberg/pull/55912) * [Add context for translators to any unclear usage of “synced”](https://github.com/WordPress/gutenberg/pull/55935) * [Image block: Add check for lightbox values during image block migration](https://github.com/WordPress/gutenberg/pull/56057) * [Image Block: Enable image block to be selected correctly when clicked](https://github.com/WordPress/gutenberg/pull/56043) * [Reduce specificity of default Cover text color styles.](https://github.com/WordPress/gutenberg/pull/56411) * [Image Block: Fix deprecation when width/height attribute is number](https://github.com/WordPress/gutenberg/pull/57063) * [Text selection: show CSS hack to Safari only.](https://github.com/WordPress/gutenberg/pull/57300) * [SlotFill: Allow contextual SlotFillProviders](https://github.com/WordPress/gutenberg/pull/56779) ## What’s next? The `dev-reviewed` workflow ([double committer sign-off](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-beta-versions/#double-committer-signoff)) is now in effect when making changes to the 6.4 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release( 3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".. The final release is expected on Tuesday, Janury 30th, 2024. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the 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/) 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/) [#6-4-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ) channel. A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test! _Thanks to _[@joemcgill](https://profiles.wordpress.org/joemcgill/)_ for pre-publication review_ [#6-4](https://make.wordpress.org/core/tag/6-4/), [#6-4-x](https://make.wordpress.org/core/tag/6-4-x/), [#minor-releases](https://make.wordpress.org/core/tag/minor-releases/), [#releases](https://make.wordpress.org/core/tag/releases/) [ ](https://profiles.wordpress.org/webcommsat/) [Abha Thakor](https://profiles.wordpress.org/webcommsat/) 6:33 pm _on_ January 24, 2024 Tags: 6-4, [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [agenda ( 1,125 )](https://make.wordpress.org/core/tag/agenda/), [dev chat ( 901 )](https://make.wordpress.org/core/tag/dev-chat/) # 󠀁[Dev Chat agenda, January 24, 2024](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/)󠁿 _(Update from new Contributor Meeting added)_ The next WordPress Developers Chat will take place on [Wednesday, 17 January 2024 at 20:00 GMT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240117T2000) in the [core](https://wordpress.slack.com/messages/core/) channel on [Make WordPress Slack](https://make.wordpress.org/chat/). 1. [Discussions](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#discussions) 2. [Highlighted posts](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#highlighted-posts) 3. [Core-editor updates](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#core-editor-updates) 4. [Releases](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#releases) 5. a. [Next major release: 6.5](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#next-major-release-6-5) b. [Next minor release: 6.4.3](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#next-minor-release-6-4-3) 6. [Tickets to highlight for assistance](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#tickets-to-highlight-for-assistance) 7. [Open floor](https://make.wordpress.org/core/2024/01/24/dev-chat-agenda-january-24-2024/#open-floor) ## Discussions These will focus on open proposals in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and release items. * [Interactivity API and building interactive blocks](https://make.wordpress.org/core/2023/03/30/proposal-the-interactivity-api-a-better-developer-experience-in-building-interactive-blocks/) has moved past the proposal stage and is aimed at being a key feature planned for 6.5. Now that it’s near complete and planned for 6.5: - is there anything actionable in the proposal? - or is it considered done / closed? Next week’s dev chat, a discussion opportunity is identified for this open proposal on core relating to [major release Field Guides](https://make.wordpress.org/core/2023/08/31/proposal-an-update-to-the-field-guide/). Could you help curate a Call for Volunteers to review the [open proposals on Make/Core](https://make.wordpress.org/core/?s=proposal) and create a list of unresolved ones to discuss during Dev Chat meetings? ## Highlighted posts [Summary from the experimental new style Dev Chat from January 17, 2024](https://make.wordpress.org/core/2024/01/22/dev-chat-summary-january-17-2024/)– [@webcommsat](https://profiles.wordpress.org/webcommsat/) and [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) [A Week in Core – January 24, 2024](https://make.wordpress.org/core/2024/01/22/a-week-in-core-january-22-2024/)– props to [@audrasjb](https://profiles.wordpress.org/audrasjb/) for creating this. On TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 15 and January 22, 2024: * 35 commits * 62 contributors * 67 tickets created * 10 tickets reopened * 72 tickets closed * and a welcome to three new contributors [Performance team roadmap for 2024](https://make.wordpress.org/performance/roadmap-2024/) is out and covers priorities. Team reps update. The nomination period has been extended for the Core Team Reps 2024 edition to [Wednesday, 31 January 2024 at 23:59 GMT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240131T2359). Full details are on the [original nominations post](https://make.wordpress.org/core/2023/12/04/nominations-for-core-team-reps-2024-edition/) where nominations can be added. New core contributor meeting – if you were not able to attend and would like to find out more, check out the link to the meeting in [Slack on January 24, 2024](https://wordpress.slack.com/archives/C02RQBWTW/p1706122821516599) which includes useful information on getting started and the contributor mentorship program. The deadline for applications for the second cohort for the program is Wednesday, February 7, 2024. ## Core-editor updates [Core Editor Improvement: Robust Revisions in the Site Editor](https://make.wordpress.org/core/2024/01/22/core-editor-improvement-robust-revisions-in-the-site-editor/). Props to [@annezazu](https://profiles.wordpress.org/annezazu/) for sharing this list. * [Marketing tracking issue](https://github.com/WordPress/gutenberg/issues/58028) opened for the highlight grid for 6.5. * Section Styling: some [questions remain around CSS specificity ](https://github.com/WordPress/gutenberg/issues/57537#issuecomment-1895419662) to unblock this work. Whether that problem can be resolved determines whether this will be included in the release. * Font Library: biggest work continues to be the [Font Library: refactor REST API](https://github.com/WordPress/gutenberg/issues/55278#top) which needs feedback. Please help review if you have experience with the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface( API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/) and review the [merge criteria for this feature.](https://href.li/?https://core.trac.wordpress.org/ticket/59166#comment:23). * Pattern overrides: PR was merged to [Stabilize the pattern overrides block context](https://github.com/WordPress/gutenberg/pull/58102#top)/ remove it as experimental and to add override support to [image blocks](https://github.com/WordPress/gutenberg/pull/57909), [heading blocks, and button blocks](https://github.com/WordPress/gutenberg/pull/57789). * List View: a nice UXUX User experience improvement the merging of[ Displace list view items when dragging (a bit more WYSIWYG)](https://github.com/WordPress/gutenberg/pull/56625#top). * Data Views: the default layout has been set to table layout for template, template parts, and patterns after feedback from design. A PR is in progress to stabilize the new [Data Views for Patterns ahead of the release](https://github.com/WordPress/gutenberg/pull/58139) with the grid layout as the default. * 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.: [work continues](https://github.com/WordPress/gutenberg/issues/56803#issuecomment-1904202471) for a public launch with 6.5 with great optimism that it will make the cut off. * Link Control: A bigger draft PR is in the works for [Implementing new UX for invoking rich text Link UI](https://github.com/WordPress/gutenberg/pull/57986#top), alongside some smaller quality of life PRs like [improving the link control preview.](https://github.com/WordPress/gutenberg/pull/57775) * 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. Bindings: a discussion was kicked off around [what parts to include for 6.5](https://wordpress.slack.com/archives/C02QB2JS7/p1705917394175109) alongside a [PR to backport for introducing the API to core](https://github.com/WordPress/wordpress-develop/pull/5888) and broader technical work in[ Add block bindings PHP registration mechanisms and “Post meta” source under the experimental flag](https://github.com/WordPress/gutenberg/pull/57249). ## Releases ### 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 Any other updates? Phase 3 media library meeting will take place on [Thursday, 8 February 2024 at 00:00 GMT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240208T0000) in the [#core-media](http://wordpress.slack.com/messages/core-media/) channel. The Media Component team is coordinating a meeting with the Editor team and other interested stakeholders to work on planning for the proposed Phase 3 Media Library. [Core-editor improvement – revisions in the site editor](https://make.wordpress.org/core/2024/01/22/core-editor-improvement-robust-revisions-in-the-site-editor/). This is a useful post for understanding some of the changes and new features to current revision functionality in the Site Editor aimed for 6.5 and the wider work in this area.  [WordPress 6.5 release squad formation](https://make.wordpress.org/core/2024/01/18/wordpress-6-5-release-squad-formation/) as at January 18, 2024. Additional discussion on size of the squad can be found in the comments on this post. [Important milestones in the Editor for 6.5](https://make.wordpress.org/core/2024/01/19/editor-important-milestones-for-wordpress-6-5/)– useful post for contributors working or wishing to support the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) repository with the 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. 1 for WordPress 6.5 scheduled for February 13, 2024. **Existing 6.5 links** * [Roadmap to 6.5](https://make.wordpress.org/core/2023/12/07/roadmap-to-6-5/) * [WordPress 6.5 Editor Tasks board](https://github.com/orgs/WordPress/projects/148) * [Development cycle page](https://make.wordpress.org/core/6-5/) ### Next 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.: 6.4.3 Any other updates? Earlier today there were[ four open tickets](https://wordpress.slack.com/archives/C055Y7FKS7N/p1706113701035289)– update in 6.4 release leads channel. ## Tickets to highlight for assistance Tickets for 6.5 and 6.4.3 will be prioritized. ## Open floor [#6-4](https://make.wordpress.org/core/tag/6-4/), [#6-5](https://make.wordpress.org/core/tag/6-5/), [#agenda](https://make.wordpress.org/core/tag/agenda/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/webcommsat/) [Abha Thakor](https://profiles.wordpress.org/webcommsat/) 9:49 pm _on_ January 22, 2024 Tags: 6-4, [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [core ( 723 )](https://make.wordpress.org/core/tag/core/), [core-editor ( 746 )](https://make.wordpress.org/core/tag/core-editor/), [dev chat ( 901 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 967 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev Chat summary, January 17, 2024](https://make.wordpress.org/core/2024/01/22/dev-chat-summary-january-17-2024/)󠁿 [Start of meeting on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1705521631998149) This DevChat starts with an experiment to shift the chat to synchronize discussions and away from dropping of links. Please read the [DevChat Agenda](https://make.wordpress.org/core/2024/01/16/dev-chat-agenda-january-16-2024/) for a curated list of [announcements](https://make.wordpress.org/core/2024/01/16/dev-chat-agenda-january-16-2024/#announcements), [highlighted posts](https://make.wordpress.org/core/2024/01/16/dev-chat-agenda-january-16-2024/#highlighted-posts), [Core Editor updates](https://make.wordpress.org/core/2024/01/16/dev-chat-agenda-january-16-2024/#core-editor-update), [major and minor release updates](https://make.wordpress.org/core/2024/01/16/dev-chat-agenda-january-16-2024/#release-updates), and more. ## Discussion on open proposals in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. ### Default Theme Task Force for 2024 Link to the post: [Proposal: Default Theme Task Force for 2024](https://make.wordpress.org/core/2023/12/05/proposal-default-theme-task-force-for-2024/) [Dev Chat slack link](https://wordpress.slack.com/archives/C02RQBWTW/p1705521914972909) **Comments in Dev Chat focused:** * positive feedback and highlighting that people can self-nominate their ability to help triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. those open default theme issues * promote the call to encourage people to be active in triaging and resolving those [436 Bundled Theme tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&component=Bundled+Theme&group=milestone&max=500&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority) **Latest position from [@desrosj](https://profiles.wordpress.org/desrosj/) **: * advised the idea has been accepted: t’s rallying a group of folks to get through and clean out the Bundled Theme component backlog on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. * three self nominations and more expected to be confirmed by end of the week * aim to start before the end of January 2024, currently 437 tickets in the Bundled Theme component * Jonathan will be leading the team as a mentor and someone with commit privileges, and other committers are welcome to help as well) * the week to week working arrangement will be depends on the team’s availability. Stay tuned!  * confirmed the new theme task force group will remain under core team purview. More detail on this in the comments section of the post. More contributors for the Themes team welcome to help out too. “It’s a balance though, My goal here was to allow those contributors to continue exploring what new themes look like while this team handles cleaning up some of our cruft and backlog for pre-existing ones.” * expecting ‘as a side effect, cleaning out the backlog also will effectively “ retire” these themes in some ways, and going forward, the majority of the tickets will be blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor support related (hopefully).’  **Actions**: * more volunteers needed and will increase the speed can go through the outstanding tickets in the component * to assist, contact [@desrosj](https://profiles.wordpress.org/desrosj/) 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/) on in the comments for the post itself ### Proposal to improve the editor tech workflow for major releases **Post link:** [Proposal](https://make.wordpress.org/core/2023/08/01/proposal-improve-the-editor-tech-workflow-for-major-releases/) [Dev Chat Slack link](https://wordpress.slack.com/archives/C02RQBWTW/p1705522885954929) **Context: **This proposal was started in 6.4. With 6.5 underway, thinking the learnings from 6.4 could be built upon for how to continue improving the Core merges 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/) during 6.5. Core Editor and Core chats are now combined into Dev Chat as an experiment. **Discussion**: * [@joemcgill](https://profiles.wordpress.org/joemcgill/) raised the question of the right venue to push this forward. “In my opinion, the current status quo is error prone and unsustainable (as well as taking a lot of manual overhead from contributors).” * [@jorbin](https://profiles.wordpress.org/jorbin/): If we want to try early syncing for 6.4.3, [https://core.trac.wordpress.org/ticket/59828](https://core.trac.wordpress.org/ticket/59828) just needs a second committers review and we can get all the updates into the 6.4.x nightly * [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/): I’m not sure either what the “right venue for pushing this forward” is. Needs a discussion with both Core and Core Editor folks to figure out the needs and how to improve these workflows. Seems earlier the better as 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 is fast approaching * [@jorbin](https://profiles.wordpress.org/jorbin/) suggested one way to mitigate the issue would be nominating the release team, or at least the editor tech, for the next release before the current release ships. An interim editor tech to help get the ball rolling while an official team has not been announced. [@joemcgill](https://profiles.wordpress.org/joemcgill/) agreed having an identified set of release leads for 6.5 to discuss how they want to handle things for this release would help. The [Community Summit conversation](https://make.wordpress.org/summit/2023/08/22/community-summit-discussion-notes-aligning-processes-and-contributions-between-wordpress-core-and-gutenberg/) was very helpful. A working group to continue that conversation and come back with concrete proposals would be helpful, if a release team is not the right venue. A working group had positive feedback in the dev chat discussions as these workflows are continuously improving and span more than one 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.. [@jorbin](https://profiles.wordpress.org/jorbin/) suggested @tellthemachines should be given right of first refusal to continue leading the effort since she kicked off the proposal. * Ideas included: a proposal needed to address the identified set of problems, a hallway hangout similar to the ones [@annezazu](https://profiles.wordpress.org/annezazu/) and others have done. **Actions:** * Wait for response from [@isabel_brison](https://profiles.wordpress.org/isabel_brison/) about leading the working group. Done ✅ After DevChat, [Isabel responded](https://wordpress.slack.com/archives/C02RQBWTW/p1705544044578779?thread_ts=1705523590.619159&cid=C02RQBWTW) and is interested in leading the working group. * Make/Core post for plans and to form a working group, along with an [actionable list of tasks to tackle](https://wordpress.slack.com/archives/C02RQBWTW/p1705544044578779?thread_ts=1705523590.619159&cid=C02RQBWTW). ## Forthcoming releases ### 6.5 [Slack discussion link](https://wordpress.slack.com/archives/C02RQBWTW/p1705523732107169) [See this section in the agenda](https://make.wordpress.org/core/2024/01/16/dev-chat-agenda-january-16-2024/#next-major-release-6-5) for updates, helpful links, and information for the 6.5 release. Blockages/ items need discussion for progress: * Font Library: - Discussion: * As a follow-up from [@joemcgill](https://profiles.wordpress.org/joemcgill/)‘ s questions last week, [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) has added the Core merge criteria/expectations to its Trac ticketticket Created for both bug reports and feature development on the bug tracker.. [The critieria](https://core.trac.wordpress.org/ticket/59166#comment:23) is the same as in 6.4, except Tonya is suggesting returning to the expectation the feature is merged before or by Beta 1. * Query raised on the criteria aspect of “running on wp.com, and not being reliant on any specific host testing this. [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/): The reason for wp.com is: it’s a normal workflow in Gutenberg as it gains a huge amount of sites running it. [@jorbin](https://profiles.wordpress.org/jorbin/) * [@annezazu](https://profiles.wordpress.org/annezazu/) suggested some of the contributors who have worked on this feature could comment. Also noted current timeline for the feature [https://core.trac.wordpress.org/ticket/59166#comment:21](https://core.trac.wordpress.org/ticket/59166#comment:21) * Question: Is this anything beyond what we’d normally expect of a 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/)? [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/): Same expectations except for REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application( think “phone app” or “website”) can communicate with the data store (think“ database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/) part of it , as I’m suggesting a maintainer needs to give a thumbs-up to its design. * jorbim: I don’t want to discourage that in any way, I just wonder if we would ever set a requirement like “Is running on Altis with no major issues” - Actions: * Update the criteria from the discussion. Done ✅ * Gather expectations from the REST API maintainers and then update the criteria accordingly. Done ✅ ## How was the first experimental new DevChat? [@jorbin](https://profiles.wordpress.org/jorbin/) said: “I think one of the most productive meetings in a while” [@afragen](https://profiles.wordpress.org/afragen/) shared there was no extra time to raise other tickets for discussion. ### What to change? Next week, reserve 10-15 minutes for open forum / floor discussion. _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/hellofromtonya/) [Tonya Mork](https://profiles.wordpress.org/hellofromtonya/) 8:03 pm _on_ January 16, 2024 Tags: 6-4, [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [core ( 723 )](https://make.wordpress.org/core/tag/core/), [core-editor ( 746 )](https://make.wordpress.org/core/tag/core-editor/), [dev chat ( 901 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 967 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev Chat Summary, January 10, 2024](https://make.wordpress.org/core/2024/01/16/dev-chat-summary-january-10-2024/)󠁿 The WordPress Developers Chat meeting took place on [ 10 January 2024 at 20:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240110T2000) in [core](https://wordpress.slack.com/messages/core/) on [Make WordPress Slack](https://make.wordpress.org/chat/). ## Key info * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1704916883250509) of the DevChat 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. * Today’s [DevChat Agenda](https://make.wordpress.org/core/2024/01/10/dev-chat-agenda-january-10-2024/) was prepared by [@webcommsat](https://profiles.wordpress.org/webcommsat/). Please read the [DevChat Agenda](https://make.wordpress.org/core/2024/01/10/dev-chat-agenda-january-10-2024/) for a curated list of [announcements](https://make.wordpress.org/core/2024/01/10/dev-chat-agenda-january-10-2024/#announcements), [highlighted posts](https://make.wordpress.org/core/2024/01/10/dev-chat-agenda-january-10-2024/#highlighted-posts), [Core Editor updates](https://make.wordpress.org/core/2024/01/10/dev-chat-agenda-january-10-2024/#core-editor-update), [major and minor release updates](https://make.wordpress.org/core/2024/01/10/dev-chat-agenda-january-10-2024/#release-updates), and more. ## Chat Summary [Nominations for 2024 Core Team Reps](https://make.wordpress.org/core/2023/12/04/nominations-for-core-team-reps-2024-edition/): * Status: no accepted or new nominations. * Nomination period will be extended. * [@webcommsat](https://profiles.wordpress.org/webcommsat/) and I will continue until new reps are elected. * [@audrasjb](https://profiles.wordpress.org/audrasjb/) suggested: [“current team reps nominations can also be considered”](https://wordpress.slack.com/archives/C02RQBWTW/p1704917470648489). [@desrosj](https://profiles.wordpress.org/desrosj/) [reminded Gutenberg and Core development contributors](https://wordpress.slack.com/archives/C02RQBWTW/p1704917579615229) to update their [local Node.js/npm](https://make.wordpress.org/core/2023/12/20/updating-wordpress-to-use-more-modern-versions-of-node-js-npm-2/) as: > .. the versions of Node.js and npm required for WordPress CoreCore Core is the > set of software required to run WordPress. The Core Development Team builds WordPress. > development are now 20.x and 10.x. > In order to continue contributing to WordPress through `wordpress-develop` or ` > WordPress/Gutenberg`, you’ll need to upgrade the version of Node.js installed > on your machine to one that’s greater than or equal to 20.10.0 (currently the > most recent generally available version 20.x version). This should also update > npm to the correct, expected version appropriately (10.2.3 or higher is required). ### Release Updates #### Next 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.: 6.4.3 [@jorbin](https://profiles.wordpress.org/jorbin/) [shared an update](https://wordpress.slack.com/archives/C02RQBWTW/p1704918863614559): * Timeline coming before next devchat. * No pressing issues – okay to wait “a few weeks for the next minor.” * Reminder to “milestone any tickets” needing addressing. #### 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 * Release squad: [call to join the squad ended Jan 12th](https://make.wordpress.org/core/2023/12/22/call-to-action-2024-major-releases-call-for-volunteers/). * Current: in Alpha. * Next milestone: 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 is Feb 13th. ### Tickets / Issues that need assistance * [#60227](https://core.trac.wordpress.org/ticket/60227) [@jonsurrell](https://wordpress.slack.com/team/U0LN70VT9) asked for feedback to use an external library for testing the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. 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.. * [#60025](https://core.trac.wordpress.org/ticket/60025) [@jorbin](https://profiles.wordpress.org/jorbin/) requested help (it’s in the 6.4.3 milestone) and noted: > Joe did a great job of [summerizing and shared some paths forward](https://core.trac.wordpress.org/ticket/60025#comment:6) > that I think could be good to explore * [#58719](https://core.trac.wordpress.org/ticket/58719) [@justlevine](https://profiles.wordpress.org/justlevine/) asked is for feedback and decision criteria for bumping the minimum PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version to 7.2. * [@bph](https://profiles.wordpress.org/bph/) shared the following 6.5 features being developed 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/) that need testing and feedback: - [Font Library](https://github.com/WordPress/gutenberg/issues/55277). - [Syncing specific blocks and attributes of patterns](https://github.com/WordPress/gutenberg/issues/53705). - [New data views for templates, template parts, and patterns in the Site Editor](https://github.com/WordPress/gutenberg/issues/55083). - [Robust revisions](https://github.com/WordPress/gutenberg/issues/55776). - [background image support for the Group block](https://github.com/WordPress/gutenberg/issues/54336). - [aligning page edit features in Site Editor and Post Editor](https://github.com/WordPress/gutenberg/issues/52632#top). ### Open Floor #### Discussion of changing DevChat [@jorbin](https://profiles.wordpress.org/jorbin/) [opened the discussion for changing DevChat](https://wordpress.slack.com/archives/C02RQBWTW/p1704919529138629), i.e. to get to the important things to chat about (rather than half or more of the meeting dropping links): > As we are now 43 minutes into the meeting and it’s been almost all link sharing > thus far, I wonder if perhaps 2024 should be the year we explore some alternatives > for this meeting? I’m not sure that a link dump is doing it The discussion summary: * [“expect people to read”](https://wordpress.slack.com/archives/C02RQBWTW/p1704919858617819) the agenda. * Drop a prepared message with a link(s) to the sections of the agenda. * [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) [noted DevChat is also for](https://wordpress.slack.com/archives/C02RQBWTW/p1704920210369459) synchronize the discussion to help move forward the release important things: > socializing to folks leading/working on feature projects or specific items targeted > in a current major release that devchat is a good place to come and share blocks/ > problems/areas for feedback they have.  Chatting through those things synchronously > can help find alternate paths forward for those things that are of importance > to the project. * [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) [also shared](https://wordpress.slack.com/archives/C02RQBWTW/p1704920210369459) DevChat can include a discussion of [open proposals](https://make.wordpress.org/core/?s=proposal) > advance those conversations towards an acceptance or finding iterative ways to > improve those proposals. _When to start?_ Experiment starts next meeting. Call for Volunteers to review the [open proposals on Make/Core](https://make.wordpress.org/core/?s=proposal) and create a list of unresolved ones to discuss during the DevChat meeting. #### Font Library – avoid merge roadblocks [@joemcgill](https://profiles.wordpress.org/joemcgill/) [asked for Font Library](https://wordpress.slack.com/archives/C02RQBWTW/p1704919671027799) update and plan to avoid the roadblocks experienced during 6.4. See the discussion in the Slack thread which includes Core merge criteria. ## Next Meeting The next meeting will be on [ 17 January 2024 at 20:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240117T2000). This DevChat will experiment with a new approach Are you interested in helping draft DevChat summaries? Volunteer at the next meeting! _Props _[@webcommsat](https://profiles.wordpress.org/webcommsat/)_ 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/jorbin/) [Aaron Jorbin](https://profiles.wordpress.org/jorbin/) 7:31 pm _on_ January 16, 2024 Tags: 6-4, [6-4-release-leads ( 2 )](https://make.wordpress.org/core/tag/6-4-release-leads/), [core ( 723 )](https://make.wordpress.org/core/tag/core/), [maintenance ( 12 )](https://make.wordpress.org/core/tag/maintenance/) # 󠀁[6.4.3: An upcoming maintenance release](https://make.wordpress.org/core/2024/01/16/6-4-3-an-upcoming-maintenance-release/)󠁿 WordPress 6.4.3 is scheduled to be the next maintenance release for the 6.4 version. Its release will follow the following preliminary schedule: * 25 January 2024 – Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/tag/6-4/?output_format=md#alpha-beta). made available and announced here on the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. site. * 30 January 2024 – Final release made available. Specific times will be decided in advance and adjustments to the schedule may be made. All adjustments will be noted in this post. Minor or Maintenance releases of WordPress are intended as 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.- fix releases. Currently, [four bug fixes have been merged](https://core.trac.wordpress.org/query?status=closed&milestone=6.4.3&order=priority) into the 6.4 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". with [seven additional tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&milestone=6.4.3&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority) intended for this release. If you have a ticketticket Created for both bug reports and feature development on the bug tracker. that you think should be considered, please put it in the milestone or if you lack bug gardening capabilitiescapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability)., add a comment here. Note: except in extreme situations, only bug fixes will be considered and generally only bugs that have been introduced during the 6.4 cycle. Final note: Some default themes are also receiving updates, but these will be happening separately even though the tickets are in the 6.4.3 milestone. See [#60267](https://core.trac.wordpress.org/ticket/60267) for more information. **Update: [The theme updates have been released](https://make.wordpress.org/core/2024/01/16/twenty-twenty-one-twenty-twenty-and-twenty-seventeen-updates-now-available/)** ## Get involved with 6.4.3 Bug Scrubs will happen in the [#core](https://make.wordpress.org/core/tag/core/) room during the follow times: * [January 18, 2024 at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240118T1500) * [January 24, 2024 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240124T1600) Each of the open tickets is going to require development work along with testing and review. You can also run scrubs to help ensure that the correct tickets all are fixed in this release. Additionally, while the intent is for no new strings in this release, [some locales have strings in 6.4 in need of translation](https://translate.wordpress.org/stats/). General coordination for the release will happen in the [#6-4-release-leads](https://make.wordpress.org/core/tag/6-4-release-leads/) channel and decisions around code for the release will be made in the [#core](https://make.wordpress.org/core/tag/core/) room. 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. will be led by [@mikachan](https://profiles.wordpress.org/mikachan/), [@joemcgill](https://profiles.wordpress.org/joemcgill/), and myself ([@jorbin](https://profiles.wordpress.org/jorbin/)). _Thank you to [@fabiankaegy](https://profiles.wordpress.org/fabiankaegy/), [@annezazu](https://profiles.wordpress.org/annezazu/), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) for pre-publication review. _ [#6-4](https://make.wordpress.org/core/tag/6-4/), [#maintenance](https://make.wordpress.org/core/tag/maintenance/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 10:17 pm _on_ December 13, 2023 Tags: 6-4, [6-5 ( 76 )](https://make.wordpress.org/core/tag/6-5/), [dev chat ( 901 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 967 )](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/jorbin/) [Aaron Jorbin](https://profiles.wordpress.org/jorbin/) 7:01 pm _on_ December 13, 2023 Tags: 6-4, [bug scrub ( 83 )](https://make.wordpress.org/core/tag/bug-scrub/) # 󠀁[6.4.3 Maintenance Release Bug Scrub](https://make.wordpress.org/core/2023/12/13/6-4-3-maintenance-release-bug-scrub/)󠁿 There is no specific target date for WordPress 6.4.3 yet, but that doesn’t mean work can’t be done to ensure that all the correct bugs are targeted for it and that work progresses towards fixing them. To assist with this, some initial scrubs will be held at the following times: * [Thursday, December 14, 2023 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231214T1600) * [Monday, December 18, 2023 at 21:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231218T2100) All Scrubs will take place in the [#core room in Slack](https://wordpress.slack.com/archives/C02RQBWTW). The first scrub will be going through [tickets in awaiting review that may belong in the 6.4.3 milestone](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&version=trunk&version=6.4.2&version=6.4.1&version=6.4&type=defect+(bug)&milestone=Awaiting+Review&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=component&order=priority) with the goal of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and the second scrub will focus on [tickets in the 6.4.3 milestone](https://core.trac.wordpress.org/tickets/minor). Anyone else that wishes to host a scrub for 6.4.3 is welcome. Please comment here with the time you would like to hold one and I will edit the post to include it. As the documentation on [leading bug scrubs](https://make.wordpress.org/core/handbook/tutorials/leading-bug-scrubs/) states: > Leading a Bug Scrub is something any interested community member can do. _Thanks to [@joemcgill](https://profiles.wordpress.org/joemcgill/) for prepublication review_ [#6-4](https://make.wordpress.org/core/tag/6-4/), [#bug-scrub](https://make.wordpress.org/core/tag/bug-scrub/) [ ](https://profiles.wordpress.org/cbringmann/) [Chloe Bringmann](https://profiles.wordpress.org/cbringmann/) 4:37 pm _on_ December 5, 2023 Tags: 6-4, [retrospective ( 23 )](https://make.wordpress.org/core/tag/retrospective/) # 󠀁[Recap: WordPress 6.4 “Shirley” Retrospective ](https://make.wordpress.org/core/2023/12/05/recap-wordpress-6-4-shirley-retrospective/)󠁿 This post summarizes the feedback received from the [WordPress 6.4 retrospective](https://make.wordpress.org/core/2023/11/15/wordpress-6-4-retrospective/). Thank you to those who contributed their feedback via the retrospective survey and comments on the post.  For ease of reading, feedback has been synthesized. Full feedback is available for review in the [anonymized form responses](https://docs.google.com/spreadsheets/d/1wXENe5YD73hTta76YrhJS9BK7XZ3Ss2m-ILT5bmlGgc/edit?usp=sharing) and comments to the original post. Please remember that the following feedback are suggestions to bear in mind for future releases rather than action items for implementation.  ## **What would you keep?** * The Community needs/“wishlist.” * Blogblog (versus network, site) post per new feature or major change, e.g., performance improvements or the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. Tag processor. * Release team formation and announcement during the previous release cycle for easy coordination. * A 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/) channel per release focus. * Having a co-lead per release focus to allow for complimentary time-zone coverage. * Weekly health checks. ## **What would you add?** * Additional minor releases between majors.  * Iteration on Twenty Twenty-Four for Twenty Twenty-Five to reduce fragmentation. * Earlier merging of stable 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/) features into WordPress trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision..  * Equal focus on old tickets and bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions( adverse changes from the previous version) being the highest priority. fixes with new features. * Feature the Pattern Directory in the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor. * A dedicated session in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for testing the release.  * A focus on cohort involvement for sustained contribution beyond a 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.’s development cycle.  * More underrepresented release squads and opportunities for synchronous meetings in different time zones.  ## **What would you remove? ** * Underrepresented release squads.  * Minimum Core code contribution for Editor Tech role. * Increased documentation and training for new contributors to the release process. * Allow only “blessed tasks,” with enhancements/features that have received a first commit 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 to continue to Beta 2 et al. ## **How did the collaboration feel?** This section included ways for one to indicate how much they agreed or disagreed with a statement around collaboration. [[ ## Would you like to be part of future release squads? * 16.7%: I haven’t been part of the squad but I would like to try in the future. * 8.3%: I have been part of a release squad and I will gladly repeat. * 41.5%: I have been part of a release squad before and will do so again, although maybe not next year. * 8.3%: I am reluctant to participate again, but I would be open to it if responsibilities and processes were clearer. * 8.3%: Maybe later, I’m not sufficiently experienced yet. * 8.3%: I have been part of a release squad and would like to repeat, but unfortunately I don’t have the time for near/midterm future. ## **Takeaways and next steps** * Respondents felt that following the development cycle as a new contributor was challenging. - Future [WordPress Contributor Mentorship](https://make.wordpress.org/project/?p=299) programs will mirror major releases so new contributors have mentored experience with ample documentation and support to find contribution onboarding opportunities. * The shorter development cycle, while previously requested, felt too short for ample feature development and testing. - The [proposed 2024 roadmap](https://wordpress.org/about/roadmap/) allows for extended development cycles. * 6.4 was, for all intents and purposes, a success in bringing underrepresented gender voices, skill sets, and points of view into WordPress’s development cycle. 2024 will not include specific release squads to allow for more broad contributor involvement. * Maintenance will be one focus alongside new features for the WordPress 6.6 release in response to a call for more maintenance in major releases.  _Props to [@priethor](https://profiles.wordpress.org/priethor/) and [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) for reviewing this post. _ [#6-4](https://make.wordpress.org/core/tag/6-4/), [#retrospective](https://make.wordpress.org/core/tag/retrospective/) # Post navigation [← Older posts](https://make.wordpress.org/core/tag/6-4/page/2/?output_format=md)