Dev Chat Summary, October 4, 2023

Summary from the weekly WordPress developers chat that took place on 2023-10-04 at 20:00 UTC  in the core channel of Make WordPress Slack.

Key items

Start of the Dev Chat on Slack

Summary of where to post items for discussion, shared by @hellofromtonya:

  • from last week’s discussions, an effort is underway to move all source code discussions / decision making out of the release channel to happen here in #core 
  • if there’s source code or tickets to be discussed, please post them into the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., not in the #6-4-release-leads channel
  • if the release squad needs a heads up, it’s okay to post in the #6-4-release-leads channel. It’s helpful to share a link to where the discussion is happening in #core

Announcements

WordPress 6.4 Beta 2 is available – please help test and thanks to everyone who contributed and took part in the release party.

In the #core-editor channel, a change in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 16.8 release was discussed and agreed:

  • shift the Gutenberg 16.8 final release to Monday, October 9 (instead of Wed), ahead of the 6.4 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. 3 release
  • if more changes happen for the Font Library, do another 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). release before 16.8 final release

The change is to provide additional time to review and test requested changes to the Font Library’s 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/. before Beta 3.

Highlighted posts

  • Hallway Hangout – working session on consolidating modes. November 15, 2023. This is part of efforts to improve accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) of the Site Editor.   
  • The PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party checker repo is now in the WordPress organization on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/https://github.com/WordPress/plugin-check.
  • Benchmark results on 6.4 Beta 1 from the Performance Team can be read on its meeting summary.

Forthcoming release updates

Next major WordPress release: 6.4

Reminder: WordPress 6.4 Beta 3 is scheduled for October 10, 2023 – the last scheduled beta before RC1.

Update from the release squad

  • No additional major updates than the items covered.
  • Calls/Action: Note that anyone can test or file bugs they find and do not need to wait for a scrub etc.
  • Highlighted 6.4 is a shorter release cycle than recent ones, and encouraged folk to help.
  • Commit freeze experiment: no commits starting 1 hour before the release party start time seemed to work well, and will be continued throughout the rest of the cycle
  • Still lots of bugfix tickets in the milestone that need help to further.

Calls: You can help with:

@hellofromtonya confirmed if needed an unscheduled beta can (and often does if more commits come in) happen before RC1.

Calls relating to specific 6.4 tickets

About Page for 6.4

  • Call for feedback on the first draft of the About Page for 6.4. @estelaris has asked for comments to be left either on the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. #59289 or in Figma.
  • Confirmation: core developers will be able to build/commit the About Page. Request to share in the core channel when the different stages of the page are ready before each release milestone. Any additional help offers, please comment in the 6.4 release leads channel on Slack.

56922 Template/ Template Part RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.

  • @spacedmonkey and @antonvlasenko asked for assistance to take forward a Pull Request on Trac Ticket #56922 to try and get it into 6.4. The ticket allows the Gutenberg team to make revisions for template / templates parts in the editor. There is a GitHub PR 3533. More information on the call in Slack.

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.

Docs release team update via @webcommsat

  • In the Docs release team, we are working on collating dev notes for 6.4.
  • Reaching out to component maintainers as part of this and appreciate replies and input. Those involved with or writing dev notes will be able to update the GitHub project board for tracking 6.4 docs (link will be shared when ready).
  • Request to not publish dev notes as the team will be doing a final review and publish these to avoid swamping core and the RSS feedRSS Feed RSS is an acronym for Real Simple Syndication which is a type of web feed which allows users to access updates to online content in a standardized, computer-readable format. This is the feed. with too many at the same time.

More 6.4 discussion areas

Not all of these were highlighted individually during the meeting due to time. The full list in the agenda was highlighted and is listed below to help people keep in the know.

Call to Contributors: Can you help with any of these items?

  1. Discussion in release leads/ core has been on Trac ticket #59526 issue relating to fixing image assets with the Twenty Twenty Four theme identified during 6.4 beta 2 release party. Discussion in core. Update in Dev Chat: this has now been fixed.
  2. Discussion on the issue of non-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. themes access to the site editor’s pattern page, Trac ticket #58827.
  3. Update on the Font Library and 6.4 beta 2 from the core Slack
  4. Trac Ticket #59443 opened on performance regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. by @spacedmonkey during testing WP 6.4 beta 2. Aim is to fix is before Beta 3. The Slack message in core.
  5. Note in the Beta 2 release post there is a reference to testing beta releases using Local environment: Use wp-now to set up a Node.js-based WordPress 6.4 Beta 2 install locally. Learn more in this guide. This was discussed in core to include as it is an experimental option.
  6. Discussion on Trac Ticket #58827 that exposes the Patterns menu to classic themes. Ticket was moved to an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature.. Reasoning is on the ticket comment. The ticket has been punted to 6.5.
  7. Discussion on a request to allow #59131 to be committed as part of 6.4 Beta 2. Discussion thread that took place in core Slack this last week and links to previous messages on the reasoning.

Font Library update

Shared by @hellofromtonya

  • The REST API part of it:
    • works and has been working well. But its design is doing it wrong.
    • it’s in the process of a redesign in collaboration with the Core REST API maintainers
    • @timothyblynjacobs @spacedmonkey@swissspidyhave been providing feedback and guidance 
    • if the redesign can get done before next Monday, then it will ship in Gutenberg 16.8
    • changes are being done in Gutenberg and the Core PR to keep them in sync.
  • It did not ship in 6.4 Beta 2 because of this redesign.
  • When could it committed into Core?
    • Expectations: Redesign gets done, ships (in the plugin), and is approved by one of the Core REST API maintainers.
    • Once all of these expectations are met, a public discussion will be opened in #core in preparation for Beta 3.
    • Only bugfixes in GB 16.8 would come into Core. Not new features or enhancements, as the editor board was cleared of those at Beta 1.
  • Font Library testing instructions were included in 6.4 Beta 2 announcement post.

Existing 6.4 useful links

Next WordPress 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.3.2

Following Dev Chat, the discussion continued regarding timing for the 6.3.2 and 6.4 Beta 3 releases. These may be discussed further in #core, but keep an eye on the #6-3-release-leads and #6-4-release-leads channels for final timings.

Help requests: Components maintainers & Tickets

No other tickets were raised in the agenda comments or after Dev Chat.

Open Floor

There was not enough time for open floor discussion today.

Next meeting

The next meeting will be on 2023-10-11 at 20:00 UTC .

Props to: @hellofromtonya for facilitating the meeting,
@webcommsat for the agenda & summary, and to @ironprogrammer for review.

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

Dev Chat Summary, September 27, 2023

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

Key links

Announcements

WordPress 6.4 Beta 1 is available – please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed to getting this to 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 and those who came and led the release party on September 26.

Highlighted posts

The following were listed on the agenda but not highlighted during the meeting due to a discussion on 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/ and Beta 1:

  • WordPress Performance team has a new version of the Performant Translations pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party with improved compatibility and performance. It has more than 1000 installations as at September 26, 2023. More testers will be needed and @swissspidy has created a proof-of-concept core patch in the meantime.

Release updates

Next major WordPress release: 6.4

WordPress 6.4 Beta 2 is scheduled for October 3, 2023.

Discussion at Dev Chat focused on Gutenberg 16.7 and WordPress 6.4. More on this discussion will be available in a separate post on the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel soon. Link to start of the discussion on Slack.

@joemcgill suggested adding comments to the discussion from the WordPress Community Summit: Community Summit Discussion Notes: Aligning processes and contributions between WordPress Core and Gutenberg.

Stay in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. with 6.4 by following:

Next minor WordPress release: 6.3.2

Call for ticketticket Created for both bug reports and feature development on the bug tracker. reviews by @joemcgill 

The scrub on September 27, 2023 focused on the 6.3.2 milestone in preparation for another 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..
Five tickets in the milestone remain to be fixed in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision..
Request/ Action: reviews are needed of these tickets to move them forward, and if they are able to get in this week. Of note, are a few that need to be synced from the Gutenberg repo. If someone has planned to help with this, please comment in the 6.3 releases leads channel on Slack.

Also six tickets that are fixed, but need to be back ported to the 6.3 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"..
Request: if committers have some time to review and help, that would be a big help.

Discussion followed in Dev Chat and after on potential target dates for the next minor, which would allow time for work to be wrapped up on the remaining tasks. Provisional dates included October 10, earlier in the day from Beta 3. @joemcgill able to help with the 6.3.2 release and noted contributors are still need to be identified for official release roles.
Action: If you can volunteer to help with 6.3.2, comment in the 6.3 release leads channel on Slack. The date for the release is still under discussion.

Gutenberg

Help requests: Components maintainers & Tickets

No other tickets were raised in the agenda comments or after Dev Chat.

Open Floor

This item did not feature at this week’s Dev Chat due to time constraints.

Next meeting

The next meeting will be on Wednesday October 4, 2023, at 20:00 UTC.

Props to @webcommsat, @nalininonstopnewsuk, @ironprogrammer, and @hellofromtonya and @marybaum for review.

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

Dev Chat Summary, September 20, 2023

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

Key Links

Announcements

No announcements were made this week.

Highlighted Posts

Hallway Hangout: Performance Improvements for WordPress 6.4: Make plans to talk Performance at this hangouts session planned for October 19, 2023 at 15:00 UTC.

Analyzing the Core Web Vitals performance impact of WordPress 6.3 in the field: Read this thorough breakdown from @felixarntz of how 6.3 performance improvements have been reflected on production sites using WordPress at scale. Feedback in invited on the post.

Community Summit Discussion Notes: Increasing contributor recognition and celebration: Join the discussion on how contributor impact can be better identified and highlighted. The discussion at the summit considered the system of props, credit outside of a release, badges, encouragement of contribution.

Evolving the FSE Outreach Program: A reminder to provide feedback on the next phase for the #fse-outreach-experiment: Deadline for feedback: Friday, September 22, 2023

Additional Highlighted Post on Interoperability under Open Floor.

Release Updates

Next major WordPress release: 6.4

The last bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub 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 will be on Monday, September 25, 2023 at 17:00 UTC.

More on 6.4 highlighted under Open Floor.

Beta 1 is scheduled for next Tuesday, September 26.

Stay in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. with 6.4 by following:

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/

Reminder: the revised release schedule for the next Gutenberg release is as follows:

  • Gutenberg 16.7 RC1: released September 20 (originally planned for September 13)
  • Gutenberg 16.7: September 27

Components & Tickets

Testing request following a recent bug scrub from @joedolson:

  • TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. #58912: Mobile: Adminadmin (and super admin) menu unexpectedly closes with Safari – after the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. is updated, this will be ready for testing
  • Trac ticket #58756: Media library improvements: UIUI User interface, Non-closing options, and Button select state issues in image editing – this is ready for testing
  • Trac ticket #40822: no longer requires further feedback and is ready for commit


From the tickets posted by @oglekler before dev chat, assistance is needed with the list of tickets left to tackle before Beta 1 (updated September 22, 2023):

  • Trac #55459: Change Login Label name
  • Trac #56886: Admin facing add site screen missing search engine visibility field
  • Trac #58703: wp-list-table: <label> is preceding <input> in the checkbox column – this ticket has a new patch, and further testing is requested
  • Trac #40762: Login: add canonical admin shorthand URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for login.php

Open Floor

  • Call for WordPress developer proposals: Update from @adamsilverstein regarding Interop 2024 was added to the Highlighted Posts list by @webcommsat.
    Seeking proposals for Interop 2024. WordPress developers are asked to contribute their proposals for 2024 as on GitHub or as a comment on the proposals post. Interop aims to improve interoperability across the three major web browser engines (Chromium, WebKit and Gecko) in important areas as identified by web developers.
  • Call for assistance with 6.3.2: @joemcgill highlighted @mikeschroder‘s message about next steps for getting another bugfix out for 6.3, and if there were any contributors available to help lead the release.
    • @ironprogrammer raised that there may be many busy with beta 1 next week, and more hands may be raised after this
    • @jeffpaul thought the concern before WCUS was that something(s) milestoned for 6.3.2 might be worth getting out before 6.4 lands. He asked if people had interest and availability, could they share this in the #6-3-release-leads Slack channel as it would be very helpful.
  • ** A number of contributors highlighted the final stretch to 6.4 Beta 1, and the calls to help deal with as many bugs as possible, clear triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. queues, and review available content.
    @cbringmann reminded the meeting that contributions are for all and not restricted to just the release squad and cohort. She thanked everyone who is lending a hand to the 6.4 release.

Next Meeting

The next meeting will be on Wednesday September 27, 2023, at 20:00 UTC.

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

Props to @ironprogrammer for hosting the meeting,
@webcommsat and @zunaid321 for the notes,
and to @marybaum and @oglekler for reviews and updates on tickets.

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

Dev Chat Summary, September 14, 2023

The notes from the weekly WordPress developers chat which took place on Thursday, September 14, 2023 at 08:00 UTC in the core channel of Make WordPress Slack.

Key Links

Announcements

No announcements were raised this week.

Highlighted Posts

What’s new for developers, September 2023 is available now on the Developer Blogblog (versus network, site).

  • @webcommsat highlighted there were opportunities for contributors to put forward topic ideas and write for the Developer Blog or contribute to one of the approved topic submissions.

Core Editor improvement – commanding the command palette posted by @annezazu.

  • The post explores the latest updates to the Command Palette, a new tool available with WordPress 6.3 designed to speed up your workflow. It also gives a preview of highlights in creation experience coming in 6.4.

The FSE Outreach Program is evolving.

  • The FSE Outreach Program will become a focused space for solving issues, creating resources, and facilitating conversations around Phase 2 adoption. You can contribute by commenting on this post.
  • After 6.4 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, the facilitated calls for FSE testing will be replaced by ad hoc calls for testing run by the Make Test team or contributors who need specific features tested.
  • Deadline for feedback: Friday, September 22, 2023

Final call: Feedback on the Learning Pathways outline from Training team from CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is invited.

  • Through greater focus on the unique needs of different user groups, Learn.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/ aims to create a more intuitive and effective learning environment.
  • The latest discussion focuses on how the resource can move towards consolidating the current content type offerings from courses, tutorials, and lesson plans to courses and lessons.
  • Deadline for feedback: Friday, September 15, 2023.

Reminder: Proposal for an update to the Field Guide accompanying a release

  • This came from an informal discussions at the Community Summit.
  • Two parts of this proposal: to move earlier the date of the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. publication by one week to the final Beta, and to create and publish a simplified Field Guide on the Dev Blog. 
  • Deadline for feedback: September 15, 2023.

Monthly update on new materials on Learn.WordPress.orgSeptember 2023 edition.

Release Updates

Current major WordPress release: 6.3

No update on minor releases or 6.3.

Next major WordPress release: 6.4

Beta 1 is 2.5 weeks away on Sept 26, 2023 as this is a short release cycle. The next triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions will focus on brainstorming the remaining tickets to identify if they can be moved forward. A call to participate in the bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs was made by @oglekler and @webcommsat. Also, the scrubs are a great tool to review asynchronously to learn about the WordPress development process and identify ways to get involved.

Bug Scrub Schedule for WordPress 6.4
The scrubs take place in the core channel on the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

No other updates from the release squad.

6.4 useful links:

Release parties schedule for 6.4

Roadmap to 6.4 – this release is scheduled for November 7, 2023.

6.4 Development Cycle

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

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/

What’s new in Gutenberg 16.6 (published September 6, 2023)

Updated schedule:

  • Gutenberg 16.7 RC1 on September 20, 2023 (originally planned on September 13)
  • This will be the general cut-off date for new features developed in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, except tasks blessed in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
  • WordPress 6.4 Beta 1 on September 26, 2023
  • Except for the blessed tasks, only fixes can be included after this date.
  • Gutenberg 16.7 on September 27, 2023

Components & Tickets

The following tickets were raised by @afragen for feedback.

Core Trac #58281: Rollback Auto-Update (Rollback part 3)

Core Trac #22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticketticket Created for both bug reports and feature development on the bug tracker.)

The discussion thread on Slack for more information.

Open Floor

An update regarding the latest Fields 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. proposal for WordPress core was raised by @sc0ttkclark

Next Meeting

The next Dev Chat will be on September 20, 2023 at 20:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel or message @webcommsat, one of the Core Team reps, in the week before the meeting.

Props to @zunaid321 and @webcommsat for the notes

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

Dev Chat Summary, September 06, 2023

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

Key Links

Highlighted Posts

A Week in Core – September 4, 2023 – Props to @audrasjb for pulling this together! Changes on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between August 21 and September 4, 2023:

An overview of updates in Trac between August 21 and September 4, 2023:

  • 75 commits
  • 150 contributors 
  • 25 new contributors 
  • 129 tickets created
  • 13 tickets reopened
  • 117 tickets closed

Call for testing of Performant Translations > I18N Performance Analysis: Testing of a dedicated pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party as a solution for an issue discovered where localized WordPress sites load significantly slower than a site without translations, found in an in-depth i18n performance analysis.

Proposal: An update to the Field Guide: From some of the informal discussions at the Community Summit. There are two parts of this proposal: to move earlier the date of the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. publication by one week to the final 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., and to create and publish a simplified Field Guide on the Dev Blogblog (versus network, site). Deadline for feedback: Sept 15th.

Some of the posts from the 2023 Community Summit:

Communication and Collaboration – Finding Your Way Around WordPress

Iterating on the Team Rep role

Understanding contributor leadership roles in the WordPress open source project

and many more on the Make/Summit site

Release Updates

WordPress 6.4 Alpha 1 is underway: Beta 1 is due on September 25, 2023

Stay in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. with 6.4 by checking out:

Roadmap to 6.4

WordPress 6.4 Development Cycle hub

6.4 Editor tasks board

6.4 Release Parties Schedule and hosts

– This post aims to prepare a calendar with the expected start time for each release party and who is involved in the upcoming 6.4 milestones.

and you can follow along in the #6-4-release-leads channel

6.4 Scrub Schedule

Bug Scrub Schedule for WordPress 6.4

The bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub schedule will take place in core on the dates in this post. All are welcome to join the scrub!

Components & Tickets

6.4 Alpha dev has been underway since 18(ish) July. The window for early is closing soon. Contributors’ help is requested for testing and feedback on these tickets to help move them forward to hopefully land in 6.4.

Tickets that were raised:

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Trac #59187: Bundled Themes need to be update to node 16 – Check out the Slack discussion for more info as it was raised by @mikestraw

Core Trac #56780: ShortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. 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. in block-based template part in a classic theme does not get expanded – More eyes were requested by @petitphp. Please check the Slack discussion for more information.

Open Floor

Nothing was raised under this section.

Next Meeting

The next meeting will be on  Thursday, September 14, 2023 at 20:00 UTC

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

Props to @zunaid321 and @webcommsat for the notes and review.

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

Default Theme chat summary: September 6, 2023

This post summarizes the latest weekly Default Theme meeting (agenda, slack transcript), held in the #core-themes SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, september 6th 2023 at 3pm UTC.

Announcements

Twenty Twenty-Four introduction post: https://make.wordpress.org/core/2023/08/24/introducing-twenty-twenty-four/

Housekeeping and updates

  • Most patterns are in the theme, but need polish
  • Over 40 contributors so far

Changes in the editor are needed for the default theme. Please check out the list of issues and PRs relevant to TT4 and see if you can help in any way.

Open Floor

@colorful-tones proposed adding clarification for contributors to add the new define( ‘WP_DEVELOPMENT_MODE’, ‘theme’ ); in their wp-config.php. Will open a PR for the theme’s README

Translations will happen later on because it is hard to keep updating patterns and then making sure the translations functions persist when copy/pasting 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. markup from editor into files.

@maneshtimilsina pointed out that there are some issues with new lines, non-uniform spaces/tabs, which can be verified with linting. It exists in the repo. We’ll wait and do this as part of the overall cleanup later on.

@onemaggie is prioritizing getting patterns merged

It would be helpful for someone to do a walk-through of how to modify a pattern in the Site Editor, which could help onboard contributors (and be used in future default themes going forward).

Reminder: contributing to the theme is not just adding patterns or designing things, but documentation and triaging communication and 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 be the repository owner. https://github.com/ issues/PRs is invaluable work too.

Props to @colorful-tones for helping with creating this post.

#6-4 #bundled-theme #core-themes #summary #twenty-twenty-four

Default Theme chat summary: August 30th, 2023

This post summarizes the latest weekly Default Theme meeting (agenda, slack transcript), held in the #core-themes SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, August 30th 2023 at 3pm UTC.

Announcements

  • This meeting is aimed at the work around the next default theme Twenty Twenty-Four, which will be released with WordPress 6.4 in November. Please keep the topic on the theme!
  • We set the meeting time to Wednesday, 3pm UTC. In the agenda, the meeting time will be noted with the automatic timezone conversion. The meetings happen weekly and may be switched to bi-weekly if we’re closer to the release.
  • The next default theme has been introduced last week: Introduction to Twenty Twenty-Four
  • How you can contribute:
    • The work on TT4 will happen in this 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 be the repository owner. https://github.com/ repository: https://github.com/WordPress/twentytwentyfour
    • Please read through the readme file carefully, as it contains important information on how to get started.
    • If you want to contribute, check out the open issues and Pull Requests first, to see if your topic has been addressed already. If not, feel free to open an issue!
    • It would be fantastic if you can link a created PR to an issue, so it’s easier to keep track of things.

Open Floor

@maneshtimilsina mentioned contributers get confused about using esc_html__ or esc_html_x_ functions in patterns for translations.

  • Resource to translation documentation: https://developer.wordpress.org/apis/internationalization/internationalization-functions/
  • Resource to esc_html__ documentation: https://developer.wordpress.org/reference/functions/esc_html__/
  • Resource to esc_html_x documentation: https://developer.wordpress.org/reference/functions/esc_html_x/
  • Discussion summary:
    • Patterns should be checked if they use the correct functions
    • Any sample text should be commented that this is sample text, using the esc_html_x function
    • Any strings that may need further explanation to be correctly translated also need comments
    • Check on previous default themes for similar strings to see how it was handled there

@maneshtimilsina mentioned that there’s confusion about the home.php file, which contains multiple patterns

  • The patterns should be extracted into smaller components, which then possibly make home.php not needed anymore.

@kafleg mentioned the backlog of open PRs regarding patterns in the repository.

  • These will be taken care of this week.

@poena asked about the status of pattern categories and pattern switching for 6.4, and if this will work with non synced patterns

  • It seems this has not yet been discussed, an issue needs to be created to start a discussion around this topic

#6-4 #bundled-theme #core-themes #summary #twenty-twenty-four

Dev Chat Summary, August 16, 2023

The WordPress Developers Chat meeting took place on August 2, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Highlighted Posts

Here’s an overview of what’s happened in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between July 31 and August 14, 2023:

  • 40 commits
  • 50 contributors
  • 164 tickets created
  • 15 tickets reopened
  • 138 tickets closed
  • and 5 new contributors in this period ❤️
  • Status update on the Interactivity API: Get the latest updates on this proposal and where to track its progress. This post also includes info on valuable learning resources so you can dive in and explore the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.’s possibilities.
  • What’s new for developers? (August 2023): Do “new shiny objects”, “bag of goodies”, and “kid in a toy shop” spark your interest? Thought so! Check out the newest stuff in 6.3 and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ in this latest post on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/’s own Developer Blogblog (versus network, site).
  • What’s new in Gutenberg 16.4: Inside: A new progress bar component, updates to the Command Palette and Footnotes blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., and auto-inserting blocks are highlighted in the latest pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party release.
  • ⏰ Reminder: Share your comments on the ticket ownership discussion by September 1, 2023.

Release Updates

WordPress 6.3

  • See the WordPress 6.3 developer notes. The Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. has had 6,500 views since it was published on July 18!

WordPress 6.3.1

  • There are some urgent fixes that have been identified for a quick turnaround 6.3.1 release, but as of this writing, timing is still being decided. For the latest updates, follow discussions in the #6-3-release-leads channel.

WordPress 6.4

Stay in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. with 6.4 by checking out:

Maintainers: Component Help Requests

Rollback Auto Updates – Part 3

The Rollback Update Failure plugin has received several recent updates, and is awaiting security audit and additional feedback.

Plugin Dependencies

Plugin dependencies (Trac #22316) has been updated with the latest round of feedback, and is ready for commit consideration. Trac #59112 has been created to encompass remaining design input for this feature, which could be incorporated during the feature’s merge to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

Open Floor

WCUS 2023 Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

Make/Core Post

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US Contributor Day is next week! There is a Core blog draft underway that aims to promote and provide info to new contributors ahead of the event. The post is to be finalized after Dev Chat, and it is requested that Core community members provide feedback in the #core channel. Core Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @webcommsat is collating details for the event.

Volunteers Needed

Volunteers are needed to help facilitate in person at tables and remotely on Slack during Contributor Day. Contributors are asked to raise their hand in Slack, or add their name and level of participation in the post comments.

A handful of chat attendees raised their hands to help attend to Core tables throughout the day, as well as help remote attendees in Slack, but there are still no clear Core table leads.

Ticketticket Created for both bug reports and feature development on the bug tracker. Focus

There was a question about whether “ancient” Trac tickets should be a point of focus during Contributor Day, and there was general agreement that good-first-bug tickets were likely better candidates to focus on, given the limited time and resources available at the event.

New contributors to Core are encouraged to set up their local environments in advance of WCUS, and to join the next New Core Contributor meeting on 2023-08-23 at 19:00 UTC in the #core channel.

Fields API

A status update was provided for the WordPress Fields API, with a Make/Core post to come later this week. Those interested in this project are invited to help with project research, stop on by and chat with @sc0ttkclark at WCUS, and to join the conversation over in the #core-fields channel.

6.4 Scrub Schedule

The bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub schedule is still being finalized, but the first session is to take place on 2023-08-17 at 17:00 UTC in #core. All are welcome to join the scrub!

Next Meeting

The next meeting will be on August 23, 2023 at 20:00 UTC.

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

Props @afragen for peer review of this post.

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

Dev Chat Summary, August 2, 2023

The WordPress Developers Chat meeting took place on August 2, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Announcements

Highlighted Posts

Here’s an overview of updates in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between July 24 and July 31, 2023:

  • 21 commits
  • 40 contributors
  • 64 tickets created
  • 12 tickets reopened
  • 39 tickets closed
  • Synced Patterns: The Evolution of Reusable Blocks: New pattern functionality with WordPress 6.3.
  • Whose ticket is it, anyway?: Follow-up post to last week’s DevChat discussion about ticketticket Created for both bug reports and feature development on the bug tracker. ownership. Share your thoughts and opinions by September 1, 2023.
  • Proposal: improve the editor tech workflow for major releases: Ideas for improvements to ease the pain points of merging code from GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., particularly before BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1. This proposal has already generated a lot of favorable consensus to experiment with this approach in the 6.4 cycle.
  • This proposal has been adopted: Proposal: Criteria for Removing “Beta Support” from Each PHP 8+ Version. Involved contributors are currently in the process of:
    • working through the action items list.
    • evaluating the list of incompatibilities for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.0 and 8.1 for WordPress 6.3.

Release Updates

WordPress 6.3

@hellofromtonya asked if Trac #58940 – site-health.php page Fatal error on version: 6.3-RC2 would require another RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). release. It was confirmed that the ticket was opened before RC 3, but not fixed in that release. @jeffpaul and @audrasjb agreed that another RC may be warranted, and would check other tickets that remain in the 6.3 milestone (or same query grouped by workflow).

WordPress 6.4

@hellofromtonya indicated that work was underway on 6.4 early tickets.

@chanthaboune noted that wishlist items were being gathered, and that 6.4 release coordinators would be able to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. these earlier than is typical, since the 6.4 release cycle is shorter than normal. Of particular note was consideration of items requiring additional dev, design, or a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) attention before committing them to the release.

Maintainers: Component Help Requests

@craigfrancis asked for attention on Trac #54042 – Extending wpdb::prepare() to support IN() operator, and consideration for 6.4 early designation. He asked for review and thoughts/suggestions on improving the existing patches.

Open Floor

Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. Core/Core-* Tables

@desrosj related questions he’d received regarding how Core tables are often spread out at Contributor Day, which can be confusing for both new and experienced Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. who wish to move between tables, especially for collaboration with other focus teams. @webcommsat agreed that it would be beneficial to locate them closely together, to avoid the issue of contributors getting confused and dropping out of the event.

@desrosj also asked if there were any volunteers from the #core-performance and #core-editor channels who would be willing to lead their respective tables at WCUS. @hellofromtonya suggested posing the question to each team’s Slack channel. @joemcgill raised his hand for helping at the Core Performance table.

PHP 8.3

@hellofromtonya shared that initial impressions concerning PHP 8.3 are that it would have a low impact to Core. PHP 8.3’s release date is scheduled for November 23, 2023.

Next Meeting

The next meeting will be on August 9, 2023 at 20:00 UTC.

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

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

Dev Chat Summary, June 7, 2023

The WordPress Developers Chat meeting took place on June 7, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Announcements

  • WordPress 6.4 Development Cycle: The third planned 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. for 2023 is taking shape! Check out the release team and supporting cohort, the release schedule, and learn how you can get involved with 6.4.
  • Gutenberg 15.9.1 available: 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. provides two fixes: custom fonts are again visible on the editor, and social icon colors now correctly reflect changes in Global Styles. Thanks to everyone involved in this release.

Highlighted posts

Here’s an overview of updates in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between May 22 and June 5, 2023:

  • 37 commits
  • 63 contributors
  • 91 tickets created
  • 9 tickets reopened
  • 71 tickets closed
  • and 10 new contributors in this period ♥️
  • Contribute to Core at WordCamp Europe Contributor Day 2023: Are you preparing to join the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2023 CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tables on Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.? Check out this helpful post to get started, and to set up a local environment in advance of the event. Note: there are no more tickets for Contributor Day, the additional attendee tickets have now all gone.
    For those people who want to get started contributing to core, but were unable to get tickets, the links below are a good start:
  • June 2023 Developer Blog Editorial Meeting: Update from @webcommsat for the Editorial Group – If you are looking to contribute through writing blogblog (versus network, site) posts, check out the summary from this most recent Developer Blog editorial meeting for a list of articles under discussion or in need of a writer. There are editors who support the posts through the process of being published, so don’t worry if you have not contributed to the Developer Blog previously.
    • Have an idea for a post? Great! You can also suggest posts that you would like to read or contribute to the blog. Or do you just want to read excellent content geared toward WordPress developers? Got you covered there, too: check out the latest posts.
    • The Editorial Group wants is encouraging developers to come along and contribute on topics that are approved and suggest new ones, including on how to use new features in a release etc. Please do chat with people at WCEU who might be interested. There is a lot of support available.

Release updates

WordPress 6.3 will be the next major release. Stay in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. by checking out:

  • Roadmap to 6.3
  • WordPress 6.3 Planning Roundup
  • and following along in the #6-3-release-leads channel
  • with 6.3 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 less than 3 weeks away are there any enhancements or feature requests milestoned there that need help with patches, testing, review, or committing?

Query on Fonts-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.

  • @joemcgill raised during the performance ticketticket Created for both bug reports and feature development on the bug tracker. scrub earlier, a few contributors were wondering about the Fonts-API and whether any support was needed to test that feature since it’s being developed in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repo. 
  • @hellofromtonya: Help is always appreciated! Always! There are a number of issues / enhancements being worked on that can use some testing reports and code help.
    • The Fonts API project board on GitHub.
    • The Ongoing Roadmap which has a list of “required for Core introduction” items.
    • In addition to those tickets/items, general testing to try and break it are appreciated.
    • When it’s moved out of “experimental” (note, the API is still experimental and will be until all of the required items are done and released in Gutenberg), then it’ll be a single PR to test and commit.
    • Why single PR? Because it’s been well-tested in Gutenberg over many months. Once it’s ready, it should be fully ready for Core introduction.
    • What is keeping it in “experimental”?
      The biggest reason is: the interaction between Theme JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. and Fonts API for populating typography pickers in editors (not including the Site Editor). This issue. The scope of this will change with the introduction of the Font Library.
    • What’s the Font Library?

Tickets/ Component Maintainers help requests

To start, there were a couple of requests for help in the open floor section of the #core-editor meeting on May 31, 2023, including:

No comments were raised during the live meeting on these two areas.

Open floor

Two items:

  • WordCamp Europe attendees were encouraged to ask any questions during the meeting or in the contributor-channel/ core channel relating to Core contribution.
  • @hellofromtonya: A proposal is drafted and will be published before next week’s dev chat. The proposal is for setting criteria for removing “beta support” from each PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8+ version. It includes seeing the criteria in action for WordPress 6.3 which could possibly mean removing “beta support” label from PHP 8.0 and 8.1 – maybe.

Next Meeting

The next meeting will be on June 14, 2023 at 20:00 UTC.

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

Props to @ironprogrammer and @webcommsat for the summary, and @hellofromtonya for peer review.

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